Koozali.org: home of the SME Server

New XP Pro Computers cant access internet w/browsers

ebthor

New XP Pro Computers cant access internet w/browsers
« on: September 12, 2005, 08:17:03 PM »
To note, I am a tech who is very inexperienced with Linux.  My new customer is a school running a Mitel 6000 SME Server with cable internet.  On the server, they run filtering software called Dan's Guardian. These new Dell Optiplex computers cannot browse the web through any browser, but can ping by name or IP and can activate their MS Office software without problems.  Also, network connectivity is not affected.  I have spoken to the tech who installed the server, and he's stumped.  None of the computers in the school use a proxy server setting, but I have even tried this pointing to the Linux server with 8080 as the port.  Then, I don't get "page cannot be displayed" but I do get a message like "web site under construction" for any site.  I have tried reformatting one of these computers and a different network card.  They use DHCP but I have even tried static settings pointing DNS to the LInux server (they have a Server 2003 server that is the DNS server), but this isn't a DNS problem because they can ping by name.  There is one other XP Pro computer in the building (an older one), and it and all the 2000's do not have this problem.  The only differnce I can think of with the other XP pro is that it may only be running SP1, and these have SP2.  Any suggestions??

Offline NickR

  • *
  • 283
  • +0/-0
    • http://www.witzendcs.co.uk/
New XP Pro Computers cant access internet w/browsers
« Reply #1 on: September 12, 2005, 09:39:37 PM »
Try manualy setting the proxy port in IE to 3128 as that's the port the proxy runs on - not sure where you got 8080 from?
--
Nick......

Offline jackl

  • ****
  • 136
  • +0/-0
New XP Pro Computers cant access internet w/browsers
« Reply #2 on: September 14, 2005, 01:15:39 AM »
ebthor
If you are using Dan's Guardian set the proxy settings in IE to the name of your server and port 8080 if not try what Nick suggests use port 3128 instead.

Regards
Jack
......