Nat Problems On Hyper-V Server

[ICTCity]

It can't work, if you put the same ip of your router (10.0.0.1) your network simply doesn't work. The problem is that you CANNOT surf (actually exit) from your LAN (10.0.0.0) also with others computers. It looks like there are 2 same IPs. Maybe you have mis configured a static or DHCP IP somewhere. Is it possible?

[nasomi]

C:\Documents and Settings\Owner>tracert 8.8.8.8

 

Tracing route to google-public-dns-a.google.com [8.8.8.8]

over a maximum of 30 hops:

 

1 30 ms

[nasomi]

that was just with DHCP and RAS. Then I installed hyper-v and got this:

 

C:\Documents and Settings\Owner>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1     *        *        *     Request timed out.
2     *        *        *     Request timed out.
3     *        4 ms     4 ms  L100.PHLAPA-VFTTP-97.verizon-gni.net [173.49.21.
1]
4     5 ms     6 ms     7 ms  G0-6-3-2.PHLAPA-LCR-22.verizon-gni.net [130.81.1
39.140]
5     9 ms     9 ms     7 ms  so-3-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
22.60]
6     8 ms    12 ms    17 ms  0.so-7-0-0.XL4.PHL6.ALTER.NET [152.63.3.81]
7    13 ms    32 ms    19 ms  0.so-1-0-1.XL4.NYC4.ALTER.NET [152.63.1.170]
8    26 ms    29 ms    15 ms  TenGigE0-5-1-0.GW8.NYC4.ALTER.NET [152.63.21.73]

9    39 ms    40 ms    33 ms  Internet-gw.customer.alter.net [152.179.72.66]
10    15 ms    14 ms    29 ms  216.239.43.114
11    57 ms    24 ms    49 ms  72.14.239.93
12    29 ms    29 ms    16 ms  72.14.236.200
13    17 ms    37 ms    22 ms  216.239.49.145
14    17 ms    17 ms    22 ms  google-public-dns-a.google.com [8.8.8.8]

Trace complete.

[nasomi]

And again. strange results.

 

C:\Documents and Settings\Owner>tracert 8.8.8.8

 

Tracing route to google-public-dns-a.google.com [8.8.8.8]

over a maximum of 30 hops:

 

1 7 ms

[nasomi]

And from the VM pre-restart:

 

C:\Users\Administrator>tracert 8.8.8.8

 

Tracing route to google-public-dns-a.google.com [8.8.8.8]

over a maximum of 30 hops:

 

1

[nasomi]

Post restart. Every computer, including the host, vm, and other physical server, tracert always goes to 10.0.0.1 for 30 hops then gives up.

[nasomi]

I deleted the virtual network adapter from the config, restarted, and it worked. Reinstalled, restarted, and it stopped. This is beyond my realm of smartness.

[ICTCity]

Your problem seems to be the firewall.

 

Also when the traceroute works, the second "hop" fails, and there should be your firewall (after the first gateway).

 

It's ok that a HOP is dropped, but actually the same device (assuming it is your firewall), is blocking some traffic. Maybe there's PORT SECURITY configured on a switch / port and when the mac-address changes, it blocks the port.

[nasomi]

I found the issue. I had to uncheck the "Allow management operating system to share this network adapter" Everything works fine now. Thanks for all of your help.

 

.

Edited February 9, 2014 by AWS

[ICTCity]

This resolved your issue but for me this is not the actual problem. I'm still thinking that your problem was a switch or firewall blocking the mac address, because that option is always on and you have the issue ONLY after a restart... but I could be wrong...