This computer can't connect to the remote computer

Did you run Internet connection wizard and make sure that terminal service is selected?
If not let's start by doing that first.
Run the wizard again that cannot do any arm.

vico1

which menu to I run the wizard from?  do you mean network connection wizard?

I ran it again---I did not see where I could select Terminal Services

vico1 are you still willing to help?

Please advise if you can connect to the server via Remote Desktop from INSIDE your LAN.  If you can, then the problem is in your router/firewall and 3389 is most likely NOT open or is directed to the wrong IP.

To check if port 3389 is open, from a remote machine, open a command prompt and enter:

C:\>telnet <your FQDN or IP> 3389

Where <your FQDN or IP> is substituted by your actual FQDN or External IP address.  
The result of this command should give just a blank screen if you are successful.  If the port is not open, you'll get an error message.

Jeff
TechSoEasy

One other thing... what is the Operating System running on the computer you are trying to connect from?

Jeff
TechSoEasy

Yes djdavid57,
 this is what you should look for:

1.-From Your router Make sure that port 3389 is forwarded to Your SBS Server IP Address
2.-Go to server management console
3.-Click on "To do list" or "Internet and E-mail" on left pane
4.-Click on "connect to the internet"
5.-Follow the wizard and choose enable firewall
6.-Make sure terminal service is selected and continue the wizard.

Let me know if that helped

vico1

Jeff--TechSoEasy,
I tried to Telnet and cannot connect inside the LAN to the server via Remote Desktop.
The error I am getting back is: "Could not open connection to the host, on port 3389: Connect failed.  When I open my Sonicwall hardward device the port 3389 is enabled.  I am puzzled as to why out of the blue this would stop working.  BTY: both the Operating Systems running on the computers I are trying to connect from are XP Prof SP2.

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?

No need to uninstall the update, but that's a good clue as to the problem... check this out:
http://snipurl.com/1g0eo

Jeff
TechSoEasy

TechSoEasy--- thanks for the tip, but I did in fact reboot after the patch.  That solution did not apply to my problem because Terminal Services did not change to Manual -- it actually has remained in Automatic mode.  I did reboot several times yesterday.  I am reinstalling Service Pack 2 altogether---thanks for the input---I'll keep you posted on my progress today.

I've actually done a bit more research on this issue because it's coming up as a problem for others.  Terminal Services, by default, is not set to Automatic Start on an SBS.  So I'm actually thinking that may be part of the problem.  Because if it's set for Automatic, it may be starting before some of it's prerequisite dependencies are started.

Jeff
TechSoEasy

Please forgive me for the long response, but still working directly with MS SBS group hoping they could resolve problem.  Should I restart with TS set to manual?

I certainly would... here's the list of defaults:  http://support.microsoft.com/kb/829623

Jeff
TechSoEasy

Yes, ultimately I could only resolve it reinstalling the OS & SP2---which was pain because I lost all my special permissions.  MS told me not to reinstall the update that caused the initial problem.  Thanks for all the comments and suggestions.  Pllease close the question.

Jeff,

My apologies.  I thought I'd already closed this question.  This question is officially closed