Can't use remote desktop connection - Need help

[Gil]

Hi all.
I'm running two computers in WLAN both have Win7 Ultimate 64bit.
I've noticed that if I want to have remote desktop connection, I must have a password as a user on both computers while I don't want to have a password when I use the remote desktop connection.

Can someone help me please with this thing?

Thanks.

Gil.

 

[Bill2]

Having a password makes a lot of sense from the security point of view. However, if you really dont want to set one, go through this tutorial (i believe it works for win7).

Trick to Enable and Allow Windows XP and Vista Remote Desktop Login Without Password (or With Blank Null Password) My Digital Life

 

[Gil]

yes it has sens to it but these computers are mine and I only use them therefore I don't like typing passwords each time I turn on the computer.
thanks for the help.

 

[Gil]

I still need some help. I did use a password in order to use remote desktop but I got this error message:


can someone help me?

 

[CommonTater]

Hi all.
I'm running two computers in WLAN both have Win7 Ultimate 64bit.
I've noticed that if I want to have remote desktop connection, I must have a password as a user on both computers while I don't want to have a password when I use the remote desktop connection.

Can someone help me please with this thing?

Thanks.

Gil.

Hi Gil... I've just read through this and Bill is giving some good advice... i hope you don't mind a little more noise...

First you have to enable Remote Desktop on the target machine (the one you're trying to access). This is done through System->Advanced->Remote.

And yes, you should be glad it's asking for passwords... Waking up in the morning to discover your data partitions have been deleted by some torknut in Outer Slobovia, would explain why...

 

[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.

 

[mrdemon]

Logmein.

Have you try'd Logmein. Its free and easy, you can also connect To any PC you have set up on this.

Click here for link

 

[CommonTater]

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....

 

[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....

I've set a password before I posted my previous message. I remember that before I used WLAN I didn't have to set users for access. Are you sure this is it? If I only changed from LAN to WLAN and never before had to set users for accessing remote desktop then i don't think I need now.
i don't need logmein, the computers are in the same house and Win7 has it right with remote desktop.

 

[CommonTater]

I've set a password before I posted my previous message. I remember that before I used WLAN I didn't have to set users for access. Are you sure this is it? If I only changed from LAN to WLAN and never before had to set users for accessing remote desktop then i don't think I need now.
i don't need logmein, the computers are in the same house and Win7 has it right with remote desktop.

You were on a twisted pair before and now you have a router... ya?

That changes things rather a lot... for one thing you have a third party DHCP and DNS server running... your ip addresses are issued by the router and are now meaningful in accessing various devices... it really is quite different.

 

[not so gray matter]

Personally, I second the recommendation for LogMeIn. If you don't want to use an online solution, try out TightVNC, I've heard good things.

 

[CommonTater]

Personally, I second the recommendation for LogMeIn. If you don't want to use an online solution, try out TightVNC, I've heard good things.

He's got what he needs built right into windows... It's a settings problem, most likely, it's just a matter of finding out which setting he's tripping over.

I'm sorry but I just don't see why he should have to install even more bloat into an OS that already included the needed functionality.

 

[Gil]

I've set a password before I posted my previous message. I remember that before I used WLAN I didn't have to set users for access. Are you sure this is it? If I only changed from LAN to WLAN and never before had to set users for accessing remote desktop then i don't think I need now.
i don't need logmein, the computers are in the same house and Win7 has it right with remote desktop.

You were on a twisted pair before and now you have a router... ya?

That changes things rather a lot... for one thing you have a third party DHCP and DNS server running... your ip addresses are issued by the router and are now meaningful in accessing various devices... it really is quite different.

You got it.
So how can I fix it? it's broken by the way

 

[CommonTater]

I've set a password before I posted my previous message. I remember that before I used WLAN I didn't have to set users for access. Are you sure this is it? If I only changed from LAN to WLAN and never before had to set users for accessing remote desktop then i don't think I need now.
i don't need logmein, the computers are in the same house and Win7 has it right with remote desktop.

You were on a twisted pair before and now you have a router... ya?

That changes things rather a lot... for one thing you have a third party DHCP and DNS server running... your ip addresses are issued by the router and are now meaningful in accessing various devices... it really is quite different.

You got it.
So how can I fix it? it's broken by the way

On your target machine... make sure at least one of your accounts (create one if you have to) is passworded with administrative priveledges... this is the account you will use to access the other machine...

In the target machine get into your REMOTE settings --the dialog you snipped for me-- and enable remote desktop... then click Select Users and enter the account above...

Finally take a look at the Windows Firewall... make sure the exception for Remote Desktop is checked...

Now on the source machine follow the same procedure....

If all goes well these two should now be able to access one and other.

When you click your Remote Desktop connection for the first time, make sure you go into the options and take out the trash... only enable the things you need... and set your video to minimal specs... You only have so much bandwidth if wifi is involved and you don't want to saturate the connection.

From there it should be a matter of simply clicking remote desktop, entering the machine's name, then the username and password ... et voila....

It should be pretty easy, if you follow the steps... I use it on my LAN all the time as a means to remotely administer my HTPC system and pull the porn out of my kids computers (just kidding about the last bit)....

And, because I heard your grumble about having to type passwords all the time when you start your system, I'm attaching a little Autologon utility you can use to have your systems log into a pasworded account automatically on startup or reboot...

 

[Gil]

Thanks for the detailed post but no luck...
here's the error I got (notice the welcome screen...I'm almost there):

Update: I can access the host machine from the target machine. Both have same settings.
I noticed that whenever I try to access the target machine and fail, I get an error message regarding the ATI catalyst control center when I log back on via the target machine. I hardly believe it has something to do with the connection failure.

 

[CommonTater]

Thanks for the detailed post but no luck...
here's the error I got (notice the welcome screen...I'm almost there):

Update: I can access the host machine from the target machine. Both have same settings.
I noticed that whenever I try to access the target machine and fail, I get an error message regarding the ATI catalyst control center when I log back on via the target machine. I hardly believe it has something to do with the connection failure.

That's certainly odd.. The Catalyst Control Center is part of your video drivers, a setup program actually, to let you adjust things. That shouldn't be having anything to do with remote desktop activity...

Have you tried exiting the CCC on your target machine before attempting your remote connect to see what happens?

(In truth, there's no need for it to be running all the time anyway...)

 

[Gil]

I tried without it but it doesn't help. When I try to use remote you said that the target machine locks up. It's true so far but right after the computer locks up I get the error message in my host computer. When I log back in, I see that the wireless connection in the system tray is refreshing and reconnecting, which implies that when the target machine locks up it looses the connection, disconnecting.

 

[CommonTater]

I tried without it but it doesn't help. When I try to use remote you said that the target machine locks up. It's true so far but right after the computer locks up I get the error message in my host computer. When I log back in, I see that the wireless connection in the system tray is refreshing and reconnecting, which implies that when the target machine locks up it looses the connection, disconnecting.

That would be truly strange behavior... What it does is log the desktop, the same as pressing WindowKey+L ... the rest of the computer is still functional... or it should be.

Have you checked the settings on your network adaptors?
As a thought... you could try disabling IPV6, just uncheck the box, don't uninstall anything... and see what happens. Many routers can't deal with it...

 

[Gil]

You want me to turn off IPv6 on both computers? I doubt it would work since I can use the remote desktop from the target machine on the host machine.
Could it be that the target machine looses connection due to the fact that its wireless network adapter is a USB dongle? once the target machine locks up it somehow shuts down the USB or something like that?

 

[Gil]

Some dude with the same problem:
Wireless USB Adapter behaviour - Cannot Remote Desktop TO a desktop PC that has Wireless USB Adapter?