Microsoft Loopback adapter will not work with Windows 2008 R2
I have 3 x 2003 Server and 8 x 2008 Server SP2 where my Microsoft loopback adapters work totally fine. I have 2 new servers that are running 2008 R2 and they both have the same issue. The loopback is very important to my environment because I use a load balancer that does direct server return. This means the load balancer has a virtual IP that matches the loopback IP address. The LB gets the request forwards the request to the Real IP of the server then the server responds directly back to the request with out passing back through the LB. After installing the Legacy Hardware > network > Microsoft > loopback adapter and then assigning an IP address to the adapter I get "Access Type: No Network Access" under the Network and Sharing Center. I have gone through hundreds of forum posts and nothing seems to work. The Loopback Ip is bound to IIS and it will respond locally however when any attempts are made remotely through the load balancer there is no response. Same is true of ping of the Loopback Adapter IP, the 172.16.148.44 will respond from the local machine but not from any remote computers. Firewall is disabled. I noticed a difference in the "Remoting and Remote access" window. On all the other versions servers under the network interfaces section there are 2 entries for the loopback adapter (type: dedicated & type: loopback), however the 2008 R2 box below shows only one entry of type loopback. Any insight into this mystery would be appreciated. At this point I either need to install an older version of windows or not use this new server. Ip configuration is supplied below is for 2008 R2 Server - NOT Working C:\Users\administrator.ATGCORPORATE>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : db8 Primary Dns Suffix . . . . . . . : atgcorporate.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : atgcorporate.com Ethernet adapter Local Area Connection 5: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Loopback Adapter Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 172.16.148.44(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 172.16.148.178(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 172.16.148.180(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection 3: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #3 Physical Address. . . . . . . . . : 14-FE-B5-D2-F4-21 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::512d:535f:f338:4c7c%15(Preferred) IPv4 Address. . . . . . . . . . . : 172.16.149.8(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.192 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 370474677 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-2D-51-1C-14-FE-B5-D2-F4-1F DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #2 Physical Address. . . . . . . . . : 14-FE-B5-D2-F4-1B DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::f55e:f8cd:2c5c:97cf%13(Preferred) IPv4 Address. . . . . . . . . . . : 172.16.148.8(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 172.16.148.13(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 172.16.148.1 DHCPv6 IAID . . . . . . . . . . . : 303365813 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-2D-51-1C-14-FE-B5-D2-F4-1F DNS Servers . . . . . . . . . . . : 172.16.146.131 172.16.146.132 NetBIOS over Tcpip. . . . . . . . : Enabled ------------------------------------------------------------------- Ip configuration is supplied below is for 2008 SP2 Server - IS Working C:\Users\administrator.ATGCORPORATE>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : www3 Primary Dns Suffix . . . . . . . : atgcorporate.com Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : atgcorporate.com Ethernet adapter Local Area Connection 5: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft Loopback Adapter Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::74fc:c6ea:1d45:45a8%14(Preferred) IPv4 Address. . . . . . . . . . . : 172.16.148.162(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 172.16.148.167(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 172.16.148.172(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 172.16.148.178(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 172.16.148.180(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 172.16.148.193(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 419561548 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-79-BB-85-14-FE-B5-D9-F0-04 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection 149: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #35 Physical Address. . . . . . . . . : 14-FE-B5-D9-F0-06 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::1cb4:b5ec:29ac:80ab%11(Preferred) IPv4 Address. . . . . . . . . . . : 172.16.149.2(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.192 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 286588597 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-79-BB-85-14-FE-B5-D9-F0-04 DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom BCM5709C NetXtreme II GigE (NDIS VBD Client) #34 Physical Address. . . . . . . . . : 14-FE-B5-D9-F0-04 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::c035:e861:9f22:7619%10(Preferred) IPv4 Address. . . . . . . . . . . : 172.16.148.30(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 172.16.148.31(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 172.16.148.32(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 172.16.148.40(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 IPv4 Address. . . . . . . . . . . : 172.16.148.80(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 172.16.148.1 DHCPv6 IAID . . . . . . . . . . . : 253034165 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-15-79-BB-85-14-FE-B5-D9-F0-04 DNS Servers . . . . . . . . . . . : 172.16.146.131 NetBIOS over Tcpip. . . . . . . . : Enabled
September 22nd, 2011 12:00pm

Hi bhalbach, Thanks for posting here. For me, it seems like a source address and routing selecting issue on client , could you try to verify the interface binding order on problematic and compare with the settings on non-problematic server and correct it to see how is going, please also post the route table form both host here. For more information please refer to the old thread below: http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/fe2848aa-f68d-47e3-b48d-068b55fa19db/ Thanks. Tiger Li Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
September 26th, 2011 8:27am

Sorry for delay: didn't see your reply, but I am still having the issue. Binding order for both systems are loopback adapters always are bound before the physical connections. routing tables you requested are below. Routing Table for 2008 R2 system not working: C:\Users\administrator.ATGCORPORATE>route print =========================================================================== Interface List 16...02 00 4c 4f 4f 50 ......Microsoft Loopback Adapter #2 10...78 2b cb 45 68 b6 ......Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Clie nt) #34 1...........................Software Loopback Interface 1 11...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 13...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 172.16.148.1 172.16.148.150 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 172.16.148.0 255.255.255.0 On-link 172.16.148.165 286 172.16.148.0 255.255.255.0 On-link 172.16.148.150 266 172.16.148.150 255.255.255.255 On-link 172.16.148.150 266 172.16.148.151 255.255.255.255 On-link 172.16.148.150 266 172.16.148.152 255.255.255.255 On-link 172.16.148.150 266 172.16.148.153 255.255.255.255 On-link 172.16.148.150 266 172.16.148.157 255.255.255.255 On-link 172.16.148.150 266 172.16.148.165 255.255.255.255 On-link 172.16.148.165 286 172.16.148.255 255.255.255.255 On-link 172.16.148.165 286 172.16.148.255 255.255.255.255 On-link 172.16.148.150 266 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 172.16.148.150 266 224.0.0.0 240.0.0.0 On-link 172.16.148.165 286 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 172.16.148.150 266 255.255.255.255 255.255.255.255 On-link 172.16.148.165 286 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 172.16.148.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 10 266 fe80::/64 On-link 10 266 fe80::94bf:7d29:d08c:a016/128 On-link 1 306 ff00::/8 On-link 10 266 ff00::/8 On-link =========================================================================== Persistent Routes: None Routing Table for working connection Server 2008 SP2 C:\Users\administrator.ATGCORPORATE>route print =========================================================================== Interface List 17 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter #5 16 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter #4 15 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter #3 14 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter #2 13 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter 11 ...00 1e c9 b2 65 42 ...... Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Cl ient) #2 10 ...00 1e c9 b2 65 40 ...... Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Cl ient) 1 ........................... Software Loopback Interface 1 12 ...00 00 00 00 00 00 00 e0 isatap.{ABB03F4F-FBA2-4DBB-9216-156171BDB20E} 28 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 18 ...00 00 00 00 00 00 00 e0 isatap.{75DA9511-89C7-4DCB-B076-E972C4B64378} 19 ...00 00 00 00 00 00 00 e0 isatap.{EB3E6ADC-DC6C-42AE-920E-B64BD5A00034} 20 ...00 00 00 00 00 00 00 e0 isatap.{E60B3B8D-2CD9-49BC-A6D7-2B88E9A61CFD} 21 ...00 00 00 00 00 00 00 e0 isatap.{0C976E9F-1230-4047-B0CE-77A52FE344DD} 22 ...00 00 00 00 00 00 00 e0 isatap.{8A48FE5B-4D39-48BF-9AFE-F96336233205} =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 172.16.148.1 172.16.148.90 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 172.16.0.0 255.255.0.0 172.16.148.1 172.16.148.90 266 172.16.148.0 255.255.255.0 On-link 172.16.148.171 286 172.16.148.0 255.255.255.0 On-link 172.16.148.168 286 172.16.148.0 255.255.255.0 On-link 172.16.148.169 286 172.16.148.0 255.255.255.0 On-link 172.16.148.166 286 172.16.148.0 255.255.255.0 On-link 172.16.148.162 286 172.16.148.0 255.255.255.0 On-link 172.16.148.90 266 172.16.148.90 255.255.255.255 On-link 172.16.148.90 266 172.16.148.91 255.255.255.255 On-link 172.16.148.90 266 172.16.148.92 255.255.255.255 On-link 172.16.148.90 266 172.16.148.93 255.255.255.255 On-link 172.16.148.90 266 172.16.148.94 255.255.255.255 On-link 172.16.148.90 266 172.16.148.95 255.255.255.255 On-link 172.16.148.90 266 172.16.148.96 255.255.255.255 On-link 172.16.148.90 266 172.16.148.97 255.255.255.255 On-link 172.16.148.90 266 172.16.148.98 255.255.255.255 On-link 172.16.148.90 266 172.16.148.99 255.255.255.255 On-link 172.16.148.90 266 172.16.148.162 255.255.255.255 On-link 172.16.148.162 286 172.16.148.165 255.255.255.255 On-link 172.16.148.162 286 172.16.148.166 255.255.255.255 On-link 172.16.148.166 286 172.16.148.167 255.255.255.255 On-link 172.16.148.166 286 172.16.148.168 255.255.255.255 On-link 172.16.148.168 286 172.16.148.169 255.255.255.255 On-link 172.16.148.169 286 172.16.148.171 255.255.255.255 On-link 172.16.148.171 286 172.16.148.172 255.255.255.255 On-link 172.16.148.171 286 172.16.148.173 255.255.255.255 On-link 172.16.148.171 286 172.16.148.174 255.255.255.255 On-link 172.16.148.171 286 172.16.148.175 255.255.255.255 On-link 172.16.148.171 286 172.16.148.176 255.255.255.255 On-link 172.16.148.168 286 172.16.148.177 255.255.255.255 On-link 172.16.148.171 286 172.16.148.178 255.255.255.255 On-link 172.16.148.171 286 172.16.148.179 255.255.255.255 On-link 172.16.148.168 286 172.16.148.191 255.255.255.255 On-link 172.16.148.162 286 172.16.148.192 255.255.255.255 On-link 172.16.148.162 286 172.16.148.193 255.255.255.255 On-link 172.16.148.162 286 172.16.148.194 255.255.255.255 On-link 172.16.148.162 286 172.16.148.196 255.255.255.255 On-link 172.16.148.162 286 172.16.148.198 255.255.255.255 On-link 172.16.148.162 286 172.16.148.199 255.255.255.255 On-link 172.16.148.162 286 172.16.148.255 255.255.255.255 On-link 172.16.148.171 286 172.16.148.255 255.255.255.255 On-link 172.16.148.168 286 172.16.148.255 255.255.255.255 On-link 172.16.148.169 286 172.16.148.255 255.255.255.255 On-link 172.16.148.166 286 172.16.148.255 255.255.255.255 On-link 172.16.148.162 286 172.16.148.255 255.255.255.255 On-link 172.16.148.90 266 172.16.149.0 255.255.255.192 On-link 172.16.149.15 266 172.16.149.15 255.255.255.255 On-link 172.16.149.15 266 172.16.149.63 255.255.255.255 On-link 172.16.149.15 266 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 172.16.148.162 286 224.0.0.0 240.0.0.0 On-link 172.16.148.166 286 224.0.0.0 240.0.0.0 On-link 172.16.148.169 286 224.0.0.0 240.0.0.0 On-link 172.16.148.168 286 224.0.0.0 240.0.0.0 On-link 172.16.148.171 286 224.0.0.0 240.0.0.0 On-link 172.16.148.90 266 224.0.0.0 240.0.0.0 On-link 172.16.149.15 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 172.16.148.162 286 255.255.255.255 255.255.255.255 On-link 172.16.148.166 286 255.255.255.255 255.255.255.255 On-link 172.16.148.169 286 255.255.255.255 255.255.255.255 On-link 172.16.148.168 286 255.255.255.255 255.255.255.255 On-link 172.16.148.171 286 255.255.255.255 255.255.255.255 On-link 172.16.148.90 266 255.255.255.255 255.255.255.255 On-link 172.16.149.15 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 172.16.148.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 13 286 fe80::/64 On-link 14 286 fe80::/64 On-link 15 286 fe80::/64 On-link 16 286 fe80::/64 On-link 17 286 fe80::/64 On-link 10 266 fe80::/64 On-link 11 266 fe80::/64 On-link 13 286 fe80::97f:89be:c1b1:530/128 On-link 16 286 fe80::59b8:7627:e522:4221/128 On-link 17 286 fe80::68b9:90dd:858c:c2d5/128 On-link 14 286 fe80::690e:5f85:e24f:65/128 On-link 15 286 fe80::d4b8:6306:689:6bdc/128 On-link 11 266 fe80::d57c:6e51:2d8b:3307/128 On-link 10 266 fe80::e9a0:1408:b38f:40fe/128 On-link 1 306 ff00::/8 On-link 13 286 ff00::/8 On-link 14 286 ff00::/8 On-link 15 286 ff00::/8 On-link 16 286 ff00::/8 On-link 17 286 ff00::/8 On-link 10 266 ff00::/8 On-link 11 266 ff00::/8 On-link =========================================================================== Persistent Routes: None
November 3rd, 2011 7:39pm

Sorry for delay: didn't see your reply, but I am still having the issue. Binding order for both systems are loopback adapters always are bound before the physical connections. routing tables you requested are below. Routing Table for 2008 R2 system not working: C:\Users\administrator.ATGCORPORATE>route print =========================================================================== Interface List 16...02 00 4c 4f 4f 50 ......Microsoft Loopback Adapter #2 10...78 2b cb 45 68 b6 ......Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Clie nt) #34 1...........................Software Loopback Interface 1 11...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 13...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 172.16.148.1 172.16.148.150 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 172.16.148.0 255.255.255.0 On-link 172.16.148.165 286 172.16.148.0 255.255.255.0 On-link 172.16.148.150 266 172.16.148.150 255.255.255.255 On-link 172.16.148.150 266 172.16.148.151 255.255.255.255 On-link 172.16.148.150 266 172.16.148.152 255.255.255.255 On-link 172.16.148.150 266 172.16.148.153 255.255.255.255 On-link 172.16.148.150 266 172.16.148.157 255.255.255.255 On-link 172.16.148.150 266 172.16.148.165 255.255.255.255 On-link 172.16.148.165 286 172.16.148.255 255.255.255.255 On-link 172.16.148.165 286 172.16.148.255 255.255.255.255 On-link 172.16.148.150 266 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 172.16.148.150 266 224.0.0.0 240.0.0.0 On-link 172.16.148.165 286 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 172.16.148.150 266 255.255.255.255 255.255.255.255 On-link 172.16.148.165 286 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 172.16.148.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 10 266 fe80::/64 On-link 10 266 fe80::94bf:7d29:d08c:a016/128 On-link 1 306 ff00::/8 On-link 10 266 ff00::/8 On-link =========================================================================== Persistent Routes: None Routing Table for working connection Server 2008 SP2 C:\Users\administrator.ATGCORPORATE>route print =========================================================================== Interface List 17 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter #5 16 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter #4 15 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter #3 14 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter #2 13 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter 11 ...00 1e c9 b2 65 42 ...... Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Cl ient) #2 10 ...00 1e c9 b2 65 40 ...... Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Cl ient) 1 ........................... Software Loopback Interface 1 12 ...00 00 00 00 00 00 00 e0 isatap.{ABB03F4F-FBA2-4DBB-9216-156171BDB20E} 28 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 18 ...00 00 00 00 00 00 00 e0 isatap.{75DA9511-89C7-4DCB-B076-E972C4B64378} 19 ...00 00 00 00 00 00 00 e0 isatap.{EB3E6ADC-DC6C-42AE-920E-B64BD5A00034} 20 ...00 00 00 00 00 00 00 e0 isatap.{E60B3B8D-2CD9-49BC-A6D7-2B88E9A61CFD} 21 ...00 00 00 00 00 00 00 e0 isatap.{0C976E9F-1230-4047-B0CE-77A52FE344DD} 22 ...00 00 00 00 00 00 00 e0 isatap.{8A48FE5B-4D39-48BF-9AFE-F96336233205} =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 172.16.148.1 172.16.148.90 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 172.16.0.0 255.255.0.0 172.16.148.1 172.16.148.90 266 172.16.148.0 255.255.255.0 On-link 172.16.148.171 286 172.16.148.0 255.255.255.0 On-link 172.16.148.168 286 172.16.148.0 255.255.255.0 On-link 172.16.148.169 286 172.16.148.0 255.255.255.0 On-link 172.16.148.166 286 172.16.148.0 255.255.255.0 On-link 172.16.148.162 286 172.16.148.0 255.255.255.0 On-link 172.16.148.90 266 172.16.148.90 255.255.255.255 On-link 172.16.148.90 266 172.16.148.91 255.255.255.255 On-link 172.16.148.90 266 172.16.148.92 255.255.255.255 On-link 172.16.148.90 266 172.16.148.93 255.255.255.255 On-link 172.16.148.90 266 172.16.148.94 255.255.255.255 On-link 172.16.148.90 266 172.16.148.95 255.255.255.255 On-link 172.16.148.90 266 172.16.148.96 255.255.255.255 On-link 172.16.148.90 266 172.16.148.97 255.255.255.255 On-link 172.16.148.90 266 172.16.148.98 255.255.255.255 On-link 172.16.148.90 266 172.16.148.99 255.255.255.255 On-link 172.16.148.90 266 172.16.148.162 255.255.255.255 On-link 172.16.148.162 286 172.16.148.165 255.255.255.255 On-link 172.16.148.162 286 172.16.148.166 255.255.255.255 On-link 172.16.148.166 286 172.16.148.167 255.255.255.255 On-link 172.16.148.166 286 172.16.148.168 255.255.255.255 On-link 172.16.148.168 286 172.16.148.169 255.255.255.255 On-link 172.16.148.169 286 172.16.148.171 255.255.255.255 On-link 172.16.148.171 286 172.16.148.172 255.255.255.255 On-link 172.16.148.171 286 172.16.148.173 255.255.255.255 On-link 172.16.148.171 286 172.16.148.174 255.255.255.255 On-link 172.16.148.171 286 172.16.148.175 255.255.255.255 On-link 172.16.148.171 286 172.16.148.176 255.255.255.255 On-link 172.16.148.168 286 172.16.148.177 255.255.255.255 On-link 172.16.148.171 286 172.16.148.178 255.255.255.255 On-link 172.16.148.171 286 172.16.148.179 255.255.255.255 On-link 172.16.148.168 286 172.16.148.191 255.255.255.255 On-link 172.16.148.162 286 172.16.148.192 255.255.255.255 On-link 172.16.148.162 286 172.16.148.193 255.255.255.255 On-link 172.16.148.162 286 172.16.148.194 255.255.255.255 On-link 172.16.148.162 286 172.16.148.196 255.255.255.255 On-link 172.16.148.162 286 172.16.148.198 255.255.255.255 On-link 172.16.148.162 286 172.16.148.199 255.255.255.255 On-link 172.16.148.162 286 172.16.148.255 255.255.255.255 On-link 172.16.148.171 286 172.16.148.255 255.255.255.255 On-link 172.16.148.168 286 172.16.148.255 255.255.255.255 On-link 172.16.148.169 286 172.16.148.255 255.255.255.255 On-link 172.16.148.166 286 172.16.148.255 255.255.255.255 On-link 172.16.148.162 286 172.16.148.255 255.255.255.255 On-link 172.16.148.90 266 172.16.149.0 255.255.255.192 On-link 172.16.149.15 266 172.16.149.15 255.255.255.255 On-link 172.16.149.15 266 172.16.149.63 255.255.255.255 On-link 172.16.149.15 266 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 172.16.148.162 286 224.0.0.0 240.0.0.0 On-link 172.16.148.166 286 224.0.0.0 240.0.0.0 On-link 172.16.148.169 286 224.0.0.0 240.0.0.0 On-link 172.16.148.168 286 224.0.0.0 240.0.0.0 On-link 172.16.148.171 286 224.0.0.0 240.0.0.0 On-link 172.16.148.90 266 224.0.0.0 240.0.0.0 On-link 172.16.149.15 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 172.16.148.162 286 255.255.255.255 255.255.255.255 On-link 172.16.148.166 286 255.255.255.255 255.255.255.255 On-link 172.16.148.169 286 255.255.255.255 255.255.255.255 On-link 172.16.148.168 286 255.255.255.255 255.255.255.255 On-link 172.16.148.171 286 255.255.255.255 255.255.255.255 On-link 172.16.148.90 266 255.255.255.255 255.255.255.255 On-link 172.16.149.15 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 172.16.148.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 13 286 fe80::/64 On-link 14 286 fe80::/64 On-link 15 286 fe80::/64 On-link 16 286 fe80::/64 On-link 17 286 fe80::/64 On-link 10 266 fe80::/64 On-link 11 266 fe80::/64 On-link 13 286 fe80::97f:89be:c1b1:530/128 On-link 16 286 fe80::59b8:7627:e522:4221/128 On-link 17 286 fe80::68b9:90dd:858c:c2d5/128 On-link 14 286 fe80::690e:5f85:e24f:65/128 On-link 15 286 fe80::d4b8:6306:689:6bdc/128 On-link 11 266 fe80::d57c:6e51:2d8b:3307/128 On-link 10 266 fe80::e9a0:1408:b38f:40fe/128 On-link 1 306 ff00::/8 On-link 13 286 ff00::/8 On-link 14 286 ff00::/8 On-link 15 286 ff00::/8 On-link 16 286 ff00::/8 On-link 17 286 ff00::/8 On-link 10 266 ff00::/8 On-link 11 266 ff00::/8 On-link =========================================================================== Persistent Routes: None
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2011 7:39pm

Sorry for delay: didn't see your reply, but I am still having the issue. Binding order for both systems are loopback adapters always are bound before the physical connections. routing tables you requested are below. Routing Table for 2008 R2 system not working: C:\Users\administrator.ATGCORPORATE>route print =========================================================================== Interface List 16...02 00 4c 4f 4f 50 ......Microsoft Loopback Adapter #2 10...78 2b cb 45 68 b6 ......Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Clie nt) #34 1...........................Software Loopback Interface 1 11...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter 13...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 172.16.148.1 172.16.148.150 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 172.16.148.0 255.255.255.0 On-link 172.16.148.165 286 172.16.148.0 255.255.255.0 On-link 172.16.148.150 266 172.16.148.150 255.255.255.255 On-link 172.16.148.150 266 172.16.148.151 255.255.255.255 On-link 172.16.148.150 266 172.16.148.152 255.255.255.255 On-link 172.16.148.150 266 172.16.148.153 255.255.255.255 On-link 172.16.148.150 266 172.16.148.157 255.255.255.255 On-link 172.16.148.150 266 172.16.148.165 255.255.255.255 On-link 172.16.148.165 286 172.16.148.255 255.255.255.255 On-link 172.16.148.165 286 172.16.148.255 255.255.255.255 On-link 172.16.148.150 266 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 172.16.148.150 266 224.0.0.0 240.0.0.0 On-link 172.16.148.165 286 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 172.16.148.150 266 255.255.255.255 255.255.255.255 On-link 172.16.148.165 286 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 172.16.148.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 10 266 fe80::/64 On-link 10 266 fe80::94bf:7d29:d08c:a016/128 On-link 1 306 ff00::/8 On-link 10 266 ff00::/8 On-link =========================================================================== Persistent Routes: None Routing Table for working connection Server 2008 SP2 C:\Users\administrator.ATGCORPORATE>route print =========================================================================== Interface List 17 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter #5 16 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter #4 15 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter #3 14 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter #2 13 ...02 00 4c 4f 4f 50 ...... Microsoft Loopback Adapter 11 ...00 1e c9 b2 65 42 ...... Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Cl ient) #2 10 ...00 1e c9 b2 65 40 ...... Broadcom BCM5708C NetXtreme II GigE (NDIS VBD Cl ient) 1 ........................... Software Loopback Interface 1 12 ...00 00 00 00 00 00 00 e0 isatap.{ABB03F4F-FBA2-4DBB-9216-156171BDB20E} 28 ...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2 18 ...00 00 00 00 00 00 00 e0 isatap.{75DA9511-89C7-4DCB-B076-E972C4B64378} 19 ...00 00 00 00 00 00 00 e0 isatap.{EB3E6ADC-DC6C-42AE-920E-B64BD5A00034} 20 ...00 00 00 00 00 00 00 e0 isatap.{E60B3B8D-2CD9-49BC-A6D7-2B88E9A61CFD} 21 ...00 00 00 00 00 00 00 e0 isatap.{0C976E9F-1230-4047-B0CE-77A52FE344DD} 22 ...00 00 00 00 00 00 00 e0 isatap.{8A48FE5B-4D39-48BF-9AFE-F96336233205} =========================================================================== IPv4 Route Table =========================================================================== Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 172.16.148.1 172.16.148.90 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 172.16.0.0 255.255.0.0 172.16.148.1 172.16.148.90 266 172.16.148.0 255.255.255.0 On-link 172.16.148.171 286 172.16.148.0 255.255.255.0 On-link 172.16.148.168 286 172.16.148.0 255.255.255.0 On-link 172.16.148.169 286 172.16.148.0 255.255.255.0 On-link 172.16.148.166 286 172.16.148.0 255.255.255.0 On-link 172.16.148.162 286 172.16.148.0 255.255.255.0 On-link 172.16.148.90 266 172.16.148.90 255.255.255.255 On-link 172.16.148.90 266 172.16.148.91 255.255.255.255 On-link 172.16.148.90 266 172.16.148.92 255.255.255.255 On-link 172.16.148.90 266 172.16.148.93 255.255.255.255 On-link 172.16.148.90 266 172.16.148.94 255.255.255.255 On-link 172.16.148.90 266 172.16.148.95 255.255.255.255 On-link 172.16.148.90 266 172.16.148.96 255.255.255.255 On-link 172.16.148.90 266 172.16.148.97 255.255.255.255 On-link 172.16.148.90 266 172.16.148.98 255.255.255.255 On-link 172.16.148.90 266 172.16.148.99 255.255.255.255 On-link 172.16.148.90 266 172.16.148.162 255.255.255.255 On-link 172.16.148.162 286 172.16.148.165 255.255.255.255 On-link 172.16.148.162 286 172.16.148.166 255.255.255.255 On-link 172.16.148.166 286 172.16.148.167 255.255.255.255 On-link 172.16.148.166 286 172.16.148.168 255.255.255.255 On-link 172.16.148.168 286 172.16.148.169 255.255.255.255 On-link 172.16.148.169 286 172.16.148.171 255.255.255.255 On-link 172.16.148.171 286 172.16.148.172 255.255.255.255 On-link 172.16.148.171 286 172.16.148.173 255.255.255.255 On-link 172.16.148.171 286 172.16.148.174 255.255.255.255 On-link 172.16.148.171 286 172.16.148.175 255.255.255.255 On-link 172.16.148.171 286 172.16.148.176 255.255.255.255 On-link 172.16.148.168 286 172.16.148.177 255.255.255.255 On-link 172.16.148.171 286 172.16.148.178 255.255.255.255 On-link 172.16.148.171 286 172.16.148.179 255.255.255.255 On-link 172.16.148.168 286 172.16.148.191 255.255.255.255 On-link 172.16.148.162 286 172.16.148.192 255.255.255.255 On-link 172.16.148.162 286 172.16.148.193 255.255.255.255 On-link 172.16.148.162 286 172.16.148.194 255.255.255.255 On-link 172.16.148.162 286 172.16.148.196 255.255.255.255 On-link 172.16.148.162 286 172.16.148.198 255.255.255.255 On-link 172.16.148.162 286 172.16.148.199 255.255.255.255 On-link 172.16.148.162 286 172.16.148.255 255.255.255.255 On-link 172.16.148.171 286 172.16.148.255 255.255.255.255 On-link 172.16.148.168 286 172.16.148.255 255.255.255.255 On-link 172.16.148.169 286 172.16.148.255 255.255.255.255 On-link 172.16.148.166 286 172.16.148.255 255.255.255.255 On-link 172.16.148.162 286 172.16.148.255 255.255.255.255 On-link 172.16.148.90 266 172.16.149.0 255.255.255.192 On-link 172.16.149.15 266 172.16.149.15 255.255.255.255 On-link 172.16.149.15 266 172.16.149.63 255.255.255.255 On-link 172.16.149.15 266 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 172.16.148.162 286 224.0.0.0 240.0.0.0 On-link 172.16.148.166 286 224.0.0.0 240.0.0.0 On-link 172.16.148.169 286 224.0.0.0 240.0.0.0 On-link 172.16.148.168 286 224.0.0.0 240.0.0.0 On-link 172.16.148.171 286 224.0.0.0 240.0.0.0 On-link 172.16.148.90 266 224.0.0.0 240.0.0.0 On-link 172.16.149.15 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 172.16.148.162 286 255.255.255.255 255.255.255.255 On-link 172.16.148.166 286 255.255.255.255 255.255.255.255 On-link 172.16.148.169 286 255.255.255.255 255.255.255.255 On-link 172.16.148.168 286 255.255.255.255 255.255.255.255 On-link 172.16.148.171 286 255.255.255.255 255.255.255.255 On-link 172.16.148.90 266 255.255.255.255 255.255.255.255 On-link 172.16.149.15 266 =========================================================================== Persistent Routes: Network Address Netmask Gateway Address Metric 0.0.0.0 0.0.0.0 172.16.148.1 Default =========================================================================== IPv6 Route Table =========================================================================== Active Routes: If Metric Network Destination Gateway 1 306 ::1/128 On-link 13 286 fe80::/64 On-link 14 286 fe80::/64 On-link 15 286 fe80::/64 On-link 16 286 fe80::/64 On-link 17 286 fe80::/64 On-link 10 266 fe80::/64 On-link 11 266 fe80::/64 On-link 13 286 fe80::97f:89be:c1b1:530/128 On-link 16 286 fe80::59b8:7627:e522:4221/128 On-link 17 286 fe80::68b9:90dd:858c:c2d5/128 On-link 14 286 fe80::690e:5f85:e24f:65/128 On-link 15 286 fe80::d4b8:6306:689:6bdc/128 On-link 11 266 fe80::d57c:6e51:2d8b:3307/128 On-link 10 266 fe80::e9a0:1408:b38f:40fe/128 On-link 1 306 ff00::/8 On-link 13 286 ff00::/8 On-link 14 286 ff00::/8 On-link 15 286 ff00::/8 On-link 16 286 ff00::/8 On-link 17 286 ff00::/8 On-link 10 266 ff00::/8 On-link 11 266 ff00::/8 On-link =========================================================================== Persistent Routes: None
November 3rd, 2011 7:48pm

I can also reproduce this on multiple machines... Can you attempt the following on one of your Windows 2008 Server R2 machines possibly? Add legacy > Network adapter > Microsoft > loop back adapter Configure the IP address to be on the same network as physical adapter. Enter nothing into the gateway or DNS fields under the IP configuration. Then to test I use the following procedure. Assuming IIS is installed: I browse with a webserver locally from the same machine and enter the IP address that is bound to the loopback adapter. IIS will respond with the default page. Then test this loopback IP address from a different external computer by using a webbrowser. In my experience with the 3 different servers I have tried it does not ever respond. They all show "No network access"
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2011 8:03pm

I can also reproduce this on multiple machines... Can you attempt the following on one of your Windows 2008 Server R2 machines possibly? Add legacy > Network adapter > Microsoft > loop back adapter Configure the IP address to be on the same network as physical adapter. Enter nothing into the gateway or DNS fields under the IP configuration. Then to test I use the following procedure. Assuming IIS is installed: I browse with a webserver locally from the same machine and enter the IP address that is bound to the loopback adapter. IIS will respond with the default page. Then test this loopback IP address from a different external computer by using a webbrowser. In my experience with the 3 different servers I have tried it does not ever respond. They all show "No network access"
November 3rd, 2011 8:03pm

I can also reproduce this on multiple machines... Can you attempt the following on one of your Windows 2008 Server R2 machines possibly? Add legacy > Network adapter > Microsoft > loop back adapter Configure the IP address to be on the same network as physical adapter. Enter nothing into the gateway or DNS fields under the IP configuration. Then to test I use the following procedure. Assuming IIS is installed: I browse with a webserver locally from the same machine and enter the IP address that is bound to the loopback adapter. IIS will respond with the default page. Then test this loopback IP address from a different external computer by using a webbrowser. In my experience with the 3 different servers I have tried it does not ever respond. They all show "No network access"
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2011 8:12pm

Hi, I have a very similar problem. I'm trying to setup direct server return on my Radware load balancers (they call it Triangulation I believe). I have 4 x Windows Server 2008 R2 servers that I need to setup a loopback adaptor on. I've followed the MS instructions on how to do this, and the adaptors are installed and I have then assigned the same VIP that exists on the load balancers to the loopback adaptor. This all seems to be working from an operating system level, in that I'm not seeing any errors in the logs etc. However, when I then try to spray this traffic across the servers from the HLB, I just don't get any response. If I try to the same setup on a Windows Server2 2003 server, it works fine. I can connect to the VIP, and which in turns sprays to the server, and gets a response from the loopback. I've read the link above, and have tried experimenting with IP addresses (lower/higher etc), but without luck. If there any way to get the loopback adapter functioning on Windows Server 2008 R2? Regards, James. James Frost
November 3rd, 2011 8:32pm

Hi, I have a very similar problem. I'm trying to setup direct server return on my Radware load balancers (they call it Triangulation I believe). I have 4 x Windows Server 2008 R2 servers that I need to setup a loopback adaptor on. I've followed the MS instructions on how to do this, and the adaptors are installed and I have then assigned the same VIP that exists on the load balancers to the loopback adaptor. This all seems to be working from an operating system level, in that I'm not seeing any errors in the logs etc. However, when I then try to spray this traffic across the servers from the HLB, I just don't get any response. If I try to the same setup on a Windows Server2 2003 server, it works fine. I can connect to the VIP, and which in turns sprays to the server, and gets a response from the loopback. I've read the link above, and have tried experimenting with IP addresses (lower/higher etc), but without luck. If there any way to get the loopback adapter functioning on Windows Server 2008 R2? Regards, James. James Frost
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2011 8:32pm

Hi, I have a very similar problem. I'm trying to setup direct server return on my Radware load balancers (they call it Triangulation I believe). I have 4 x Windows Server 2008 R2 servers that I need to setup a loopback adaptor on. I've followed the MS instructions on how to do this, and the adaptors are installed and I have then assigned the same VIP that exists on the load balancers to the loopback adaptor. This all seems to be working from an operating system level, in that I'm not seeing any errors in the logs etc. However, when I then try to spray this traffic across the servers from the HLB, I just don't get any response. If I try to the same setup on a Windows Server2 2003 server, it works fine. I can connect to the VIP, and which in turns sprays to the server, and gets a response from the loopback. I've read the link above, and have tried experimenting with IP addresses (lower/higher etc), but without luck. If there any way to get the loopback adapter functioning on Windows Server 2008 R2? Regards, James. James Frost
November 3rd, 2011 8:41pm

Glad I am not alone on this one... It totally looks like a windows 2008 R2 bug... I have had more problems with the R2 build of the OS then any windows server OS over the last 6 years...
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2011 10:43am

Glad I am not alone on this one... It totally looks like a windows 2008 R2 bug... I have had more problems with the R2 build of the OS then any windows server OS over the last 6 years...
November 4th, 2011 10:43am

Glad I am not alone on this one... It totally looks like a windows 2008 R2 bug... I have had more problems with the R2 build of the OS then any windows server OS over the last 6 years...
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2011 10:51am

I think that you will find that it was an intentional change, not a bug. There were lots of networking changes from 2003 including tightening the security. Server 2008 R2 is much fussier about where a reply comes from. It expects to receive a reply from the IP the packet was sent to. Bill
November 4th, 2011 8:09pm

I think that you will find that it was an intentional change, not a bug. There were lots of networking changes from 2003 including tightening the security. Server 2008 R2 is much fussier about where a reply comes from. It expects to receive a reply from the IP the packet was sent to. Bill
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2011 8:09pm

I think that you will find that it was an intentional change, not a bug. There were lots of networking changes from 2003 including tightening the security. Server 2008 R2 is much fussier about where a reply comes from. It expects to receive a reply from the IP the packet was sent to. Bill
November 4th, 2011 8:17pm

I think I’ve got this working. I had to change some NIC properties (http://blog.loadbalancer.org/direct-server-return-on-windows-2008-using-loopback-adpter/) before the loopback would return the response: · netsh interface ipv4 set interface "net" weakhostreceive=enabled · netsh interface ipv4 set interface "loopback" weakhostreceive=enabled · netsh interface ipv4 set interface "loopback" weakhostsend=enabled Once I did this, I can now connect through to the VIP on any of the defined ports using Triangulation (Direct Server Return). Regards, James James Frost
Free Windows Admin Tool Kit Click here and download it now
November 6th, 2011 6:12pm

That should indeed do the trick. 2003 used the weak host model. By default 2008 uses the strong host model (which requires a reply to come from the target IP). http://www.networkworld.com/community/node/42699 Bill
November 6th, 2011 6:54pm

That should indeed do the trick. 2003 used the weak host model. By default 2008 uses the strong host model (which requires a reply to come from the target IP). http://www.networkworld.com/community/node/42699 Bill
Free Windows Admin Tool Kit Click here and download it now
November 6th, 2011 6:54pm

That should indeed do the trick. 2003 used the weak host model. By default 2008 uses the strong host model (which requires a reply to come from the target IP). http://www.networkworld.com/community/node/42699 Bill
November 6th, 2011 7:03pm

I already have a case open with PSS on this. I will put these settings to them to see what the implications are of enabling them (if any). I'll post the results.James Frost
Free Windows Admin Tool Kit Click here and download it now
November 6th, 2011 8:21pm

I already have a case open with PSS on this. I will put these settings to them to see what the implications are of enabling them (if any). I'll post the results.James Frost
November 6th, 2011 8:21pm

I already have a case open with PSS on this. I will put these settings to them to see what the implications are of enabling them (if any). I'll post the results.James Frost
Free Windows Admin Tool Kit Click here and download it now
November 6th, 2011 8:30pm

Wow... Thanks. That totaly did the trick for me. I looked for hours to find something like this. Tightened security was the thing. Thanks for showing me how to unlock it. Brad
November 7th, 2011 11:51am

Wow... Thanks. That totaly did the trick for me. I looked for hours to find something like this. Tightened security was the thing. Thanks for showing me how to unlock it. Brad
Free Windows Admin Tool Kit Click here and download it now
November 7th, 2011 11:51am

Wow... Thanks. That totaly did the trick for me. I looked for hours to find something like this. Tightened security was the thing. Thanks for showing me how to unlock it. Brad
November 7th, 2011 12:00pm

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

Other recent topics Other recent topics