Question : DHCP blocking VPN and Remote Desktop

This is a little lengthy, but I've been wracking my brain for several days now.... here goes:
I am using an evalution copy of Windows Server 2003 to see if it is worth it to convert from a peer-to-peer network.  Up until this weekend, it was great.  I had DNS, AD, shares, etc all set up and running very well.... then I set up DHCP - which worked great, but now  my wife can't connect via VPN to her client.  She is using Nortel Contivity VPN Client first, then remote desktop on both a Windows XP Pro and an XP Home machine.  When she tried to log in, it wouldn't connect.  So in a panic, I disconnected the cable modem and plugged her directly into it.... that worked fine on Saturday.  So, I deleted the DHCP setup on the server and let the router assign IPs.  That worked fine but I wasn't satisfied, so I did as much research as I could and found that if I went to Properties in the Local Area Connection on the Server, select Advanced TCP/IP Settings, the Options tab, Properties (for TCP/IP Filtering) and selected Enable TCP/IP Filtering (All Adapters), that I  could get the Contivity VPN Client to communicate with the remote server with the original DHCP configuration, but got the following message when trying to log in via the Remote Desktop:
"The client could not connect to the remote computer.  Remote connections might not be enable or the computer might be too busy to accept new connections.  It is also possible that network problems are preventing your connection.  Please try connecting again later.  If the problem continues to occur, contact your administrator."  Well I'm the administrator.... so I went back to the configuration with no DHCP, and had the router (Linksys) do the DHCP assignments, and it connected fine.
I'm at a loss... I openned port 3389 on the router, but that can't be the problem because it gets through fine as long as DHCP is not running on the server.
Any suggestions????

Answer : DHCP blocking VPN and Remote Desktop

I was gonna say something about that, since the linksys router gives the dns suffix of it's wan connection and the 2k3 server uses the AD domain as the dns suffix. But I didn't think it would have anything to do with it.

Gald you figured it out. I will not soon forget that one!

Good troubleshooting!