Windows Remote Desktop connection problem

MikeHunt79 · 4 Jan 2008 at 15:26

Computer A - Running XP pro, and has remote desktop connection enabled on a non-standard port, router is setup with port fowarding.

Computer B - Also running XP pro, and can connect and remotely operate computer A.

Computer C - Running Vista Home Basic. Used to be able to connect and control Computer A fine, but has suddenly stopped....

Has there been a Vista update or anything like that which has broken remote access? Could it even be an ISP port blocking?

Uhtred · 4 Jan 2008 at 15:40

*cue loads of people saying vista basic doesn't come with RDP

)

Are all these computers on the same network? If so i don't see how your ISP can be involved. What error do you get when you try and connect and can comptuer C connect to comptuer B?

ns400r · 4 Jan 2008 at 15:45

Zap said:
*queue loads of people saying vista basic doesn't come with TS )

Are all these computers on the same network? If so i don't see how your ISP can be involved. What error do you get when you try and connect and can comptuer C connect to comptuer B?

LOL, yep.

I'd also check the error you see and also give the Event viewer log a once over to see if that mentions anything.

pc-modd · 4 Jan 2008 at 16:31

Have you tried pinging A from C just to make sure it is connected properly? On one of the last vista updates it stopped me using RDC because it changed some security settings, cant remember what though..

MikeHunt79 · 4 Jan 2008 at 17:43

Sorry, I should have mentioned all 3 computers are miles from each other - I'm connecting over the internet.

Computer A is on BT broadband ADSL,
Computer B is on Virgin ADSL,
Computer C is on Tiscal ADSL (I think).

Also, all 3 computers are going thru routers, but I've configured port forwarding on the router for computer A to forward my RDC port.

This works, as I can connect fine from computer B to computer A even tho they are 5 or so miles from each other.

Now with computer C, I've tried almost everything apart from a Linux LiveCD. I've turn the firewall in the router off, the firewall in vista off, but even when the firewall is on, it should always allow outgoing connections shouldn't it?

I'm guessing it's some sort of Vista issue, but I can't confirm this until I either try a Linux or XP LiveCD, or even try another computer hooked up to Computer C's router. Is there anything else I can try while I am at computer C before I give up and go to the pub.

pc-modd said:
Have you tried pinging A from C just to make sure it is connected properly? On one of the last vista updates it stopped me using RDC because it changed some security settings, cant remember what though..

Well, when I ping from C to A, I get no returned packets, but I think this might be due to the router at computer A. I'll try pinging from computer B to A later on, but I have a feeling I'll get no returned packets also...

My gut feeling is bloody Vista, but I'm going to try a LiveCD next time I'm on Computer C to be sure... :mad:

EDIT: FWIW, This is the error message:

"This computer can't connect to the remote computer.

Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator."

ns400r said:
I'd also check the error you see and also give the Event viewer log a once over to see if that mentions anything.

I had a quick look, not much relevent apart from this:

Log Name: System
Source: Tcpip
Date: 04/01/2008 17:55:42
Event ID: 4226
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Mindthegap
Description:
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Could this be the reason?

ns400r · 4 Jan 2008 at 18:15

Can't think of anything apart from the non standard port used on Computer A. Is Vista on Computer C passing on the correct port number?

MikeHunt79 · 4 Jan 2008 at 18:19

ns400r said:
Can't think of anything apart from the non standard port used on Computer A. Is Vista on Computer C passing on the correct port number?

Yep, I actually had computer C set up with saved a .RDP that remembers the connection settings, username, password, etc.

I'm connecting like this:

83.78.35.26:1234

where 1234 is my port number (That isn't the real IP or port tho, for obvious reasons).

Computer C used to connect fine, but it stopped a few days ago. I've checked and double checked the port number, and it still won't work. :confused:

Uhtred · 4 Jan 2008 at 19:19

MikeHunt79 said:
I had a quick look, not much relevent apart from this:

Log Name: System
Source: Tcpip
Date: 04/01/2008 17:55:42
Event ID: 4226
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: Mindthegap
Description:
TCP/IP has reached the security limit imposed on the number of concurrent TCP connect attempts.

Could this be the reason?

Is that at the exact time you try and connect? Do you have bit torrent or anything running?

MikeHunt79 · 7 Jan 2008 at 13:55

Zap said:
Is that at the exact time you try and connect? Do you have bit torrent or anything running?

Yep, it does seem that the times match, so perhaps Vista is throwing a wobbly as it's a non-standard port?

No bittorrent or anything like that - Only firefox and avast anti-virus was running at the time. These wouldn't stop RDC connecting would they?

Anyway, I'm building an XP boot CD as I type this... Hopefully I should be able to see what causing this...

MikeHunt79 · 7 Jan 2008 at 14:30

Well, I've managed to get around the 4226 error by installing a patch....

http://www.mydigitallife.info/2007/...-tcp-connect-attempts-error-on-windows-vista/

It still won't connect tho.

MikeHunt79 · 8 Jan 2008 at 15:16

Bit of an update - I've got Computer C with an Windows XP live CD on it, and RDC still won't connect, so it doesn't appear to be a vista issue.

Is there any settings in the router or anything like that which could be causing the problem?

EDIT: I found out today computer C's ISP is BT also... also, tracert ALWAYS times out after 8 hops, so is it possible this is some ISP issue?