• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
straytoasters

Two machines cant ping each other

4 posts in this topic

I have two machines set up in Virtual Box. One is a W2K8R2 domain controller (DC2) one is a Windows 7 32 bit client (CL1). Both have internet access, but cannot ping each other. Settings below:

DC1

Windows IP Configuration

Host Name . . . . . . . . . . . . : testdc2

Primary Dns Suffix . . . . . . . : muppet.local

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : muppet.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel® PRO/1000 MT Desktop Adapter

Physical Address. . . . . . . . . : 08-00-27-A2-E1-09

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 10.0.2.100(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.0.2.2

DNS Servers . . . . . . . . . . . : 127.0.0.1

8.8.8.8

NetBIOS over Tcpip. . . . . . . . : Enabled

CL1

Windows IP Configuration

Host Name . . . . . . . . . . . . : win7-32cli1

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel® PRO/1000 MT Desktop Adapter

Physical Address. . . . . . . . . : 08-00-27-61-33-11

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

IPv4 Address. . . . . . . . . . . : 10.0.2.15(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.0.2.2

DNS Servers . . . . . . . . . . . : 10.0.2.100

8.8.8.8

NetBIOS over Tcpip. . . . . . . . : Enabled

The ultimate goal is of course to join CL1 to DC1's domain (muppet.local) but as it cannot ping or contact in any way that is not possible right now.

If I DNS ping DC2 I get "the ping request could not find host testdc2. Please check the name and try again. If I IP ping DC2 I get four returns of "Reply from 10.0.2.15: Destination host unreachable", which I assume is not really a response from the "router" (Virtual Box) essentially saying "couldn't find it...sorry 'bout ya".

I think it has to do with CL1 not having muppet.local in its DNS suffix search list, but if that is the case I am not exactly sure where to set that at (in network settings, but its not obvious where). Both machines have the same subnet mask and default gateway, so I thought they would be able to see each other. The DNS on DC1 is 127.0.0.1 (itself) and 8.8.8.8 (Google) and the DNS on CL1 is 10.0.2.100 (DC1's real IP address) and 8.8.8.8 (Google again). All information is static (even the IP's, which of course is required on DC1, but when CL1 was dynamic, the same issue were present...thus prompting me to put CL1 as static).

I feel like I am missing something pretty basic and I will be very embarrassed when someone points it out (but that's okay). Thanks everyone.

StrayToasters

0

Share this post


Link to post
Share on other sites

Your DNS situation is interesting but shouldn't impact the ability for two machines on the same subnet to be able to ping each other. Will they both reply to pings from the host machine (not VM)?

0

Share this post


Link to post
Share on other sites

Both can ping the host successfully (get a reply). They can also ping their same default gateway 10.0.2.2 (kinda goes without saying, but I said it anyway). You said my DNS setup is interesting, is there some other configuration I should try? The VM's themselves are set to "NAT" from the Virtual Box controls. If I choose "Bridged" I get a real public IP, if I set to "host only" I get a 192.x, if I set it to "Internal Network" I get a 169.x.

The "Internal Network" is useless obviously, I set CL1 to bridged (giving it a public IP), but neither DC2 or the host could ping CL1. I am wondering if when set to NAT and thus 10.x addresses Virtual box considers that to be its domain (bad choice of words) exclusively. So, maybe I HAVE to use "Host Only", but that would make me have to change some other settings (well, it may not be so bad).

Hmm, I just tried that (with both set as as "host only"/192.x) and they can ping each other. What this comes down to is I guess I'll have to do that and either have two NIC's in each machine (for internet access) or set up NAT-ing/RAS on DC2 (which still means it needs two NIC card...but they are all virtual so "money is no option").

If anyone has any better suggestions please let me know.

StrayToasters

0

Share this post


Link to post
Share on other sites

Something does seem to be funky but if you've gotten your config to a state that works then you are probably best served taking the "if it ain't broke, don't fix it" route even if the configuration is less than ideal. So let's see if you're the type of person that lets those extra NICs eat away at you until you get so annoyed that you blast an entire weekend reconfiguring your network :)

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.