Hi again,
Is this the same issue as you described in your earlier question? http://www.experts-exchang
Main Topics
Browse All TopicsI am running Server 2003 SBS SP1. Recently I am unable to connect remotely to my server inside and outside the LAN. When I try to log in as normal I received the following error: "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." Before posting my question I've read thru a few similiar questions--as a result I done the following: I checked my firewall to ensure that port 3389 is open, but when I went to www.grc.com I performed a port probe on and it indicated that 3389 is closed???? Cryptographic Services is started and Terminal Services is started but options to start, stop or restart are all greyed out.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Hi again,
Is this the same issue as you described in your earlier question? http://www.experts-exchang
Yes, I am new to Expert Exhange and it was recommended to post the same question in different areas. It's all the workstations on LAN. From what I have trouble-shooted I don't see any other problems between the workstations and the server. All my attempts to remote into the server has been using and IP address--I get the same error. I'm puzzled because this happened overnight and on my SonicWall TZ170 the port is enabled.
Can you try running the CEICW wizard in Server Management again and make sure you allow the Terminal Services service in your firewall? See here for more info: http://www.sbs-rocks.com/s
Hi:
On SBS 2003 Terminal services being started but options to start, stop, restart being grayed out is "normal". You might want to check the following things:
1. Right click on My Computer, select Properties. Select the Remote tab and insure that the "Allow users to connect remotely to this computer" is checked. You may want to select remote users (optional). Administrator is enabled by default.
2. Using the Server Managment console (Start > Programs > Administrative Tools > Server Mangement), navigate to the Advanced Management node on the left tree and expand it. Navigate to, and expand the Terminal Services configuration node. You should see a Connections folder. If you click on the folder, you should see a connection called RDP-Tcp on the right pane. If you don't, right-click on the folder and create a new connection. If a connection exists, right-click on it to ensure that the connection is enabled. You should also check the properties.
Hope this helps
cogentsol wrote:
"You should see a Connections folder. If you click on the folder, you should see a connection called RDP-Tcp on the right pane. If you don't, right-click on the folder and create a new connection. If a connection exists, right-click on it to ensure that the connection is enabled".
I went thru the steps--everything looks ok, but specifically which tab would set the "enable"?
You need to right-click on the RDP-Tcp connection to get a context menu, go to the All Tasks option then have a look at the first option. If it says "Enable Connection" click it and you might be working again, if it says "Disable connection" then the connection is already enabled and that isn't the problem.
FYI: Microsoft sent out a bad update KB925902 on April 4, 2007. I began receiving "memory relocation and user32.dll" errors my system automatically installed this update. I then had to run system restore to remove the update and go back several days. My users to log in remotely informed me this morning that their problems actually began on April 4. So, I just checked the servers updates in "Add/Remove" and discovered that this update was installed on the server on the 4th. Up to the day of the problem I had not made any system changes---therefore I make any other changes I think it's wise for me to first try and uninstall this update to see if the Terminal Services port is restored back to normal function.
What do you think?
WSUS -> Windows Server Update Services
It's a program which you can install on Windows Servers to handle the updating of client computers using Windows Update from the server. It is managed through a web-interface (although the new version will be with an mmc snap-in) and basically means you have control over what computers receive what updates etc.
See http://www.microsoft.com/w
It also helps because the updates only have to be downloaded once (to the server), they are then downloaded from the server by the individual clients (across the LAN) as opposed to every client downloading every update from the Internet, taking up bandwidth on your DSL/cable line or however you connect to the internet at your offices. So it still uses and puts load on the LAN, but with most LANs running at speeds of at least 100Mbps it shouldn't cause too many issues.
I am currently working with the Microsoft's SBS group. We have discovered that I was in "Safe Mode" to uninstall the update via C:\Windows folder ($NtUninstallKB925902$)---
Business Accounts
Answer for Membership
by: tigermattPosted on 2007-04-09 at 12:47:32ID: 18878097
Is it only on one particular workstation inside the LAN or all of them?
Are there any other issues on the LAN between workstations and the server?
Can you remote desktop into the server from the LAN using an IP address, or do you get the same error? (If an IP address works it could be a name resolution issue)