Alright, heres the problem. We have a Windows 2000 Server machine that is going kaput (albeit slowly). We also have a Windows 2003 machine that has been acting as our VPN machine over the last couple months. Our 2000 machine has acted as our file server (for both internal client machines and our VPN (outside) users). Our main thing with having this configuration is so people can access a database program and make entries into it. I have copied our stuff from our 2000 machine to our 2003 machine so far. I have also promoted our 2003 machine to a domain controller (I guess you'd say it is now a secondary domain controller) in the process of getting the 2003 machine to replace our 2000 machine. The 2003 machine should be getting pretty close to being an exact replica of our 2000 machine, although I will probably still have to work on that. One thing that was wierd that happened was that, now, on the external user's computers, when they try to connect to the VPN, they now (seemingly) automatically get referred to the 2003 server (given the IP that is showing up on their system) and I didn't even do anything to set it like that. (Besides promote the machine to a domain controller, of course, but I don't know if that would have done it). Can you guys tell me if that would have caused it? The other thing is that we use a network drive to access the program we need. I have that set up, after having to share the appropriate file on the 2003 server after copying the file from the 2000 machine, and setting the appropriate permissions. So now, our internal people can connect the network drive properly. HOWEVER, they cannot run the database program properly. Every time they try, they are bought to the initial login screen, they enter their user name and password, theres a pause, and the program crashes. We have an INI file on the shared folder on the server that probably has something to do with it, but I can' imagine what. As for our external (VPN users) I'm not sure exactly, but I don't think they can login to the VPN anymore. (Again, something changed the IP they are to use, to the new server, I wish it wouldn't have unless it was going to work.) By the way, we have Terminal Server installed on the 2003 machine. Can anyone help?