Windows 2003 Port 3389 not staying open

I have a windows 2003 standard edition server with service pack 2.  Every day i need to reboot the server because port 3389 is not longer open.  This started about two weeks ago, long after sp2 was installed and a year after the server was put into production.  RDP has always been used on the server.

No new software was installed on it recently, except windows updates.

I checked around this and other sites for help with no luck.  Most cases had a specific issue that caused this problem, mine didn't seem to.  Just stopped working and works again with a simple reboot.
trademark16Asked:
Who is Participating?
 
bhzdkhConnect With a Mentor Commented:
change the RDP port to something else like 9833, and see if this happens again.

on your server, go to start/ type regedit press enter
Go to
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStation\RDP-Tcp\Port Number, then change it to Decimal, and change it to 9833.
Reboot your server.

When you want to connect to it, use IP Address:9833
0
 
celazkonCommented:
Hi,
any errors or warnings in the eventlog? The software firewall is turned off? Is the server accessible on LAN while not available from WAN?
0
 
pcchiuCommented:
Try to update the video driver(or roll back the video driver to an older version); Microsoft update may not have the latest video driver you may need to download the latest driver from the video/motherboard manufacture; video driver will cause such problem as well.

0
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

 
kenyclCommented:
can you logon onto the console and see what services has stopped and eventlogs to get some clue as to why rdp has stopped.
when its stopped are you about to ping the server and telnet to the server on 3389?
0
 
trademark16Author Commented:
celazkon,

nothing in the event logs.  The firewall is turned off for this feature.  And yes the server is accessible by another computer on the LAN.  Nothing from the WAN right now.
0
 
bhzdkhCommented:
did you try what I suggested?
0
 
trademark16Author Commented:
bhzdkh,

not yet.  was hoping to get 3389 straight first.  will be trying your idea now.  unfortunately will not know right away as a reboot temporarily fixes it.
0
 
bhzdkhCommented:
If this solves your problem, then I think there is another software/service using this port.
0
 
trademark16Author Commented:
pcchiu,

it is a Dell T300 server.  The original driver was a Standard VGA.  Dell had a updated driver for the service tag i put in, which was for a ATI graphics card.  I applied and rebooted.
0
 
trademark16Author Commented:
bhzdkh

ok.  will let you know tomorrow if it fails again.
0
 
bhzdkhCommented:
Don't try different solutions together, So don't change the port for now, and see if driver update solves it.
0
 
trademark16Author Commented:
no luck on the video card driver change.  trying to change port next.
0
 
trademark16Author Commented:
On Firday i changed the port number and had no porblems until Monday when i could not connect in.  I rebooted and all was well again.  Today no porblems.  So other than the hiccup yesterday the port number change may have worked.  I think i will keep case open a few more days just in case.
0
 
kenyclCommented:
is there firewall logs you can look at to see why it is actually blocking possibly?
0
 
trademark16Author Commented:
kenycl, there was nothing in the log fo the router, which is a linksys.  Does windows 2003 standard have a log for it's firewall?  

Also i was not able to open Windows firewall because "Windows Firewall cannot run becasue another program or service is running that might use the network address translation component (Ipnat.sys)"  This error is new.
0
 
kenyclCommented:
right, on the linksys there is logging under security i believe. look at the firewall log part of it and see.
windows firewall logs are under eventlogs for windows
0
 
trademark16Author Commented:
nothing in either of the logs.

it has been fours days an no need to reboot so it looks like the change it port number seemed to work.

Thanks to all for all your help.
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.

All Courses

From novice to tech pro — start learning today.