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.

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.

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.

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

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

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.

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

Yes, but traffic trying to work on the clients of the LAN should be routed through to the WAN. If a computer gets it's IP from LAN, it goes computer >> lan >> wan for internet route. Why doesn't this work with the 3rd nic? Perhaps if i add the vlan adapter to the NAT portion of the RRAS role and set it to private network, it will route it's internet through the WAN port. OR!!! What if I disinclude the 3rd nic, install hyper-v first to create the vlan adapter, then go into ipv4 of that and set the ip manually to 10.0.0.1, then configure DHCP to work off the vlan adapter instead of the LAN adapter, the configure RRAS on the VLAN >> WAN route. It's so crazy it just might work...

I'm not sure I understand what you mean by the same work.

That's why I had to have the 3rd interface added. When I would install hyper-v, it makes you select a network interface for the vm's. I select the 3rd interace, which should route traffic from the vlan over the router to the lan port, then RRAS translates traffic coming in on the lan port over to the wan port.

I was thinking about that for a minute, jumping through more hoops than necessary. I ran dhcp and rras forever and it was fine, and i ran hyper-v and it was fine. it was when i put it together. that the problem came up.

DHCP & RRAS works perfectly. Everything works fine with dhcp and rras. everyone gets the internet. The moment i install hyper-v and the vlan is created, everything stops.

Yeah, I've become pretty damned efficient at that, i did it about 30 times last weekend trying to figure out what i was doing wrong or doing out of order(because order affects how rras and dhcp roles play together...).

That's the thing, after that restart, I can't get it to work again until I do a fresh install of the OS. I'll try removing all the roles, but that hasn't worked in the past.

sitting at the server i did tracert 8.8.8.8. What network port it went over I'm not sure. I'm guessing it went over 10.0.0.15 through to 10.0.0.1 I also did it from a vm and it stopped and just looped on 10.0.0.1.

Cheers, this makes perfect sense now thanks to that tracert command. It seems to be routing inet traffic through the vlan ip, the tracert over 30 hops merely goes to 10.0.0.1 again and again and again. So, I need a way to point inet traffic to the wan ip right?

Perhaps I'm using incorrect terminology. I did not create the vlan. When I deploy hyper-v, and select a network adapter, it disables that network adapter and creates a new one that it calls virtual network adapter. Perhaps what I'm just calling VLAN actually exists as something else, and I'm incorrect in calling it that. That's just what I named it because it's not a physical lan. Unfortunately I'm at the office and the server is at home, and it was restarted and currently hanging at the bios screen waiting for me to hit F1 because the front panel connector isn't detected. Stupid "feature" that I haven't figured out how to bypass yet. From my tinkering though, 192.168.1.101 can ping 192.168.0.1. it can rdp into it. it can rdp into every computer on either side of the network, 10.0.0.x or 192.168.0.x. However when it tries to resolve 8.8.8.8 or any external address, it times out.

Honestly, I don't know. It's a linksys srw-224. It's old, but it has always worked well for me. Perhaps I should explain what I'm doing and maybe you have a better suggestion. I have 4 1u servers on the rack that I want to consolidate onto one. One server runs DHCP & RRAS, and 3 are remote desktop servers. Not a lot of cpu being used, consumes a lot of power, and produces a lot of heat. So the plan was to replace them with a single 4u that would run DHCP, RRAS, and virtualize the other 3 servers. This is my first time playing with vlan's, and hyper-v. When I had the virtual servers in place, they worked perfectly. Migration from physical to virtual was seemless. So at that point I have the 4u running hyper-v, and one 1u running DHCP & RRAS, which connected to the switch, then to the 4u. Everything worked good. I put everything on the 4u and create a mini-network as shown in hte illistration above, and everything works. Until I restart the server. Then, the only functionality I lose is internet. All other network access works, I can remote into everything from the main server. In the past, this has always pointed to a RRAS configuration problem, however my experience with vlans is limited at best. Initially I had wanted to create a virtual network adapter for the vlan to pull ip's from LAN adapter, and not use a 3rd network card, but I couldn't figure out how. Also, I'm not sure I understand how the LAN and VLAN have the same ip. LAN is manually configured with 10.0.0.1 and VLAN adapter gets it's ip from that, as 10.0.0.15.

Hi, I have set up an isolated network for this little project until I can get it working properly. I am able to ping other machines on the mini-lan. I can remote into them. I'm not the most well versed in terminology, this is a side project, so please forgive me. Default gateway is assigned in the dhcp scope as option 003 router, and set to 10.0.0.1. Without that setting, NAT doesn't work, and things did work post setup and pre restart. Once I restarted, no internet access. I don't understand how the switch has 2 physical networks on it. If LAN is the dhcp server and VLAN is the dhcp client, I've never had to configure the switch before for this. The part that is strange to me, is that the host server does not have internet access, which makes me think it doesn't know how to send requests to the internet, so even if everything else is configured properly, nothing will work until the host can access the internet. To better illistrate it, here is a rough sketch of my network: Now, from the server in question, i can remote into any vm, the pc on that network, in addition to remote into big on the previous network. And I can do it by either IP or computer name. Thanks for your help.

I'm hoping someone can make a suggestion as I'm at a loss. I have one server with 3 NIC's, WAN, LAN, and VLAN. WAN has the internet. LAN has a static IP assigned to it. VLAN is the hyper-v network adapter. I install Hyper-V and configure it to use VLAN. Several restarts occur. Then, I install DHCP, list LAN as the adapter to bind to, set the scope, and set server option 3 to the LAN ip address. I then install Network Policy & Access, select NAT, select WAN as the adapter sourcing the internet, and LAN as the adapter to share internet with. LAN and VLAN are connected to the same switch, VLAN gets it's ip from LAN's scope. VM's get their ip from the VLAN adapter, as well as other machines connected to the switch. At this point, it looks like this: WAN IP: 192.168.1.101(DHCP) LAN IP: 10.0.0.1(Static) VLAN IP: 10.0.0.15(DHCP) VM1 IP: 10.0.0.16(DHCP) VM2 IP: 10.0.0.17(DHCP) Everything works. All computers have internet access. Then, I restart the server, and suddenly no computer has internet access. All computers receive an IP from the dhcp server, the server's WAN port receives an IP from it's DHCP server, however there is no internet access any longer. I have reconfigured close to 30 times this weekend, started from scratch, jumped through all hoops, to no avail. If someone could point me in the direction of what to check, I would appreciate it. I'm at a loss here.