The default gateway is actually 192.168.0.101. When you experienced this issue, was just one station affected, or all? If I ping the same DG from other stations, I do not experience the timeouts.

Thanks!

On Mar 30, 2010, at 10:58 AM, Glen Johnson wrote:

Maybe a wild shot, but we had this problem once.
Is the default gateway 192.168.0.1?
Vendor brought in a DVR with had a static ip configured to that same.
Chased that one down for quite a while.
Could be someone brought in a wap or other device with same ip as the
default gateway.

-----Original Message-----
From: Eric Brouwer [mailto:[email protected]]
Sent: Tuesday, March 30, 2010 10:16 AM
To: NT System Admin Issues
Subject: Strange network issue

Good morning,

I'm having a very odd networking issue with one computer in the
office.  The machine in question is an HP box running XP Pro and is
used for video editing.  When the editor tries to access network
resources, he sometimes loses his network connection and his process
basically locks up.  This happens during simple file transfers through
Explorer.

Here's where it gets weird...

I started a continuos ping (ping -t) to the file server in question,
and everything looks great.  No lost packets at all.  I then ran the
same ping to the default gateway and I'm seeing a lot of Request time
outs.  I'd say 10-15% of the ping requests fail.

Any idea why I'd have trouble pinging the DG, but not a resource on
the other side of the DG?

Thank you,

Eric Brouwer
IT Manager
www.forestpost.com
[email protected]
248.855.4333





~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~



Eric Brouwer
IT Manager
www.forestpost.com
[email protected]
248.855.4333





~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to