New
#1
IIS not working across subnets
Hello and thank you for your time. Here is my situation. I recently got help with setting up multiple subnets on my hyper-v host server. The thread located here Configuring Static Routes Everything has been working great! Until I started testing some IIS applications.
Hyper-V Windows Server 2012 - 192.168.1.136
Guest VM - Windows Server 2008 R2 - 192.168.1.3
Guest VM - Windows Server 2008 R2 - 10.10.10.3
Guest VM - Windows 7 client - 192.168.1.9
Using the Windows 7 test client mentioned above, I can successfully access the IIS site running on 192.168.1.3. When I try to access the same IIS site on 10.10.10.3, I receive the authentication prompt, but receive a HTTP 400 Bad Request error.
I've used programs like Fiddler to watch the traffic from client to server. I really cannot figure this one out. Normally I would think it must be something in IIS for the site I'm trying to access. If that were the case, I should get the same error when I'm accessing the IIS site on 192.168.1.3. It's not until I try to cross subnets, that I encounter issues.
I'm wondering if I need some additional routing internally?
An interesting test that I did was to use my personal desktop. This desktop is a Windows 8.1 machine, not joined to the domain I have. It is in the same subnet as the hyper-v server and hyper-v guests on the 192.168.1.0/24 subnet. The desktop utilizes the same gateway, but completely different DNS server. The DNS server utilized by my desktop is my ISP's DNS.
So, my the desktop I goto http://192.168.1.3/website/page and it loads fine. I then goto http://10.10.10.3/website/page and it loads fine.
Baffling..
I wonder if this means that the routing and remote access services on the hyper-v host, which just routes LAN traffic, needs some additional help?
Quote