Re: 1 NIC Windows 2003 Domain; 1 Wireless NIC to Internet - Can't get both working

From: Ron Lowe (ron-msng_at_{d.e.l.e.t.e.}lowe-family.me.uk)
Date: 11/06/04 

Date: Sat, 6 Nov 2004 11:46:01 -0000

"Jay Moritz" <jay_moritz@hotmail.com> wrote in message
news:uup%23Ao9wEHA.1988@TK2MSFTNGP12.phx.gbl...
>I have a computer running Windows XP Pro SP2 that needs to connect via
>standard NIC to a Windows Small Business Server 2003 Domain (192.168.16.x)
>and also needs to use a Wireless NIC to connect to the Internet
>(192.168.1.x). I have both network connections setup to use DHCP. Problem I
>am having is that if the Domain is connected Win XP is trying to send ALL
>TCP/IP traffic to the Domain and only sends the 192.168.1.x requests to the
>Wireless NIC.
>
> I have tried changing the Primary DNS suffix of the computer to the
> Wireless NIC but it still doesn't work.
> I have also tried resetting Winsock (netsh winsock reset)
>
>

This is due to the way the Default Gateway setting works.

Each connection can specify a default gateway, or obtain one from DHCP.
but only one is actually used.

The 192.168.16.x connection is taking over the default gateway.

Go to a command prompt, and ittue the command 'route print' when both are
connected, and you will probably see 2 routes listed to the 0.0.0.0
destination. Also, the automatic route metric feature may have assigned a
higher priority ( lower route metric ) to the wired connection.

With both connections using DHCP, there's limited manual configuration you
can do on the client.
I can think of 2 possible solutions, but I'm sure there are others...

1) Configure the DHCP server on the SBS machine to not issue a default
gateway.
 ( If the domain is all on one subnet, ie 192.168.16.x, then it's not
needed. )
 Then the wireless connection's Default Gateway will be the only one.
 Do a route print after this, and the only Defauly Gateway (0.0.0.0 route )
 should be the 192.168.1.x address.

 If you want to know how to do that on the DHCP server, post back.

2) Force the default gateway manually.

   This is a bit clumsy, but should work too...
   Go to a command prompt, and type:

  Route -p add 0.0.0.0 mask 0.0.0.0 192.168.1.? metric 1

( replace ? with correct IP address of the Internet gateway. )
Then do a route print again.

This will force all Internet traffic down the wireless connection to the
gateway router
you listed. The route metric of 1 should over-ride the other default routes. 

-- 
Best Regards,
Ron Lowe
MS-MVP Windows Networking

Relevant Pages

  • Re: VPN and remote gateway
    ... > It seems you use the wrong route add command. ... > when the VPN connection is established. ... > | using the remote network as my gateway. ...
    (microsoft.public.windows.server.sbs)
  • Re: AT&Ts ISP & COnnection issues
    ... info Resolving name ok for: ... Gateway Diagnostic ... action Automated repair: Reset network connection ... Wireless Diagnostic ...
    (microsoft.public.windowsxp.basics)
  • Re: 1 NIC Windows 2003 Domain; 1 Wireless NIC to Internet - Cant get both working
    ... >and also needs to use a Wireless NIC to connect to the Internet ... Each connection can specify a default gateway, ... and ittue the command 'route print' when both are ...
    (microsoft.public.windows.server.sbs)
  • Re: Network connected but no IP address
    ... To make sure that the NIS firewall isn't blocking the gateway ??router??, open NIS and add the gateway ??router?? ... To minimize any conflicts while working to resolve this issue Uninstall Any/All devices listed in Device Manager> Network Adapters. ... Shut down and remove the wireless NIC. ... What components/protocols are listed as installed in the NIC connection properties? ...
    (microsoft.public.windowsxp.general)
  • Baffling DNS Problem
    ... Network Diagnostics for Windows XP also states a DNS problem in the log ... - internet connection works just fine when switched over to my MacBook ... Gateway Diagnostic ... Wireless Diagnostic ...
    (microsoft.public.windowsxp.network_web)