We have a server (Windows Server 2003 Ent R2) that keeps losing it's
internet connection. This is a problem as this server needs a constant
connection for continious off site backups.

It can go off for up to 25 minutes at a time and if left alone it will
eventually restore itself it seems. It looks like running ipconfig
/registerdns will fix it.



Server uses a static IP and is set up correctly. It has 2 NICS teamed using
the HP management software.

When the machine loses its internet connectivity it can still ping/access
other nmachines and still works in every other respect - it is running SQL
server and other machines have no problem accessing it.

Machine has had a reboot.

Any thoughts?

>

>
> Any thoughts?
>

Yes: Make up your mind. You write:

> When the machine loses its internet connectivity it can still
> ping/access other nmachines and still works in every other respect -
> it is running SQL server and other machines have no problem accessing it.
>

Pick one. You cannot have it both ways. Either your machine has lost
Internet Protocol connectivity, in which case it will be inaccessible
and ping won't work, or ping works and other machines can connect, in
which case your machine has not lost IP connectivity. Describe your
problem properly.

"Zebby" <someone@newsgroup> wrote in message
news:e%23OzpymnKHA.5344@newsgroup

> When the machine loses its internet connectivity it can still ping/access
> other nmachines and still works in every other respect - it is running SQL
> server and other machines have no problem accessing it.
>

So it looses internet connectivity, but not LAN connectivity?
Expand on what you mean by "internet connectivity"; just your backup site?
Or all internet connectivity.
Are other computers still able to access that/those site(s), at the same
time that the server cannot?

Yes to your first point, the server continues the work as normal in every
respect.

By 'internet connectivity' I mean I'm just getting page cannot be displayed
on any website, not just the one we use to manage the backups. No other
machine is affected.

"JohnB" <jbrigan@newsgroup> wrote in message
news:uNJEdXpnKHA.1548@newsgroup

> "Zebby" <someone@newsgroup> wrote in message
> news:e%23OzpymnKHA.5344@newsgroup

>> When the machine loses its internet connectivity it can still ping/access
>> other nmachines and still works in every other respect - it is running
>> SQL server and other machines have no problem accessing it.
>>

> So it looses internet connectivity, but not LAN connectivity?
> Expand on what you mean by "internet connectivity"; just your backup
> site? Or all internet connectivity.
> Are other computers still able to access that/those site(s), at the same
> time that the server cannot?
>
>
>
>

Sounds like it may be a DNS configuration problem.

Your DNS server(s) should be configured with *Forwarders* that point to your
ISP DNS servers. DNS on your server should point to itself. Your DHCP
should be configured to point your clients to your internal DNS server for
DNS.

Take a look at this article, if you have not configured it that way.
http://support.microsoft.com/kb/323380




"Zebby" <someone@newsgroup> wrote in message
news:udBM$ypnKHA.5552@newsgroup

> Yes to your first point, the server continues the work as normal in every
> respect.
>
> By 'internet connectivity' I mean I'm just getting page cannot be
> displayed on any website, not just the one we use to manage the backups.
> No other machine is affected.
>
> "JohnB" <jbrigan@newsgroup> wrote in message
> news:uNJEdXpnKHA.1548@newsgroup

>> "Zebby" <someone@newsgroup> wrote in message
>> news:e%23OzpymnKHA.5344@newsgroup

>>> When the machine loses its internet connectivity it can still
>>> ping/access other nmachines and still works in every other respect - it
>>> is running SQL server and other machines have no problem accessing it.
>>>

>> So it looses internet connectivity, but not LAN connectivity?
>> Expand on what you mean by "internet connectivity"; just your backup
>> site? Or all internet connectivity.
>> Are other computers still able to access that/those site(s), at the same
>> time that the server cannot?
>>
>>
>>
>>

>
>

By 'internet connectivity' I mean I'm just getting page cannot be displayed on any website, not just the one we use to manage the backups.




Come now!&nbsp; Conflating "Internet" and "World Wide Web" is a well-known error to avoid.



You have a WWW browser problem.&nbsp; There are many potential causes.&nbsp; For all we know, you could have misconfigured HTTP proxy settings or an erroneously shaped hole knocked in a firewall or a (mal)functioning malware filter.&nbsp; (JohnB is leaping to conclusions with no factual justification.)&nbsp; You need to do proper diagnosis.&nbsp; That starts with looking at the error messages.&nbsp; Look at the error messages.&nbsp; If you want help from other people, tell those other people the error messages, too.&nbsp; Then you run tests, systematically, to eliminate possibilities.

Sounds like it may be a DNS configuration problem.



You're leaping to conclusions with no factual basis.&nbsp; M. Zebby hasn't actually proven that that xyr WWW browser problem is a DNS problem.&nbsp; I can think of three potential non-DNS causes for such a problem off the top of my head, and those are just for starters.&nbsp; We have no information for narrowing the problem down.




Your DNS server(s) should be configured with Forwarders that point to your ISP DNS servers.



Balderdash.&nbsp; This is received wisdom that is wrong.&nbsp; There's nothing universally wrong with doing query resolution onesself, and there are good reasons for doing so.&nbsp; The decision about forwarding is a complex one, with factors for and against that have to be weighed.&nbsp; Simplistic "You should always do X." recipes are just plain wrong.&nbsp; Moreover, please think about what a DNS problem would cause before leaping to conclusions.&nbsp; M. Zebby hasn't proven that this is a DNS problem in the first place, and in fact the datum that other machines have no WWW browser problems indicates that this most certainly isn't a problem that is in any way affected by whether or not xyr proxy DNS server is doing forwarding.



"Doctor, I have a pain in my elbow."
"Ah, you must have cancer of the liver.&nbsp; Here's what to do when one has cancer of the liver ..."