Page 1 of 1

Internal Network not communicating!

Posted: 13. Dec 2012, 00:37
by Paul86uk
Hope someone can help,
I'm new to Virtual technology but pretty tech savvy otherwise..

my problem is,
i have a virtual box(4.2.4) running on a win7 Home Premium 64bit,
Virtual Machines are..
1. 'Server' Windows Server 2008 R2 Enterprise 64bit
Server-2012-12-12-22-21-57.zip
Server log
(9.6 KiB) Downloaded 5 times
2. 'Client' Windows 7 Proffesional 64bit
Cli1-2012-12-12-21-55-54.zip
Client log
(18.87 KiB) Downloaded 1 time
the virtual card does not provide a DHCP, as the Server provides a dhcp and a dns..
virtual cards IP is. 192.168.1.5 subn 255.255.255.0
both VM's have a single NIC which is set to Internal, net name is 'intnet' for both..

'Server' has a static IP of 192.168.1.10 subn 255.255.255.0 dns 192.168.1.10
'Client' is set to assign by DHCP

left to itself, neither reports any traffic or a connected network though the connection has 'media connected'

if i assign a gateway to the client of 192.168.1.10 it recognises there is a network, and can ping the server
but fails any other communication, also if i try to add the 'server' IP as a dns server the client reports it is on a
diffrent subnet...

in both scenarios the server cannot ping the client, with a transmit general failure.

ive also tried setting both VM's gateway as the IP of the virtual card, no effect.

im at a loss...

Re: Internal Network not communicating!

Posted: 13. Dec 2012, 08:26
by BillG
Communicating between two machines in the same IP subnet does not require a default gateway. Communication is by direct connection using the hardware (MAC) addresses of the machines. Using a virtual network does not change that fact. A default gateway is only required to communicate with machines in another subnet or network.

If the machine is telling you that the DNS service is in a different subnet, something is misconfigured. Check the configuration of the DHCP server, then check the actual values being issued to the client machine. If you still can't see what is going on, post the ipconfig of both vms.

Re: Internal Network not communicating!

Posted: 13. Dec 2012, 21:00
by Paul86uk
yes i know that it doesnt require a gateway if the subnet is the same, i only appiled the gateway when then client reported the server
being on a seperate subnet...
IP configs...

Server:
IP : 192.168.1.10
subn : 255.255.255.0
DNS : 192.168.1.10

Client:
autoconfig IP : 169.254.164.216 (preferred)
subn : 255.255.0.0
DNS : 192.168.1.10
(sure you know, but this is the default config given by windows when one isnt assigned.)

if i open the IPv4 config on the client, IP is set to obtain automatically, with a specified DNS of 192.168.1.10 and nothing else..
alternate config is blank.

even if i specify an IP on the client of.
IP : 192.168.2.1
subn : 255.255.255.0
dns : 192.168.1.10

it still fails to communicate,

ive also tried assigning ip to the client, and reserving that ip on the dhcp..
still no comms.

Re: Internal Network not communicating!

Posted: 13. Dec 2012, 21:57
by noteirak
Please show the output of

Code: Select all

route print
on the server and the client

Re: Internal Network not communicating!

Posted: 14. Dec 2012, 00:05
by Paul86uk
Client route print.zip
(553 Bytes) Downloaded 5 times
Server route print.zip
(637 Bytes) Downloaded 3 times

Re: Internal Network not communicating!

Posted: 14. Dec 2012, 00:10
by noteirak
Paul86uk wrote:even if i specify an IP on the client of.
IP : 192.168.2.1
subn : 255.255.255.0
dns : 192.168.1.10
I just realised something : is 192.168.2.0/24 the subnet of IP that you've setup in your DHCP?

Also, put the following ip config on your client :
IP : 192.168.1.1
subnet : 255.255.255.0
nothing in router & DNS

then try to ping 192.168.1.10 again

Re: Internal Network not communicating!

Posted: 14. Dec 2012, 20:21
by Paul86uk
yeah i did that aswell, no luck. but it did disable my ability to get on the internet from the host as thats the ip of my router.. lol.

no, that was just an ip i assigned to the client as a test, the subnet on the DHCP is 255.255.255.0

Re: Internal Network not communicating!

Posted: 14. Dec 2012, 23:22
by noteirak
If you duplicated your router's IP, it won't work for sure :) give another ip then, like 192.168.1.35.

Which digit you put for the last number is irrelevant, all I am looking for is to be sure with static IPs in the same subnet (192.168.1.x), you can actually ping. If you can't, then we can go deeper.

Re: Internal Network not communicating!

Posted: 16. Dec 2012, 14:32
by Paul86uk
tried it, no joy...

rather irritating...

Re: Internal Network not communicating!

Posted: 16. Dec 2012, 14:39
by noteirak
Did you disable the windows firewall or at least enable the ports you want to access? By default it is on