It turns out it was the driver.  The packet counts from windows were not
matching the ethereal packets, so I rolled back the drivers and everything
is back to normal.  Thanks for your help.

John roberts

-----Original Message-----
From: Kevin O'Shea [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, August 05, 2003 2:27 PM
To: [EMAIL PROTECTED]
Subject: RE: Windows XP computer spewing packets

Just went trough the same issue here re: packet count - There was no
correlation b/w the numbers of packets caught on ethereal and the local
area connection status counter.

Found a round-about reference at
http://eu.computers.toshiba-europe.com/cgi-bin/ToshibaCSG/faq.jsp?FID=tr
o0000001b96

Apparently its an error in the driver - I downloaded an updated driver
directly from intel and the problem is fixed.

The driver issue seems independent of your Nmap question...

Kevin


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] 
Sent: Friday, August 01, 2003 12:06 PM
To: [EMAIL PROTECTED]
Subject: Windows XP computer spewing packets

One of the employees here has a Windows laptop, and in the last day, it
has
sent out over 1,000,000,000,000 packets, and received around 30,000. The
30,000 is a standard load, but the trillion packets seem to be a bit
high. 
I've scanned for spyware and viruses and found nothing.  I tried to
nMapWin
from the network, and the computer didn't respond, and when he tried to
nMapWin his ports, he couldn't find himself, from his own computer.  Do
you
have any idea what could be causing this?  I'm not to keen on these
packets
flying around my network, and if there are security issues, I'm even
less
keen.

 

John roberts


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .



------------------------------------------------------------------------
---
------------------------------------------------------------------------
----


---------------------------------------------------------------------------
----------------------------------------------------------------------------



---------------------------------------------------------------------------
----------------------------------------------------------------------------

Reply via email to