Set a route to the tool’s IP forcing it through the 2nd NIC. From: Bambi J Saastad Sent: Friday, October 25, 2013 11:11 AM To: ntsysadm Subject: Re: [NTSysADM] 2 NICs on Win 7 can't access internet
Thanks all for the suggestions None of the suggestions so far fixes it. I am going to push back to the vendor and make them re-hard code a different IP on the tool Thx B On Fri, Oct 25, 2013 at 8:36 AM, Randal, Phil <[email protected]> wrote: Not directly relevant to this discussion, but have a look at KB2903590 too Packets may be sent from unexpected NIC on Multihomed Computer in Windows 7 and Windows Server 2008 R2 https://urldefense.proofpoint.com/v1/url?u=http://support.microsoft.com/kb/2903590&k=2a4Akkj3oY%2FOkjwft1MTMw%3D%3D%0A&r=huaWdlkKCLdDhy1pZhxT%2BkmBgdz%2BpN%2BUPQXytPI%2FoEI%3D%0A&m=TJa6xRUtCicCuDMxQEYFT9zeBBoqG9zUiJ58oghBL%2Fs%3D%0A&s=29e86344d0869b0c8ba472ac0522ab84d1be9b45b920bcd87c6908463946a946 Oh, the joys of multihoming. Phil -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kurt Buff Sent: 25 October 2013 13:54 To: [email protected] Subject: Re: [NTSysADM] 2 NICs on Win 7 can't access internet On Fri, Oct 25, 2013 at 4:42 AM, Bambi J Saastad <[email protected]> wrote: > I have a Window 7 pc on a tool that requires 2 NIC's > 1 NIC is used by the pc to communicate with the tool and it's TCPIP > settings are and must remain > 10.10.0.100 > 255.0.0.0 > No Gateway > > Our network is also 10.x.x.x > so LAN NIC is > 10.1.36.93 > 255.255.240.0 > 10.1.32.1 > > System can see the network and I can VNC or RDP to it from a different > subnet, though will not auto map Server shortcuts, and cannot access > the internet. > > Vendor has suggested that there is a registry setting that will put > the LAN NIC into broadcast mode and it will fix the issue, but they do > not know what this registry setting is. > I have googled for a resolution but nothing has yet fixed it. > > Does anyone have any suggestions? Yeah, that's not going to work. Per Richard and Glen, the overlapping networks will fubar you until you change one of them. Suggestions? Two come to mind o- If the NIC that is connected to the tool *absolutely* must have a /8 subnet mask, put the LAN NIC in a different RFC1918 range - either 192.168.0.0/16 or 172.16.0.0/12. If necessary, put up a separate vlan on your switches just for that machine, which is probably a good idea anyway. Make sure your router knows about it, too. o- Push harder on the manufacturer of the device, and see if you can notch down that /8 to a /30 or a /29. Gotta say, though, that if the manufacturer of that tool specifies that it can only reside in a full 10.0/8 subnet, they have no freaking idea of what they're doing. Kurt Hoople Ltd, Registered in England and Wales No. 7556595 Registered office: Plough Lane, Hereford, HR4 0LE "Any opinion expressed in this e-mail or any attached files are those of the individual and not necessarily those of Hoople Ltd. You should be aware that Hoople Ltd. monitors its email service. This e-mail and any attached files are confidential and intended solely for the use of the addressee. This communication may contain material protected by law from being passed on. If you are not the intended recipient and have received this e-mail in error, you are advised that any use, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error please contact the sender immediately and destroy all copies of it."
