Multihomed Win2k8 R2 64 bit server access issues
Have a windows 2008 R2 64 bit server with two NICs. NIC1 is connected to vlan A and is configured with an IP, Subnet, gateway and DNS servers. NIC2 is connected to vlan B and is configured with an IP and subnet only. I can connect to the server thru RDP and ping it on vlan A. Cannot connect to the server thru RDP and cannot ping it on vlan B. When I am on the server I can ping the Gateway on vlan B but not vlan A Here is my routing table: C:\Users\Administrator>route print =========================================================================== Interface List 13...xx xx xx xx xx xx ......Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) #2 10...xx xx xx xx xx xx ......Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) 1...........................Software Loopback Interface 1 11...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 xx.xx.27.1 xx.xx.27.47 266 xx.xx.70.0 255.255.255.0 On-link xx.xx.70.37 266 xx.xx.70.37 255.255.255.255 On-link xx.xx.70.37 266 xx.xx.70.255 255.255.255.255 On-link xx.xx.70.37 266 xx.xx.27.0 255.255.255.0 On-link xx.xx.27.47 266 xx.xx.27.47 255.255.255.255 On-link xx.xx.27.47 266 xx.xx.27.255 255.255.255.255 On-link xx.xx.27.47 266 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link xx.xx.27.47 266 224.0.0.0 240.0.0.0 On-link xx.xx.70.37 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link xx.xx.27.47 266 255.255.255.255 255.255.255.255 On-link xx.xx.70.37 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 xx.xx.27.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 1 306 ff00::/8 On-link =========================================================================== Persistent Routes: None What am I doing wrong? I just need to be able to access the server on vlan A and vlan B. And aslo when I am on the server I need to be able to ping the gateway on vlan A and vlan B. Any help is greatly appreciated.
March 31st, 2011 5:20pm

Are these disjointed networks (no routing between them?) if so follow the instructions in this article. Multihoming a Windows Server http://networkadminkb.com/Shared%20Documents/Multihoming%20a%20Windows%20Server.aspx
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2011 5:49pm

Thanks Gunner. Had everything configured correctly except for the route addition. Just did that and same result. Any other suggestions?
March 31st, 2011 6:09pm

here is the new route table if interested: C:\Users\Administrator>route print =========================================================================== Interface List 13...xx xx xx xx xx xx ......Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) #2 10...xx xx xx xx xx xx ......Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Client) 1...........................Software Loopback Interface 1 11...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 12...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface 14...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 xx.xx.27.1 xx.xx.27.47 266 10.0.0.0 255.0.0.0 xx.xx.70.1 xx.xx.70.37 11 xx.xx.70.0 255.255.255.0 On-link xx.xx.70.37 266 xx.xx.70.37 255.255.255.255 On-link xx.xx.70.37 266 xx.xx.70.255 255.255.255.255 On-link xx.xx.70.37 266 xx.xx.27.0 255.255.255.0 On-link xx.xx.27.47 266 xx.xx.27.47 255.255.255.255 On-link xx.xx.27.47 266 xx.xx.27.255 255.255.255.255 On-link xx.xx.27.47 266 127.0.0.0 255.0.0.0 On-link 127.0.0.1 306 127.0.0.1 255.255.255.255 On-link 127.0.0.1 306 127.255.255.255 255.255.255.255 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link 127.0.0.1 306 224.0.0.0 240.0.0.0 On-link xx.xx.27.47 266 224.0.0.0 240.0.0.0 On-link xx.xx.70.37 266 255.255.255.255 255.255.255.255 On-link 127.0.0.1 306 255.255.255.255 255.255.255.255 On-link xx.xx.27.47 266 255.255.255.255 255.255.255.255 On-link xx.xx.70.37 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 10.0.0.0 255.0.0.0 xx.xx.70.1 1 0.0.0.0 0.0.0.0 xx.xx.27.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 1 306 ff00::/8 On-link =========================================================================== Persistent Routes: None
Free Windows Admin Tool Kit Click here and download it now
March 31st, 2011 6:12pm

I can connect to the server thru RDP and ping it on vlan A. Cannot connect to the server thru RDP and cannot ping it on vlan B. First, Disable the Windows Firewall Second, do all testing using the IP Addresses, and not DNS names, this will separate out issues of routing from Name resolution. Lets focus on the routing, and testing via PING. Re-test the PING commands from computers on VLAN A, B, and the mutihomed server. When I am on the server I can ping the Gateway on vlan B but not vlan A Is this still true with the updated routing table. What ip address range is VLAN A? VLAN B? These are my guesses. VLAN B = xx.xx.70.0 255.255.255.0 VLAN A = xx.xx.27.0 255.255.255.0 From the server you should be able to ping any IP Address in either VLAN A or B because the server is directly attached. Thus the gateway (xx.xx.70.1) that you entered should be for VLANS/Networks that aren't VLAN A or B. If this gateway is not responding then you are not correctly cofigured. This is usually due to an incorrect subnet mask or gateway address. Addresses on the local subnet should always work, unless you have gooffed something up. Its only the non-local/remote addresses that require the persistent routes. This seems to be the problem. The gateway and the IP Address are the same???? 0.0.0.0 0.0.0.0 xx.xx.27.1 xx.xx.27.47 <--default route ... xx.xx.27.47 255.255.255.255 On-link xx.xx.27.47 <-- broadcast for local IP Address. Given, the xx.xx i can tell, but in general unless this is VPN Client this is not possible. If this is VPN, you need to tell us. Finally, use Netstat -an and review for LISTENING on 0.0.0.0:3389 or xx.xx.70.37:3389 and xx.xx.27.47:3389 3389 is the RDP port. 0.0.0.0:3389 means RDP is listenting on all ip addresses of the server, vs a specific ip address.
March 31st, 2011 7:27pm

To answer your questions: Yes. All my testing is being done using IPs and not DNS name. Windows firewall is disabled. Even after updating the routing table, I can ping the Gateway on vlan B but not the gateway on vlan A You are correct. VLAN B = xx.xx.70.0 255.255.255.0 VLAN A = xx.xx.27.0 255.255.255.0 I deleted the xx.xx.27.47 255.255.255.255 On-link xx.xx.27.47 entry but after a reboot it comes back again. Where is it pulling this info from? netstat -an and its LISTENING on on 0.0.0.0:3389 and xx.xx.27.47:3389 but NOT on xx.xx.70.37:3389
Free Windows Admin Tool Kit Click here and download it now
April 1st, 2011 12:24am

I deleted the xx.xx.27.47 255.255.255.255 On-link xx.xx.27.47 entry but after a reboot it comes back again. This is not they way to handle this. Given your routing table this appears to be your configuration. IP: 1.1.27.47 Mask: 255.255.255.0 Gateway: 1.1.27.47 This is what i was trying to convey with my previous post. This is clearly not correct, as the IP and the Gateway are the same. Review another computers routing table to see how i infer this.
April 1st, 2011 12:51am

I assure you...I am looking at the NIC config right now for vlan A IP: xx.xx.27.47 SN: 255.255.255.0 GW: xx.xx.27.1
Free Windows Admin Tool Kit Click here and download it now
April 1st, 2011 1:01am

Oh on further review, i see my mistake. The columns were off in the routing table....sorry. If you are unable to ping 1.1.27.1 then then check the VLAN assigned to the switch port.
April 1st, 2011 1:10am

interface GigabitEthernet1/45 description TO server7 switchport switchport access vlan 27 switchport mode access spanning-tree portfast Its on the right vlan. So does the routing table look good then?
Free Windows Admin Tool Kit Click here and download it now
April 1st, 2011 1:16am

Yes, the routing table seems good. Ok, this just isn't making any sense. Strart reviewing the basics. Trace the Server7 cable and sure the cable is connected to Port 1/45, make sure there are link lights, disconnect the cable from the server and verify the port goes down on the switch, etc. ping VLAN 27 devices on the same switch, check ports stats for sent and received on the switch and on the NIC, do a network monitor capture and see what broadcast traffic you are receiving, do a ping scan of all ip addresses from 1.1.27.1 to 1.1.27.255 and see if any of them reply, etc. Hopefully, something from above will lead you in the right direction. Something is just wrong with your configuration, but it could be anything. There is no way that a device on VLAN 27 should not be able to communicate with another device on VLAN 27, especially on the same switch. If that is not working, then there is some other physical / switch issue that needs to be addressed.
April 1st, 2011 8:54am

ok. thanks gunner
Free Windows Admin Tool Kit Click here and download it now
April 1st, 2011 10:01am

Hi, as I undersood from the Thread : VLAN A: IP address: X.X.27.47 , Gateway: X.X.27.1 , DNS server VLAN B: IP address: X.X.70.30 , Gateway: NO , No DNS Server This should be the correct IP setting -------------------------- Please check this : 1. at gateway: X.X.27.1 , add route for X.X.70.0/24 send to X.X.27.47 2. at gateway: X.X.70.1 , add route for X.X.27.0/24 send to X.X.70.30 ------------------ what is the Ip of the machine that your using for RDP , Ping ? Hikmat Kanaan Amman-Jordan MCSE
April 3rd, 2011 5:17am

Hikmat: How do I do this: Please check this : 1. at gateway: X.X.27.1 , add route for X.X.70.0/24 send to X.X.27.47 2. at gateway: X.X.70.1 , add route for X.X.27.0/24 send to X.X.70.30
Free Windows Admin Tool Kit Click here and download it now
April 4th, 2011 1:59pm

what is your gateway(host) device : Cisco: on router with IP X.X.27.1: ip route X.X.70.0 255.255.255.0 X.X.27.47 on router with IP X.X.70.1: ip route X.X.27.0 255.255.255.0 X.X.70.30 ----------------------------------- MS Windows server : on host with IP X.X.27.1: route add X.X.70.0 mask 255.255.255.0 X.X.27.47 -p on host with IP X.X.70.1: route add X.X.27.0 mask 255.255.255.0 X.X.70.30 -p ------------------- I think that you dont have a route back from your gatways to this windows box Hikmat Kanaan Amman-J
April 5th, 2011 3:50pm

Hikmat; I am sorry but dont understand your query. What is my gateway device? on the x.x.27.47 it is x.x.27.1 on the x.x.35.70 it is x.x.70.1 is that what you were looking for?
Free Windows Admin Tool Kit Click here and download it now
April 6th, 2011 7:45pm

Hi Customer, I assume that your network topology is as below, please correct me if I'm wrong Internet----Gateway A(x.x.27.1)----VLAN A clients(x.x.27.x)----Server 2008( NIC1(x.x.27.47)--NIC2(x.x.70.37))----LAN B clients(x.x.70.x)-----Gateway C(x.x.70.1)-----10.0.0.0 LAN Now server 2008 route is ok, and you need check below route on two gateway (server or route?) Gateway A(x.x.27.1)----route add X.X.70.0 mask 255.255.255.0 X.X.27.47 -p Gateway C(x.x.70.1)---route add X.X.27.0 mask 255.255.255.0 X.X.70.37 -p, Gateway C(x.x.70.1)---gateway route (0.0.0.0) point to NIC2(x.x.70.37) VLAN A clients(x.x.27.x)---- gateway route point to Gateway A(x.x.27.1) VLAN B clients(x.x.70.x)----- gateway route point to Gateway C(x.x.70.1) Regards
April 7th, 2011 4:18am

I mean what is the device that is used as gatetway , is it a Cisco router or a windows server ? my pervious answer include teh command that you need to execute if you are using Cisco router or MS windows as a gateway device Hikmat Kanaan Amman-Jordan MCSE
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2011 9:25am

ahh..i see.. thanks.. OK..will check with my network engineer....
April 11th, 2011 1:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics