Quote: Originally Posted by Gil
Ok i think I'm on to something.
First, the remote connection was always set on Allow.
Second, this problem only occured when I stopped using cross cable and switched to WLAN. Now, here is what I think happens when I try to use remote:
once I initiate a remote, the remote computer logs off or something like that, and that action resets/shuts down the connection between the two. Cause right after the remote fails, I can't see the computer in my homegroup any longer.
The remote computer will lock it's desktop and it will stay locked until someone physically goes to the machine and re-enables it... this is perfectly normal in Remote Desktop connections.
Now... does the target machine have a password on the username?
If not, you'll probably have to set one. I had problems with mine not working until I created passwords on all my machines.
You also have to set specifically, each person who you will permit to access that machine by remote desktop. Each person needs an account on that machine and they have to be listed in the "allow" dialog... Click the "Select users" button and add them in there.
The user name and password you enter is that for the remote computer, not for the one you're sitting at... You'd be amazed how often I have to explain that to people
I doubt your wireless lan is the problem. It seems from your description it is making contact but the sequence of events is not completing to let you hook onto the other machine....