Ok, sounds good. Thanks for the help

>The thing to do then is to post a thread that requests the one-time ability to remote desktop connect to another VFP developer's machine at night from your home pc as a test. You will need to connect to a workstation that has a static ip as a test and then go on from there...
>
>
>>Probably not. Pretty tight here.
>>
>>>Are you allowed to connect from your home pc to your work pc? That would be the best test because then your home pc is used in the same mode as when you connect to your client...where we work we are allowed to. We use Secure Client to vpn in and then remote desktop connection to access.
>>>
>>>
>>>>I have not tried connecting to anyone else. I don't know anyone else
>>>>whom I can connect to.
>>>>
>>>>I can try the port forwarding, but like I said, I'v completely removed the
>>>>router from the DSL/PC and stll cannot connect.
>>>>
>>>>
>>>>>Can you connect (via rdc and login) to any other system from your home pc?
>>>>>
>>>>>If no, then it still points to something in your home configuration. Something else you can do is assuming your ip address on your home pc is 192.168.1.199 (because you are using a router) then configure the router to forward port 3389 to ip 192.168.1.1999 (same ip address as your pc). The router will then forward rdc to your pc.
>>>>>
>>>>>Also, the client has a static ip address and that is what you entering into the remote desktop computer: field, correct?
>>>>>
>>>>>>I have WinXP Home on my home PC. I connect to a client running Win2K.
>>>>>>This client has other people connect to him ok, and he has logged in as me
>>>>>>on other PC's. I'm sure he is running a firewall, but like I said, this just started
>>>>>>a few months ago. And other people are connecting ok.
>>>>>>
>>>>>>I have a DSL modem connected to a router. I'v tried a direct connection from the
>>>>>>modem to my PC. I have a dynamic IP.
>>>>>>
>>>>>>But again, this was all fine when I could connect. No idea why it doesn't work now.
>>>>>>
>>>>>>
>>>>>>>Kevin,
>>>>>>>I just now read your original message in this thread and realized that you are referring to a client pc as being the host you connect to. You must also do the same on their system that you have verified on yours. There must be a difference between the system at work and the one at home if one works and one does not. Is there any firewall at the client that is limiting the ip addresses, pc name, or user that may connect through it? Is the client running Windows 2000, Windows XP Home, or Windows XP Pro? Is the client pc on a network? Do you have a dynamic ip address at home and a static ip address at work? Does your work or your home use NAT? Are all three systems running SP2 (the client, your work, and your pc at home)?
>>>>>>>
>>>>>>>A quick but IMPORTANT check, can you connect to ANY OTHER SYSTEM using remote desktop connection from your home pc?