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

[Jay Moritz]

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)

 

[Ron Lowe]

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.

 

[Jay Moritz]

Thanks Ron,

Worked perfectly (forcing the default gateway manually), I thought changing
the Primary DNS suffix was supposed to do the same thing, but when I did the
route print it showed the SBS machine as the default gateway.

Thanks for the help
Jay A. Moritz