Windows 2003 Killing My Router

Dear Anyone,

I've recently migrated a peer to peer network to a Win 2003 Domain
controlled environment. Before the change Internet Access via a
broadband connection was working perfectly.

Since the first day of introducing the server I'm now experiencing
problems accessing, not only the router itself, but also the
Internet/email/outside world.

Ping packets are simply being dropped or just taking thousands of mili
seconds to respond. I've examined the possibilty of it being Virus
related but firmly believe this not to be the case. The problem
occurs at random intervals and requires a physical reboot of the
router for it to come back to life. It seems as if the router gets
tied up in some task that takes up 100% of it's time and dis-regards
everything else. When the problem does occur I've even disconnected
the router from the network and connected it to a single PC to see if
it recovers itself, only to find the problem still persists and only a
power cycle fixes it. Is Win 2003 creating particular network traffic
that causes routers to crash? I can't say I've ever experienced this
before. The router in question is a Turbocomm EA110.

Any ideas or solutions would be greatly appreciated.

Regards

SG

Set all clients to use the DNS on your Domain Controller and not the ISP's
DNS. Then in your DNS create a "Forwarders List" that includes the ISP's
DNS Server(s). If all your clients get addesses via DHCP from the Turbocomm
box, then make sure it refects this change in the DNS server the clients
use.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"SG" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Dear Anyone,
>
> I've recently migrated a peer to peer network to a Win 2003 Domain
> controlled environment. Before the change Internet Access via a
> broadband connection was working perfectly.
>
> Since the first day of introducing the server I'm now experiencing
> problems accessing, not only the router itself, but also the
> Internet/email/outside world.
>
> Ping packets are simply being dropped or just taking thousands of mili
> seconds to respond. I've examined the possibilty of it being Virus
> related but firmly believe this not to be the case. The problem
> occurs at random intervals and requires a physical reboot of the
> router for it to come back to life. It seems as if the router gets
> tied up in some task that takes up 100% of it's time and dis-regards
> everything else. When the problem does occur I've even disconnected
> the router from the network and connected it to a single PC to see if
> it recovers itself, only to find the problem still persists and only a
> power cycle fixes it. Is Win 2003 creating particular network traffic
> that causes routers to crash? I can't say I've ever experienced this
> before. The router in question is a Turbocomm EA110.
>
> Any ideas or solutions would be greatly appreciated.
>
> Regards
>
> SG

Cheers for the reply Phillip.

However, all you mentioned is already in place. Only the 2003 server
is acting as the DHCP server and all clients pick up the dns settings
from there. All DNS is via the server with the forwarders list
already created.

When the router works all internet access via the clients works fine.
It's just the router dying at totally random intervals.

SG



"Phillip Windell" <@.> wrote in message news:<(E-Mail Removed)>...
> Set all clients to use the DNS on your Domain Controller and not the ISP's
> DNS. Then in your DNS create a "Forwarders List" that includes the ISP's
> DNS Server(s). If all your clients get addesses via DHCP from the Turbocomm
> box, then make sure it refects this change in the DNS server the clients
> use.
>
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "SG" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) om...
> > Dear Anyone,
> >
> > I've recently migrated a peer to peer network to a Win 2003 Domain
> > controlled environment. Before the change Internet Access via a
> > broadband connection was working perfectly.
> >
> > Since the first day of introducing the server I'm now experiencing
> > problems accessing, not only the router itself, but also the
> > Internet/email/outside world.
> >
> > Ping packets are simply being dropped or just taking thousands of mili
> > seconds to respond. I've examined the possibilty of it being Virus
> > related but firmly believe this not to be the case. The problem
> > occurs at random intervals and requires a physical reboot of the
> > router for it to come back to life. It seems as if the router gets
> > tied up in some task that takes up 100% of it's time and dis-regards
> > everything else. When the problem does occur I've even disconnected
> > the router from the network and connected it to a single PC to see if
> > it recovers itself, only to find the problem still persists and only a
> > power cycle fixes it. Is Win 2003 creating particular network traffic
> > that causes routers to crash? I can't say I've ever experienced this
> > before. The router in question is a Turbocomm EA110.
> >
> > Any ideas or solutions would be greatly appreciated.
> >
> > Regards
> >
> > SG

Maybe it is time for a new router.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"SG" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) m...
> Cheers for the reply Phillip.
>
> However, all you mentioned is already in place. Only the 2003 server
> is acting as the DHCP server and all clients pick up the dns settings
> from there. All DNS is via the server with the forwarders list
> already created.
>
> When the router works all internet access via the clients works fine.
> It's just the router dying at totally random intervals.
>
> SG
>
>
>
> "Phillip Windell" <@.> wrote in message
news:<(E-Mail Removed)>...
> > Set all clients to use the DNS on your Domain Controller and not the
ISP's
> > DNS. Then in your DNS create a "Forwarders List" that includes the
ISP's
> > DNS Server(s). If all your clients get addesses via DHCP from the
Turbocomm
> > box, then make sure it refects this change in the DNS server the clients
> > use.
> >
> >
> > --
> >
> > Phillip Windell [MCP, MVP, CCNA]
> > www.wandtv.com
> >
> >
> > "SG" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed) om...
> > > Dear Anyone,
> > >
> > > I've recently migrated a peer to peer network to a Win 2003 Domain
> > > controlled environment. Before the change Internet Access via a
> > > broadband connection was working perfectly.
> > >
> > > Since the first day of introducing the server I'm now experiencing
> > > problems accessing, not only the router itself, but also the
> > > Internet/email/outside world.
> > >
> > > Ping packets are simply being dropped or just taking thousands of mili
> > > seconds to respond. I've examined the possibilty of it being Virus
> > > related but firmly believe this not to be the case. The problem
> > > occurs at random intervals and requires a physical reboot of the
> > > router for it to come back to life. It seems as if the router gets
> > > tied up in some task that takes up 100% of it's time and dis-regards
> > > everything else. When the problem does occur I've even disconnected
> > > the router from the network and connected it to a single PC to see if
> > > it recovers itself, only to find the problem still persists and only a
> > > power cycle fixes it. Is Win 2003 creating particular network traffic
> > > that causes routers to crash? I can't say I've ever experienced this
> > > before. The router in question is a Turbocomm EA110.
> > >
> > > Any ideas or solutions would be greatly appreciated.
> > >
> > > Regards
> > >
> > > SG

Cheers to all for the assist.

Everything pointed to the router at the end of the day. Just pure
co-incidence it started happening the same time the server was
installed. Firmware upgrade cracked it.

Thanks.




"Phillip Windell" <@.> wrote in message news:<(E-Mail Removed)>...
> Maybe it is time for a new router.
>
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
> "SG" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) m...
> > Cheers for the reply Phillip.
> >
> > However, all you mentioned is already in place. Only the 2003 server
> > is acting as the DHCP server and all clients pick up the dns settings
> > from there. All DNS is via the server with the forwarders list
> > already created.
> >
> > When the router works all internet access via the clients works fine.
> > It's just the router dying at totally random intervals.
> >
> > SG
> >
> >
> >
> > "Phillip Windell" <@.> wrote in message
> news:<(E-Mail Removed)>...
> > > Set all clients to use the DNS on your Domain Controller and not the
> ISP's
> > > DNS. Then in your DNS create a "Forwarders List" that includes the
> ISP's
> > > DNS Server(s). If all your clients get addesses via DHCP from the
> Turbocomm
> > > box, then make sure it refects this change in the DNS server the clients
> > > use.
> > >
> > >
> > > --
> > >
> > > Phillip Windell [MCP, MVP, CCNA]
> > > www.wandtv.com
> > >
> > >
> > > "SG" <(E-Mail Removed)> wrote in message
> > > news:(E-Mail Removed) om...
> > > > Dear Anyone,
> > > >
> > > > I've recently migrated a peer to peer network to a Win 2003 Domain
> > > > controlled environment. Before the change Internet Access via a
> > > > broadband connection was working perfectly.
> > > >
> > > > Since the first day of introducing the server I'm now experiencing
> > > > problems accessing, not only the router itself, but also the
> > > > Internet/email/outside world.
> > > >
> > > > Ping packets are simply being dropped or just taking thousands of mili
> > > > seconds to respond. I've examined the possibilty of it being Virus
> > > > related but firmly believe this not to be the case. The problem
> > > > occurs at random intervals and requires a physical reboot of the
> > > > router for it to come back to life. It seems as if the router gets
> > > > tied up in some task that takes up 100% of it's time and dis-regards
> > > > everything else. When the problem does occur I've even disconnected
> > > > the router from the network and connected it to a single PC to see if
> > > > it recovers itself, only to find the problem still persists and only a
> > > > power cycle fixes it. Is Win 2003 creating particular network traffic
> > > > that causes routers to crash? I can't say I've ever experienced this
> > > > before. The router in question is a Turbocomm EA110.
> > > >
> > > > Any ideas or solutions would be greatly appreciated.
> > > >
> > > > Regards
> > > >
> > > > SG