Sponsored Content
Full Discussion: Connecting windows to Vmware
Special Forums UNIX and Linux Applications Virtualization and Cloud Computing Connecting windows to Vmware Post 302905994 by kaushik02018 on Monday 16th of June 2014 01:08:08 PM
Old 06-16-2014
Quote:
Originally Posted by blackrageous
You probably don't have the correct IP address or a fire wall rule is blocking it.
I am using ifconfig to get ip address and used /etc/init.d/iptables stop

and on windows stopped firewall still not able to connect from windows putty to vmware
 

10 More Discussions You Might Find Interesting

1. IP Networking

Connecting SGI to Windows PC

I am trying to network an SGI running Irix 6.5 through an ethernet line to a PC running Windows 2000 (I have connected other PC's to this PC without any problems.) The PC has a DSL connection from Verizon that does not support Unix. I tried using DHCP on the SGI, but when I open a web browser on... (2 Replies)
Discussion started by: mdbanas
2 Replies

2. UNIX for Advanced & Expert Users

connecting to windows from unix

how to connect to windows from unix??? (7 Replies)
Discussion started by: hemant30
7 Replies

3. Windows & DOS: Issues & Discussions

free VMWARE clone for windows?

I'm looking for a free alternative to VMWARE, that will function in the same way. Bochs is not an option, and I can't seem to find any other viable software that will run on Windows. Cygwin is not what I'm looking for. Anyone know of public license software that is like VMWARE? (4 Replies)
Discussion started by: dangral
4 Replies

4. Windows & DOS: Issues & Discussions

Connecting UNIX to Windows

Is there a way to connect to Windows from UNIX. From Windows to UNIX, there is a putty that can be used. Is putty also possible to use to connect? (2 Replies)
Discussion started by: punyenye
2 Replies

5. IP Networking

connecting to Unix from windows - help

Hello, I have a requirement like - I need to connect to specific Unix machine.That machine authenticates the user who is logging in. I am accessing from XP machine. Is possible to supply the Username & Password along with Host name and port, from Windows command prompt? If so how? (13 Replies)
Discussion started by: cassiel
13 Replies

6. Linux

What's better for running Windows software in Linux, Wine or Windows VMware?

What are the differences, advantages, and disadvantages? (1 Reply)
Discussion started by: Advice Pro
1 Replies

7. Solaris

Can not ping from Solaris VMWare to Windows

Dear All, I have installed Sun Solaris 10 on VMWare 6.5 completely and i have configured IP address already. Solaris's IP Address (on VMWare) is 192.168.10.241 and Windows xp that contain VMWare IP address is 192.168.10.125, but when i ping from solaris to my windows it didn't response at all.... (3 Replies)
Discussion started by: veasnabee
3 Replies

8. Solaris

Connectivity between Solaris 10 in VMWare and windows Host

I have installed Open Solaris 10 on VMware which is hosted on Windows XP, my PC. I would like to have a connection between Solaris and Windows, so that i can SSH/Telnet from windows to Solaris. I don't have any Internet connection. Please help me with the network connection settings i have to... (3 Replies)
Discussion started by: mailsachin245
3 Replies

9. Shell Programming and Scripting

Connecting to Windows Server

Hi, One of the folders in UNIX is mapped with a drive on Windows.From this UNIX machine I want to connect to the Windows Server, perform some checks and view the results back on the UNIX machine. For e.g. if I touch a file under the shared folder on UNIX, I should be able to telnet to Windows... (2 Replies)
Discussion started by: swasid
2 Replies

10. Red Hat

Share folder between vmware and windows

when i try to mount share folder in redhat mount share -t vmboxfs /mnt it shows no filesystem vmbox:) (4 Replies)
Discussion started by: amitbharad
4 Replies
FIREWALLD.DIRECT(5)						 firewalld.direct					       FIREWALLD.DIRECT(5)

NAME
firewalld.direct - firewalld direct configuration file SYNOPSIS
/etc/firewalld/direct.xml DESCRIPTION
A firewalld direct configuration file contains the information about permanent direct chains and rules. These are the chains, rules and passthrough ... This is the structure of a direct configuration file: <?xml version="1.0" encoding="utf-8"?> <direct> [ <chain ipv="ipv4|ipv6" table="table" chain="chain"/> ] [ <rule ipv="ipv4|ipv6" table="table" chain="chain" priority="priority"> args </rule> ] [ <passthrough ipv="ipv4|ipv6"> args </passthrough> ] </direct> direct The mandatory direct start and end tag defines the direct. This tag can only be used once in a direct configuration file. There are no attributes for direct. chain Is an optional empty-element tag and can be used several times. It can be used to define names for additional chains. A chain entry has exactly three attributes: ipv="ipv4|ipv6" The IP family where the chain will be created. This can be either ipv4 or ipv6. table="table" The table name where the chain will be created. This can be one of the tables that can be used for iptables or ip6tables. For the possible values, please have a look at the TABLES section in the iptables man pages: For ipv="ipv4" in iptables(8), for ipv="ipv6" in ip6tables(8). chain="chain" The name of the chain, that will be created. Please make sure that there is no other chain with this name already. Please remember to add a rule or passthrough rule with an --jump or --goto option to connect the chain to another one. rule Is an optional element tag and can be used several times. It can be used to add rules to a built-in or added chain. A rule entry has exactly four attributes: ipv="ipv4|ipv6" The IP family where the rule will be added. This can be either ipv4 or ipv6. table="table" The table name where the chain will be created. This can be one of the tables that casn be used for iptables or ip6tables. For the possible values, please have a look at the TABLES section in the iptables man pages: For ipv="ipv4" in iptables(8), for ipv="ipv6" in ip6tables(8). chain="chain" The name of the chain where the rule will be added. This can be either a built-in chain or a chain that has been created with the chain tag. priority="priority" The priority is used to order rules. Priority 0 means add rule on top of the chain, with a higher priority the rule will be added further down. Rules with the same priority are on the same level and the order of these rules is not fixed and may change. If you want to make sure that a rule will be added after another one, use a low priority for the first and a higher for the following. The args can be any arguments of iptables or ip6tables, that do not conflict with the table or chain attributes. If the chain name is a built-in chain, then the rule will be added to chain_direct, else the supplied chain name is used. chain_direct is created internally for all built-in chains to make sure that the added rules do not conflict with the rules created by firewalld. passthrough Is an optional element tag and can be used several times. It can be used to add rules to a built-in or added chain. A rule entry has exactly one attribute: ipv="ipv4|ipv6" The IP family where the passthrough rule will be added. This can be either ipv4 or ipv6. The args can be any arguments of iptables or ip6tables. The passthrough rule will be added to the chain directly. There is no mechanism like for the direct rule above. The user of the passthrough rule has to make sure that there will be no conflict with the rules created by firewalld. EXAMPLE
Blacklisting of the networks 192.168.1.0/24 and 192.168.5.0/24 with logging and dropping early in the raw table: <?xml version="1.0" encoding="utf-8"?> <direct> <chain ipv="ipv4" table="raw" chain="blacklist"/> <rule ipv="ipv4" table="raw" chain="PREROUTING" priority="0">-s 192.168.1.0/24 -j blacklist</rule> <rule ipv="ipv4" table="raw" chain="PREROUTING" priority="1">-s 192.168.5.0/24 -j blacklist</rule> <rule ipv="ipv4" table="raw" chain="blacklist" priority="0">-m limit --limit 1/min -j LOG --log-prefix "blacklisted: "</rule> <rule ipv="ipv4" table="raw" chain="blacklist" priority="1">-j DROP</rule> </direct> SEE ALSO
firewall-applet(1), firewalld(1), firewall-cmd(1), firewall-config(1), firewalld.conf(5), firewalld.direct(5), firewalld.icmptype(5), firewalld.lockdown-whitelist(5), firewall-offline-cmd(1), firewalld.richlanguage(5), firewalld.service(5), firewalld.zone(5), firewalld.zones(5) NOTES
firewalld home page at fedorahosted.org: http://fedorahosted.org/firewalld/ More documentation with examples: http://fedoraproject.org/wiki/FirewallD AUTHORS
Thomas Woerner <twoerner@redhat.com> Developer Jiri Popelka <jpopelka@redhat.com> Developer firewalld 0.3.9 FIREWALLD.DIRECT(5)
All times are GMT -4. The time now is 07:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy