Windows 2003 server causes router to crash

Newbie here. I have just set up a 2003 server on my network and it causes
the ADSL router (a USR 9003) to crash at random intervals. The router is
normally rock solid, and performs flawlessly with the server shut down. The
server is running DNS, the router provides DHCP and firewall. I can't see
anything obvious that would cause this, any clues on where I should be
looking? Many thanks

"Grizelli" <(E-Mail Removed)> wrote in message
news:16F56598-057D-4B87-9C76-(E-Mail Removed)...
> Newbie here. I have just set up a 2003 server on my network and it causes
> the ADSL router (a USR 9003) to crash at random intervals. The router is
> normally rock solid, and performs flawlessly with the server shut down.

There is really nothing that the server can DO to the
router that isn't a BUG on the router (and nothing
much likely that it can do even then.)

Replace the router or upgrade the firmware if that
is possible.

> The
> server is running DNS, the router provides DHCP and firewall.

Two DHCP servers might interfere with each other
but that would affect the clients and not likely cause
one to crash.

DNS is a passive services (clients must ask it a
question.)

BTW, chances are that you need to take a look at
the DHCP on the router anyway to make sure it
is NOT giving out it's own (or an ISP) DNS server
address.

> I can't see
> anything obvious that would cause this, any clues on where I should be
> looking? Many thanks

My thinking would be something odd about the
routers NIC or arp tables finding a bug in their
code when the server is online (extra entry, odd
response to particular MAC adddress, some
weirdness in the wiring.)



--
Herb Martin

Many thanks Herb, I'll take another look a the things that you suggest.
Different PCs come and go on the network all the time and don't cause this
problem, so I find it hard to beleive that the router has an inherent fault
of some kind - its been running fine for around a year, and the problem has
only appeared with the arrival of the server, and it disappears if the server
is shut down. I'm struggling :-(

Martin

"Herb Martin" wrote:

> "Grizelli" <(E-Mail Removed)> wrote in message
> news:16F56598-057D-4B87-9C76-(E-Mail Removed)...
> > Newbie here. I have just set up a 2003 server on my network and it causes
> > the ADSL router (a USR 9003) to crash at random intervals. The router is
> > normally rock solid, and performs flawlessly with the server shut down.
>
> There is really nothing that the server can DO to the
> router that isn't a BUG on the router (and nothing
> much likely that it can do even then.)
>
> Replace the router or upgrade the firmware if that
> is possible.
>
> > The
> > server is running DNS, the router provides DHCP and firewall.
>
> Two DHCP servers might interfere with each other
> but that would affect the clients and not likely cause
> one to crash.
>
> DNS is a passive services (clients must ask it a
> question.)
>
> BTW, chances are that you need to take a look at
> the DHCP on the router anyway to make sure it
> is NOT giving out it's own (or an ISP) DNS server
> address.
>
> > I can't see
> > anything obvious that would cause this, any clues on where I should be
> > looking? Many thanks
>
> My thinking would be something odd about the
> routers NIC or arp tables finding a bug in their
> code when the server is online (extra entry, odd
> response to particular MAC adddress, some
> weirdness in the wiring.)
>
>
>
> --
> Herb Martin
>
>
>
>

On Sat, 26 Feb 2005 12:09:04 -0800, "Grizelli"
<(E-Mail Removed)> wrote:

>Many thanks Herb, I'll take another look a the things that you suggest.
>Different PCs come and go on the network all the time and don't cause this
>problem, so I find it hard to beleive that the router has an inherent fault
>of some kind - its been running fine for around a year, and the problem has
>only appeared with the arrival of the server, and it disappears if the server
>is shut down. I'm struggling :-(

I'm assuming your server is a static IP and it and the router are not
the same IP. Also that the router DHCP doesn't have the server IP in
its scope.

Jeff


>"Herb Martin" wrote:
>
>> "Grizelli" <(E-Mail Removed)> wrote in message
>> news:16F56598-057D-4B87-9C76-(E-Mail Removed)...
>> > Newbie here. I have just set up a 2003 server on my network and it causes
>> > the ADSL router (a USR 9003) to crash at random intervals. The router is
>> > normally rock solid, and performs flawlessly with the server shut down.
>>
>> There is really nothing that the server can DO to the
>> router that isn't a BUG on the router (and nothing
>> much likely that it can do even then.)
>>
>> Replace the router or upgrade the firmware if that
>> is possible.
>>
>> > The
>> > server is running DNS, the router provides DHCP and firewall.
>>
>> Two DHCP servers might interfere with each other
>> but that would affect the clients and not likely cause
>> one to crash.
>>
>> DNS is a passive services (clients must ask it a
>> question.)
>>
>> BTW, chances are that you need to take a look at
>> the DHCP on the router anyway to make sure it
>> is NOT giving out it's own (or an ISP) DNS server
>> address.
>>
>> > I can't see
>> > anything obvious that would cause this, any clues on where I should be
>> > looking? Many thanks
>>
>> My thinking would be something odd about the
>> routers NIC or arp tables finding a bug in their
>> code when the server is online (extra entry, odd
>> response to particular MAC adddress, some
>> weirdness in the wiring.)
>>
>>
>>
>> --
>> Herb Martin
>>
>>
>>
>>

"Grizelli" <(E-Mail Removed)> wrote in message
news:5C8F04BE-5F26-451D-B674-(E-Mail Removed)...
> Many thanks Herb, I'll take another look a the things that you suggest.
> Different PCs come and go on the network all the time and don't cause this
> problem, so I find it hard to beleive that the router has an inherent
fault
> of some kind - its been running fine for around a year, and the problem
has
> only appeared with the arrival of the server, and it disappears if the
server
> is shut down. I'm struggling :-(

Let's make it really simple: By definition if
you can crash that router by sending it something
on the network then the router has a bug.

Routers should AT LEAST survive whatever
traffic they are asked to handle.

--
Herb Martin


>
> Martin
>
> "Herb Martin" wrote:
>
> > "Grizelli" <(E-Mail Removed)> wrote in message
> > news:16F56598-057D-4B87-9C76-(E-Mail Removed)...
> > > Newbie here. I have just set up a 2003 server on my network and it
causes
> > > the ADSL router (a USR 9003) to crash at random intervals. The router
is
> > > normally rock solid, and performs flawlessly with the server shut
down.
> >
> > There is really nothing that the server can DO to the
> > router that isn't a BUG on the router (and nothing
> > much likely that it can do even then.)
> >
> > Replace the router or upgrade the firmware if that
> > is possible.
> >
> > > The
> > > server is running DNS, the router provides DHCP and firewall.
> >
> > Two DHCP servers might interfere with each other
> > but that would affect the clients and not likely cause
> > one to crash.
> >
> > DNS is a passive services (clients must ask it a
> > question.)
> >
> > BTW, chances are that you need to take a look at
> > the DHCP on the router anyway to make sure it
> > is NOT giving out it's own (or an ISP) DNS server
> > address.
> >
> > > I can't see
> > > anything obvious that would cause this, any clues on where I should be
> > > looking? Many thanks
> >
> > My thinking would be something odd about the
> > routers NIC or arp tables finding a bug in their
> > code when the server is online (extra entry, odd
> > response to particular MAC adddress, some
> > weirdness in the wiring.)
> >
> >
> >
> > --
> > Herb Martin
> >
> >
> >
> >

> I'm assuming your server is a static IP and it and the router are not
> the same IP. Also that the router DHCP doesn't have the server IP in
> its scope.

Now that is an interesting idea -- years
ago it was not uncommon for some (UNIX)
systems to crash on duplicate addresses.

Still a bug on the router or any machine that
does this but that might account for it.

--
Herb Martin


"Jeff Cochran" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> On Sat, 26 Feb 2005 12:09:04 -0800, "Grizelli"
> <(E-Mail Removed)> wrote:
>
> >Many thanks Herb, I'll take another look a the things that you suggest.
> >Different PCs come and go on the network all the time and don't cause
this
> >problem, so I find it hard to beleive that the router has an inherent
fault
> >of some kind - its been running fine for around a year, and the problem
has
> >only appeared with the arrival of the server, and it disappears if the
server
> >is shut down. I'm struggling :-(
>
> I'm assuming your server is a static IP and it and the router are not
> the same IP. Also that the router DHCP doesn't have the server IP in
> its scope.
>
> Jeff
>
>
> >"Herb Martin" wrote:
> >
> >> "Grizelli" <(E-Mail Removed)> wrote in message
> >> news:16F56598-057D-4B87-9C76-(E-Mail Removed)...
> >> > Newbie here. I have just set up a 2003 server on my network and it
causes
> >> > the ADSL router (a USR 9003) to crash at random intervals. The
router is
> >> > normally rock solid, and performs flawlessly with the server shut
down.
> >>
> >> There is really nothing that the server can DO to the
> >> router that isn't a BUG on the router (and nothing
> >> much likely that it can do even then.)
> >>
> >> Replace the router or upgrade the firmware if that
> >> is possible.
> >>
> >> > The
> >> > server is running DNS, the router provides DHCP and firewall.
> >>
> >> Two DHCP servers might interfere with each other
> >> but that would affect the clients and not likely cause
> >> one to crash.
> >>
> >> DNS is a passive services (clients must ask it a
> >> question.)
> >>
> >> BTW, chances are that you need to take a look at
> >> the DHCP on the router anyway to make sure it
> >> is NOT giving out it's own (or an ISP) DNS server
> >> address.
> >>
> >> > I can't see
> >> > anything obvious that would cause this, any clues on where I should
be
> >> > looking? Many thanks
> >>
> >> My thinking would be something odd about the
> >> routers NIC or arp tables finding a bug in their
> >> code when the server is online (extra entry, odd
> >> response to particular MAC adddress, some
> >> weirdness in the wiring.)
> >>
> >>
> >>
> >> --
> >> Herb Martin
> >>
> >>
> >>
> >>
>

Can't argue with that. I'm going to try the idea of taking the server
address out of the DHCP scope and see if it solves the problem. Thanks for
all the suggestions, I'll report back later.

Martin


> Let's make it really simple: By definition if
> you can crash that router by sending it something
> on the network then the router has a bug.
>
> Routers should AT LEAST survive whatever
> traffic they are asked to handle.
>
> --
> Herb Martin
>
>
>

"Grizelli" <(E-Mail Removed)> wrote in message
news:CC760344-6043-47F0-8CDB-(E-Mail Removed)...
> Can't argue with that. I'm going to try the idea of taking the server
> address out of the DHCP scope and see if it solves the problem. Thanks
for
> all the suggestions, I'll report back later.

Well, the router/DHCP should not be
giving out an address in use anyway.

(Some -- e.g., MS -- probe first so maybe
the bug is in THAT part of the router code.)



--
Herb Martin


>
> Martin
>
>
> > Let's make it really simple: By definition if
> > you can crash that router by sending it something
> > on the network then the router has a bug.
> >
> > Routers should AT LEAST survive whatever
> > traffic they are asked to handle.
> >
> > --
> > Herb Martin
> >
> >
> >

Well, as expected, it ain't the DHCP/address. The crash seems to happen
after a number of hours, around 3 or 4, and mostly when there are no live
internet connections going on, but can't see anything in the server activity
logs to identify a possible event that might be the cause. I've killed AD
and restarted the server, lets see if that highlights where the problem with
the router is. More later...

Martin

"Herb Martin" wrote:

>>
> Well, the router/DHCP should not be
> giving out an address in use anyway.
>
> (Some -- e.g., MS -- probe first so maybe
> the bug is in THAT part of the router code.)
>
>
>
> --
> Herb Martin
>
>
> >
> > Martin
> >
> >
> > > Let's make it really simple: By definition if
> > > you can crash that router by sending it something
> > > on the network then the router has a bug.
> > >
> > > Routers should AT LEAST survive whatever
> > > traffic they are asked to handle.
> > >
> > > --
> > > Herb Martin
> > >
> > >
> > >
>
>
>

"Grizelli" <(E-Mail Removed)> wrote in message
news:23D53989-5BA3-465E-961A-(E-Mail Removed)...
> Well, as expected, it ain't the DHCP/address. The crash seems to happen
> after a number of hours, around 3 or 4, and mostly when there are no live
> internet connections going on, but can't see anything in the server
activity
> logs to identify a possible event that might be the cause. I've killed AD
> and restarted the server, lets see if that highlights where the problem
with
> the router is. More later...

"Killing AD" or looking in the server logs
is NOT going to solve you problem with this
ROUTER.

It is just silly to focus on AD for such a problem.

Upgrade the firmware on the router or seek help
from the router newsgroups/help desk.