• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 541
  • Last Modified:

RDP to SBS 2003 server

All of a sudden I can no longer remotely connect to the SBS 2003 server.  Internet works, email works. Pinging the server works, have checked the Firewall router its configured correctly.  Have the SBS 2003 server firewall turned off. Can't seem to find an answer.
0
M L Wallace
Asked:
M L Wallace
  • 4
  • 3
  • 3
  • +3
1 Solution
 
archersloCommented:
You might want to give a clear description of exactly what does happen when you attempt to connect via RDP.
0
 
tjc123IT DirectorCommented:
Check the Remote tab under the Computer properties of the SBS server to ensure RDP access is enabled and for the account you are trying to access it with.  Also, check Terminal Services Manager under Administrative Tools to ensure there are no active sessions taking up the allotted 2 default admin allowable connections if you don't have the Terminal Services role installed with appropriate licenses.
0
 
M L WallaceOwnerAuthor Commented:
The Remote desktop connection times out after about 10 minutes and says;
This computer can't connect to the remote computer.

The two computers couldn't connect in the amount time allocated.
Try connecting again,  If the problem continues contact your administrator
for technical support.

I have tried from several computers and get the same answer.  I have tried using the private server IP address and the public.  SonicWall has tested very thing and says the problem is with the server.  I don't know what else to tell you.  It worked a week ago when we lost power for two hours and now it won't work.
0
Cloud Class® Course: Ruby Fundamentals

This course will introduce you to Ruby, as well as teach you about classes, methods, variables, data structures, loops, enumerable methods, and finishing touches.

 
M L WallaceOwnerAuthor Commented:
Both of your suggestions have already been done.  My partner and I are MCSE's if the Terminal Services License had been exceeded then that message would be displayed. And
off course we checked the remote  connection in System.
0
 
btdownloads7Commented:
I've seen this happen on a few servers, but I haven't been abe to find what's causing it. But rebooting the server solves the problem.
0
 
archersloCommented:
Have you restarted the service? Obviously, that would happen if you restart the server - but it'd be worth a shot before doing that.
0
 
WORKS2011Austin Tech CompanyCommented:
what happens if you leave ping running, try ping -t ip address.

tracert tell you anything?

Have you reset the router? Central point of failure I would start here. Also check the router logs.
0
 
M L WallaceOwnerAuthor Commented:
Tried all your suggestions.  None worked.
0
 
WORKS2011Austin Tech CompanyCommented:
Did you reset the switch, it's a single point of failure could cause issues. If it's a managed switch check the logs.
0
 
hecgomrecCommented:
Real world experience quickly teaches administrators to leverage the numerous Windows SBS 2003 wizards; trying shortcuts or manually configuring SBS 2003 settings is a recipe for disaster. Don't do it. Use the wizards.

SBS 2003 includes a wizard dedicating to configuring remote connections.

To access the Remote Access Wizard:

1.Click Start.
2.Open the Server Management console.
3.Highlight the To Do List.
4.Click the Start link for Configure Remote Access (the third step) within Network Tasks.

Try that and then try to connect.  Also, what is the result of a "ping <servername>"???
0
 
btdownloads7Commented:
You should try RDPing from inside the LAN using the server's internal IP address. If you can do that, but still can't connect from the outside, then the problem is not with the server, but with your router/firewall. But if you can't connect from the LAN either, then you've narrowed the problem down to the server itself.
0
 
hecgomrecCommented:
If you can resolve the issue with the previous indications please try to restore a system backup from a point you know it was working.  I don't know if you updated something on the server that might be causing the issue.  Maybe the only way will be to restore your settings to previous state before that.  Hope you have one!!!!
0
 
WORKS2011Austin Tech CompanyCommented:
Sorry but a system backup is highly "NOT" recommended. Real life experience shows that MCSE's like myself and marionlwallace resolve issues not turn to backups. There's a fix for this I don't believe any backups is the correct approach.
0
 
tjc123IT DirectorCommented:
Can you describe any items that have changed since it stopped working?  System updates?  Windows Updates?  AV Updates?  Software firewall installations?
0
 
btdownloads7Commented:
I completely agree with WORKS2011 -- restoring a server from backup is a terrible idea. That should be the absolute last resort. There are a lot of things that can be checked first, especially if the problem isn't with the server at all, but with the router or other network equipment/settings.
0
 
M L WallaceOwnerAuthor Commented:
We discovered the problem: finally.  We accidently found that the program tscc.mcs was missing.  The tscc.dll was there, we copied the file from another SBS 2003 server and bang
everything was fixed.

Thanks for everyone's response.

I am glad its fixed.

Works2011 is right you exhaust yourself to fix rather than restore or reinstall.  I will accept works2011 solution and close this case
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

  • 4
  • 3
  • 3
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now