Re: rdc could not connect
From: Chris (carsx88-6012_at_yahoo)
Date: 12/10/04
- Next message: Russell Cook: "Re: Logging on to remote desktop when not at home"
- Previous message: The Q: "Re: Remote Desktop will Not Re-Connect after initial session."
- In reply to: Bill Sanderson: "Re: rdc could not connect"
- Next in thread: Robin Walker: "Re: rdc could not connect"
- Reply: Robin Walker: "Re: rdc could not connect"
- Messages sorted by: [ date ] [ thread ]
Date: 9 Dec 2004 20:08:37 -0600
"Bill Sanderson" <Bill_Sanderson@msn.com.plugh.org> wrote in
news:uE#Ylpk3EHA.3000@TK2MSFTNGP15.phx.gbl:
> "Chris" <carsx88-6012@yahoo> wrote in message
> news:Xns95BAB4BD73C22carsx886012yahoo@38.119.100.146...
>>I am sure this has been asked a million times, but I have checked on
>>Google
>> and couldn't find the proper solution that fixes my problem.
>>
>> I have a laptop that is running Windows XP Pro SP2. It has been
>> working fine since SP2 was installed. However, all of a sudden, I
>> can no longer use Remote Desktop to connect to my servers.
>>
>> I have tried connecting to Windows 2000 Server and Windows Server
>> 2003 without success. The error I get is:
>>
>> The client could not connect to the remote computer
>> Remote connections might not be enabled or the computer might be too
>> busy to accept new connections. It is also possible that network
>> problems are preventing your connection.
>> Please try connecting again later. If the problem continues to
>> occur, contact your administrator.
>>
>>
>> I have no problems connecting with a few different computers and all
>> servers are listening on port 3389.
>>
>> I have the remote desktop web connection set up on a different box
>> running IIS, and I get a similar message that I can't connect using
>> this particular
>> computer when trying it within Internet Explorer.
>>
>> I have even try telnetting to port 3389 of some of the servers and it
>> just says "Could not open connection to the host, on port 3389:
>> Connect failed." It's not a DNS problems as it can look up the names
>> of the servers fine and it's assigned by DHCP anyway.
>>
>> I checked with netstat -an during the attempt of connection and it
>> does say
>> "10.10.34.x:3389 SYN_SENT", rather than "Established".
>>
>> So, is there anything else I can try to resolve this? I hope someone
>> can help me.
>>
>> Thank you.
>>
>>
>
>
>
> Good one!
>
> Hope the collective "we" are up to this one.
>
> Sounds like you know that the target hosts are properly configured and
> functional 'cause others can talk to them.
>
> And your machine is properly configured and functional 'cause you can
> talk to OTHER machines.
>
> And it isn't something esoteric with RDC, 'cause RDWC gives the same
> behavior (not too surprising, really.)
>
> So I tend to agree with the portion of the error message that reads:
>
> "It is also possible that network problems are preventing your
> connection."
>
> So far, just analysis, now I'm reaching a depth limit. You've got
> DNS, apparently. You can't do a telnet test, and the netstat -an
> result is unusual, apparently. I expect that you've tested using IP
> addresses as well as dns names?
>
> What can you tell us about the network?
Everything is closed behind the "corporate firewall". The problematic
machine is just accessing servers in the same subnet. Nothing is leaving
the firewall. Our subnet is 10.10.34.0, with netmask 255.255.255.0. We
used to have four domain controllers, now down to three... one W2k and
two Win Server 2003. The W2k DC is the Global Catalog server and it's
not doing much other than file sharing. One "active directory
integrated" DNS server (WinServ 2003) and two secondary DNS servers. Two
WINS servers on the WinServ 2003 and also two DHCP servers for the
subnet, but of course, divided into two different ranges when providing
addresses to DHCP clients. There are about twenty machines which have
DHCP reservations on both servers.
And yes, I have tried using IP addresses as well as host names when
trying to connect with the Remote Desktop Client, but with same results.
I attempted to reinstall the client, but of course, it doesn't let me
since the RD Client is a built-in component of Windows XP.
I am really stumped. Is there any way I can replace DLLs and/or EXEs
that the RD client use? It's a machine-wide problem because when I
logged in using a different domain user name, it gives me the same
errors.
Thanks...
Chris
- Next message: Russell Cook: "Re: Logging on to remote desktop when not at home"
- Previous message: The Q: "Re: Remote Desktop will Not Re-Connect after initial session."
- In reply to: Bill Sanderson: "Re: rdc could not connect"
- Next in thread: Robin Walker: "Re: rdc could not connect"
- Reply: Robin Walker: "Re: rdc could not connect"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
