Question : Gateway setting changes with Manually configured IP

I have a SBS 2003 domain, single nic setup (192.168.16.x). My company recently expanded into a second building a couple blocks away, so I added a pair of cisco pix 501 and setup a VPN.
The new site is 192.168.17.x. I installed a ws2K3 member server at the new site for file server/printer server roles. It's not a domain controller, no DNS, no DHCP. I have the server ip manually set to:

192.168.17.2
255.255.255.0
192.168.17.1 (local pix)

DNS
192.168.16.2 (sbs domain controller)

My problem is that the gateway on this server changes to 192.168.16.1 (the pix at the other site) or sometimes is completely blank. I've looked at Ipconfig /all and the DHCP Enable = NO. I've looked in the "advanced" tab and only the correct gateway is shown.
This seems to happen more frequently if I am remotely connecting to the computer via RDC. I'm connecting from workstaions in the 192.168.17.X subnet so I can't see how they could be causing the problem.

The 192.168.17.1 pix is handling DHCP duties on this subnet and it is setup to supply the correct 17.x gateway since all the workstations have been working fine for over a month now.

I have a fair amount of networking experience especially with WS2K3 but I can't think of anything that should be able override a manual setting.  

My next move is going to be slapping some old hardware together and putting a second member server in the 192.168.17.X subnet and see if it also has this problem. Then I'll at least know if it's the machine or the network.

any help would be greatly appreciated!

-Ralph

I previously posted this in the WS 2003 area but only got 1 response this week. Being a newbie here I didn't see a way to close the topic (if I needed to).

Answer : Gateway setting changes with Manually configured IP

You can maybe check if there are certain programs that are configured to run when you logon via RDP.
First of all check the client and see if there is anything configured on the Programs tab.
Then have a look at the profile of the user you are using to logon, is there any logon script or something else that runs while logging in.
Then lastly check, c:\windows\system32\usrlogon.cmd, this script normally only runs on TS's. But maybe you can just verify it's the standard Windows script.