Results 1 to 5 of 5

Thread: Server pingable but can't RDP or connect to UNC path

  1. #1
    Join Date
    Mar 2010
    Posts
    69

    Server pingable but can't RDP or connect to UNC path

    We are running Windows Server 2003 SP2 server as a file server in our office. It's configuration includes 4GB ram and 2GHz Dual core CPU. The problem I am having is that we lose the access to the server very soon and it happens almost every day. We can ping the server but cannot connect it with RDP or UNC, not even with the IP Address. If I try to log in to the server via console I cannot get the log in screen. Nothing appears on the event logs. The VMware shows processor and memory activities but not for network activity. What is the problem with my server? Need some assistance!

  2. #2
    Join Date
    May 2008
    Posts
    2,945

    Re: Server pingable but can't RDP or connect to UNC path

    If you are unable to check the network activity from Windows than use command prompt for the same. Go to the command prompt and type "netstat -an". Press Enter. There seems to be some ports issue. May be your server is not having enough ports open to make connections.

  3. #3
    Join Date
    Apr 2008
    Posts
    3,339

    Re: Server pingable but can't RDP or connect to UNC path

    Make sure that the terminal server can contact an activated Terminal Services Licensing server which has enough TS CALs installed. Go to Start, Run "Services.msc", Terminal Service and make sure the Startup Type is automatic and Status is started. Make sure that the terminal service is listening on the port 3389 and the firewall is not blocking this port. Make sure that those particular users are already added who need to remote desktop to the Remote Desktop Users group on the terminal server.

  4. #4
    Join Date
    May 2008
    Posts
    3,516

    Re: Server pingable but can't RDP or connect to UNC path

    Try to perform a clean boot of your Windows Server 2003 computer. For this go to Start, Run, type "msconfig", and then hit Enter. Go to the General tab, select "Selective Startup" option and then uncheck all the check boxes: Process SYSTEM.INI File; Process WIN.INI File; and Load Startup Items. Go to the Services tab, check the "Hide All Microsoft Services" check box, and click on Disable All button. Save this by clicking on OK button. Restart your computer for changes to take effect.

  5. #5
    Join Date
    Mar 2010
    Posts
    69

    Re: Server pingable but can't RDP or connect to UNC path

    Thanks for all of your suggestions. But none helped me. After a long discussion with my support team I have finally built a new server for our office. I have also created a new virtual server for the same. Now we have upgraded to Windows Server 2008 64 bit edition keeping in mind that we add more memory and hard drive in the near future.

Similar Threads

  1. Replies: 5
    Last Post: 23-08-2010, 08:13 AM
  2. Replies: 3
    Last Post: 10-09-2009, 09:38 AM
  3. Invalid Boot path in Server 2003
    By Leoniee in forum Operating Systems
    Replies: 3
    Last Post: 30-05-2009, 06:15 PM
  4. Replies: 0
    Last Post: 23-03-2009, 11:32 PM
  5. Upgrade path to Windows Server 2008
    By rjposey@gmail.com in forum Windows Server Help
    Replies: 3
    Last Post: 06-06-2008, 10:08 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,863,951.78753 seconds with 17 queries