i need help accessing my guest pc from other pcs in network

[samipk]

Hello everyone,

i am a noob to VMware workstation 6 beta, i just setup a windows 2003 server system as a guest and my host os is also windows 2003 server, i wanted to use the guest os as a domain controller to get my other network pc to be in a domain this way but i am unable to get the pcs on the network to access the guest system , i did a configuration on the guest which allowed it to access other pcs in the network but the other pcs were not able to connect to it

My host os has 2 NIC cards both having static ips one has a public ip and is used to access internet and the other has private ip and is used to access my local network

i want to be able to connect to internet on the guest and also want other systems in the network to access the guest os please help me out in this step by step

i am attaching the screenshots of various thing to help out

here is the ipconfig screen of the guest os

\[img]http://img157.imageshack.us/img157/4670/screenfi5.jpg[/img]

here is the ipconfig screen of the host os

\[img]http://img405.imageshack.us/img405/7244/hostscreency9.jpg[/img]

here is the summary screen of the guest

\[img]http://img172.imageshack.us/img172/7558/summaryka8.jpg[/img]

here are the screenshots of the virtual network setting tabs

\[img]http://img256.imageshack.us/img256/7623/91647152vj5.jpg[/img]

\[img]http://img256.imageshack.us/img256/7154/28457454az9.jpg[/img]

\[img]http://img296.imageshack.us/img296/4637/69475442ec7.jpg[/img]

\[img]http://img187.imageshack.us/img187/6571/62507898au9.jpg[/img]

\[img]http://img187.imageshack.us/img187/6360/32337986fd7.jpg[/img]

waiting for a quick response thanks in advance

P.S SURECOM ETHERNET ADAPTER #2 is the NIC having the private ip address of my LAN which is 192.168.0.4

Message was edited by:

samipk

[samipk]

yet another question peter... where is this ip 192.168.130.2 located, i can ping it from the freebsd guest as well as windows 2003 server guest but i have not given this ip in either of the os, is this the ip that freebsd router gives itself if we start routing in it???

thanks

[Peter_vm]

It is a VMware NAT router (for VMnet8), running on your VMware host.

Did you publish information about your VM guest (IPCONFIG /ALL and .vmx)?

[samipk]

yeah look at 2 posts above and you will find the config and other details

and 192.168.130.2 is not the Vmnet 8 ip the Vmnet8 ip is 192.168.130.1 thats why i am confused where 192.168.130.2 is cause host cannot ping that ip only the guests can

[Peter_vm]

Where is your Windows 2003 guest .vmx and IPCONFIG /ALL ?

[samipk]

Peter_vm thank you for your continous support in order to solve the problem i know it would have been very hard to be patient and solve the problem with me as i was a total noob to freebsd but now the problem is solved i got everything right last night when i setup freebsd as a router the only reason why nobody was able to ping freebsd on 192.168.0.10 was that the second nic was disabled yesterday due to some reason...anyways now everyone can access each other lan user are now able to access guest VM or operating system which was unable to be accessed before

before i go one last question i just dont understand still what 192.168.130.2 is.... it is not the Vmnet 8 ip, the Vmnet8 ip is 192.168.130.1 thats why i am confused where 192.168.130.2 is cause host cannot ping that ip only the guests can

thanks for solving the problem mate

[RDPetruska]

The .2 is the built-in gateway address for the VMnet8 NAT switch.

[Peter_vm]

Read the manual:

http://www.vmware.com/pdf/ws55_manual.pdf

Paragraph "Understanding NAT" Page 367-379

In order to make networking configuration easy, a DHCP server is automatically

installed when you install VMware Workstation. Virtual machines running on the

network with the NAT device can dynamically obtain their IP addresses by sending

out DHCP requests. The DHCP server on the NAT network, which is also used in hostonly

networking configurations, dynamically allocates IP addresses in the range of

.2 as the default gateway and DNS server. This causes all IP packets destined for

the external network and DNS requests to be forwarded to the NAT device.[/code]

[samipk]

thank you again for the explanation of the .2 system thank you all for the continous support if anyone wants to learn how i did it do let me know i will try to pass the knowledge on

thanks to everyone who replied to this post especially peter_vm

[samipk]

i have another problem....i installed squid on a fedora core vm, and tried to access that server from a windows 2003 server but cannot do so it gives me errors i also tried to use the squid server from suse linux vm and it gives me an error that "cannot connect to host proxy" or sometimes also gives an error of route not found

the ips of all the systems are from 192.168.130.128 to 131 and the gateway is 192.168.130.2 for the freebsd

i dont know how to get the default gateway in fedora or suse so if you want any info in that regard kindly tel me step by step

but in windows 2003 server you can ask whatever you want in order to make squid work