Re: Clients can't browse to certain websites or URLs



running ICW won't mess up anything (unless you change something that messes
it up of course)

It almost sounds like your DNS from your ISP is failing except for that you
enter the IP and it's slow?

Are you running 1 NIC 2 NIC additional Firewall? ISA? What's your network
layout?

Are Downloads Slow also? Go to www.dslreports.com and do a network speed
test.
(if it's slower than it should be, it could be your problem. Then call your
ISP)

Another Shot in the dark sounds like your Primary DNS (From your ISP) is
Crappy

Call them up ask if the DNS server has changed been upgraded etc.
And of course make sure it's correct.

Also if you are using a 2NIC setup Check the server for SPYWARE
(hopefully they haven't surfed from the server and caused the server to
catch something.)

This would Definitely cause a slowness, but hopefully they don't surf from
the server...

I hope this helps
Russ


--
Russ Grover
Small Business IT Support
Portland\Beaverton OR USA
Email: Sales at SmallBusinessITSupport.com
Website: www.SmallBusinessITSupport.com


"Scott McBride" <ScottMcBride@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4B8F21EC-2E07-4168-BAA2-BEEA75926D77@xxxxxxxxxxxxxxxx
> Good day.
> I find myself in need of some help.
> I have a customer running SBS2003. Everything has been working well for
> over a year, but recently they have seen a lot of internet slowdowns and
> "page not found" errors. Usually, a refresh and the sites would then come
> right up.
> However, now they are in a situation where there are certain sites that
> just
> won't come up no matter what I try.
> The sites will come up fine on the server itself. I thought DNS, but I
> can
> ping the site name and get the correct IP address from both the server and
> on
> the clients. I checked out the event viewer on the server and found a
> number
> of errors with event ID 7063, but I checked and found that (according to
> the
> ISP) I am using the correct external DNS server addresses for my
> forwarders
> and that they are configured to allow recursion.
> I can even try using the sites IP address in the IE address bar, and it
> still won't come up on the clients.
> Most puzzling of all is that most of the sites on the internet work just
> fine though (e.g. google, microsoft, etc.).
> I have also changed the clients to try using the external DNS just to see
> if
> it would resolve, but still no luck.
> Again...works fine on the server...it just won't work on the clients.
> Should I run the ICW? Will that hose any of the current configurations we
> have set up?
>
> I am extremely puzzled by this and any help would be greatly appreciated.
>
> Best regards to all,
> Scott McBride


.



Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Permissions across 2 Forrest
    ... Primary DNS server on 1.x and the 18.x network along with DHCP and WINS. ... For instance ForrestA DNS is now a secondary for Forrest B and vise versa. ... WINS clients must use the same "WINS Database"* ...
    (microsoft.public.windows.server.active_directory)
  • Re: Still strange not fully working DNS server
    ... On none of the computers (both DC and clients) no firewall software is ... For the rest nothing happens in the DNS forward lookup zone. ... Is the new server Global catalog? ... The config you mentioned was not configured so I have configured ...
    (microsoft.public.windows.server.dns)
  • Re: Client installation frustration.
    ... not, apparently, any DNS lookup issues on my network. ... connection's addresses in DNS" and "Use this connection's DNS suffix in DNS ... is a file and print server that we have at one of our secondary sites. ... Is there any way to cancel all current requests to install clients? ...
    (microsoft.public.sms.admin)
  • Re: problem with xp clients and windows 2003
    ... We now have the cross cable running from the room's switch ... >> policy but logs into the server. ... >> aware that this is a DNS issue but I have TRIPLE checked the DNS ... >> If I do NSlookup from the problematic clients, ...
    (microsoft.public.windows.server.networking)