RE: Can't connect to Client Desktops

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hello Geordie,

Thank you for posting to the SBS Newsgroup.

I understand that you failed to RDP to clients' computers through RWW from
the internet. If I have misunderstood your issue, please let me know.

There are many factors that may cause this issue, please see my detailed
information:

1> Do you have a router connected from SBS to internet? Make sure that the
port 4125 has turned on on the router or firewall hardware, and forward
traffic on port 4125 to the SBS server. For more information regarding a
similar issue which is caused by ISA, read the KB article:

828053 ISA Server prevents connection to a remote desktop when you connect
http://support.microsoft.com/?id=828053

2> If you have already turned on the port 4125, the issue still exists,
please check whether there is certain process running on the SBS server has
listened on the port 4125.

To resolve the issue, you need to find out which process is listening on
Port 4125 and end it, please follow the steps below:

1. On the Windows SBS computer, go to Start -> Run, type "cmd" (without the
quotation marks), and then click "OK".

2. Type the following command, and then press ENTER:

"netstat -an | find ":4125" (without the quotation marks). You receive
results that are similar to the following:

TCP < IP_Address>:<Port >< IP_Address>:<Port > LISTENING
<Process_Identifier>Note The <Process_Identifier> (ID) that appears in
these results is the ID of the process that is listening on port 4125.

3. Right-click the taskbar, and then click "Task Manager".

4. Click the "Processes" tab, and then click "Select Columns" on the "View"
menu.

5. Click to select the "PID (Process Identifier)" check box, and then click
"OK".

6. On the "Processes" tab, locate the service that corresponds to the
process ID that was returned by the netstat command.

7. Restart the service that corresponds to this process. For example, if
the process is Mad.exe, restart the Microsoft Exchange System Attendant
service. To do this, follow these steps:

a. Click "Start", click "Run", type "services.msc" (without the quotation
marks), and then click "OK".

b. Double-click the service that you want to restart, make sure that the
name of the process appears in the "Path to executable" box on the
"General" tab, and then click "Cancel".

c. Right-click the service, and then click "Restart".

d. If you are prompted to also restart one or more dependent services,
click "Yes". Note if this service has stopped responding, you may have to
end the process by using Windows Task Manager. To do this, click the
process in question, click "End Process", and then click "Yes".

For detailed information and resolution, please read the following KB
article:

886209 Users cannot connect to remote desktops by using the Windows Small
http://support.microsoft.com/?id=886209

3> Sometimes this issue can occur if you are using a Windows XP SP2
computer to connect from. Windows XP SP2 has a pop-up stopper which will
block the Web RDP session. In Internet Explorer on the workstation you are
connecting from, go to Tools, Internet Options, then click on the Privacy
tab, remove the check for Block pop-ups. Close and reopen IE and check if
you can connect now. If you have third party pop-up stopper software
installed, please also disable it.

If the issue persists, please help to gather the following information:

1. From the Internet and from LAN, go to Start -> Run "mstsc" (without
quotation marks). Test whether you can access client computers.

2. From LAN, log in RWW, test whether you can RDP to clients' computers?

3. Can you access server's desktop from LAN and from the Internet?

Hope this information helps. If anything is unclear, please feel free to
let me know. I am looking forward to hearing from you!


Best regards,

Brandy Nee

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

.



Relevant Pages

  • Re: companyweb from RWW
    ... "Could not open connection to the host, on port 23: ... internet should tell the tale, ... Les Connor [SBS Community Member - SBS MVP] ... This site is the default web site. ...
    (microsoft.public.windows.server.sbs)
  • Re: companyweb from RWW
    ... Les Connor [SBS Community Member - SBS MVP] ... "Could not open connection to the host, on port 23: ... internet should tell the tale, ... This site is the default web site. ...
    (microsoft.public.windows.server.sbs)
  • Re: External Access to Companyweb Fails
    ... Is there any hardware router or firewall installed in front of the SBS ... device to forward the TCP 444 port request to the SBS server. ... As we need to access companyweb through port 444 which is not the ... Open a command prompt on internet client, ...
    (microsoft.public.windows.server.sbs)
  • Re: Opening range of ports
    ... >> without removing the SBS firewall? ... >>> I understand that you want to open a range of port to allow the Backup ... >>> NIC will only work for internal domain, when you access from internet or ...
    (microsoft.public.windows.server.sbs)
  • Re: OWA Problem
    ... Firewall and publish your OWA to internet. ... Click Start on your SBS server, ... the appropriate port should be forwarded. ...
    (microsoft.public.windows.server.sbs)