Unable to access internal services on a DC

November 5, 2010 at 12:44:52
Specs: Windows Server 2003 R2 Enterprise Edition, Core i5/1.97GB
Hi everyone,

I have a self-contained (including DC) virtual machine I have setup as a 2003 AD/Exchange server for internal testing (this machine will NOT be on the open internet...it operates as a guest on my laptop, which belongs to a corporate domain). The server SEEMS to be running fine thus far. I have it setup to use the corporate domain's DHCP (no need for static IP).

PROBLEM: I have a web server setup on the DC machine, but I cannot access it from my laptop.

Typically, with a non-DC machine, I am able to access the server's resources through the IP address. However, when I ping this machine (10.0.2.15), I get the following:

Pinging 10.0.2.15 with 32 bytes of data:
Reply from 75.77.135.40: TTL expired in transit.

When I ping 75.77.135.40, I get the following:

Pinging 75.77.135.40 with 32 bytes of data:
Reply from 75.77.135.40: bytes=32 time=33ms TTL=249

On the server itself, I am able to "telnet 10.0.2.15 80" but not "telnet 75.77.135.40 80".

From my laptop, I am neither able to "telnet 10.0.2.15 80" nor "telnet 75.77.135.40 80".

Any ideas?

Thanks in advance.


See More: Unable to access internal services on a DC

Report •

#1
November 5, 2010 at 14:00:43
Hi everyone,

I just wanted to follow-up. The IT sysadmin suggested that I should switch the virtual NIC from NAT to Bridged. That successfully resolved the issue.

However, if there was a way to get it working under NAT, that would be helpful as well.


Report •
Related Solutions


Ask Question