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

Terminal Server Cannot Access Websites

We recently installed a Windows 2003 Server as a Terminal Server and have started having some issues accessing websites.  All terminals connect to the server via RDP through a VPN.  We noticed that the terminals cannot access webpages through the RDP connection but are still able to access websites through the local machine.  And even though they cannot access the web through the terminal, they can still RDP in to the server.

Going to the server, it cannot access webpages at all.  I have tried restarting the router and it will not fix the issue.  The only thing that will work (temporarily) is to restart the server and even that will only work for 1-2 days.  Any thoughts on what could be happening?
0
stin27
Asked:
stin27
  • 5
  • 4
1 Solution
 
Jakob DigranesSenior ConsultantCommented:
first you'll have to figure out if this is a "webpage problem" or a network problem.
When you have no access to webpages, check to see if you have network connection to internet.

Go to CMD
ping 196.88.55.16
ping www.bbc.co.uk

What does these return? if the IP-address ping works, but not the FQDN, then it would be a DNS issue.
if both work - but not from Internet Explorer (or any other web browser you'd use) try updating browser as this might be the issue. If neither responds, then you have some kind of networking issue.

Do the users connect to RDP via internet or via LAN? Any errors in event viewer?
0
 
stin27Author Commented:
Pinged the IP address but request timed out. Got replies from fqdn.  I restarted the server last night and everything is still working as it should so I will try again in the next day or so when it decides to not work.  Nothing is jumping out at me in the event viewer so I will check next time problems happen, should be within the next day or so if history repeats itself.  Users connect to rdp via internet vpn, no lan users.  Thanks for the reply and will keep you updated.
0
 
Jakob DigranesSenior ConsultantCommented:
you got response from www.bbc.co.uk ping ?
try pinging the IP for www.bbc.co.uk

But this shows that you have internet connection - so the problem looks to be related to Internet Explorer, somehow.

Do you have a proxy setup? Updated Internet Explorer?
0
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.

 
stin27Author Commented:
Yes, I got responses from www.bbc.co.uk but timed out when pinging the IP.  No proxy but we are on IE version 6.  Has not been updated yet and is still what came with the server.  Probably should be updated : ) but didn't think it could cause too many problems.
0
 
Jakob DigranesSenior ConsultantCommented:
running IExplorer6 shouldn't cause any problems, but the IE installation could be broken. Can try installing SP1 again to try to fix, but Iexplorer 8 is a lot more secure - and especially since you're running TS-services.

But be aware that you have to do some work in configuring secured sites, or turn off secure browsing ..
0
 
stin27Author Commented:
OK, internet just crashed.  Pinged IP address and request timed out.  Pinged domain and it says "Ping request could not find host www.bbc.co.uk. Please check the name and try again."  Remote users can still connect to the server through terminal services though.

I know if I restart the server, the internet will come back up but I don't really want to do that until I figure out what is going on.  Any ideas on what else to check?
0
 
stin27Author Commented:
Just did a little checking and the server is setup as the DNS server and the NIC has the server's IP set as the dns server.  But DNS was not running on the server.  I manually started DNS and internet is working again.  Can you think of any reason that DNS would stop working?
0
 
Jakob DigranesSenior ConsultantCommented:
nope --- does it stop several times?
But if you keep having problems with internet and DNS is still running - check:
can you browse LAN ? Try ping local machine name if you have any.

0
 
stin27Author Commented:
I would assume that when the internet goes down, this would be the cause.  We are still able to browse local computers when internet is down.  Even able to access terminal server through VPN.
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 Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

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