Another thing to look at: Are you running WINS on the Samba server? If this is an older/busy server, turn off WINS, as it can be a serious clock cycle eater. This happened to me, although I'm running a 486 as a small department file server (cheap, yet quite effective!). With WINS on, the system initially worked, but after a short while, began dropping connections. Turned off WINS, edited the hosts file, and now there are no more problems.
================================ Al Adcock Information Technologies Manager BMC Technologies 1911 Cauley Avenue Panama City Beach, FL 32407 Tel: 850-249-2222 Fax: 850-249-2226 [EMAIL PROTECTED] http://www.bmctechnologies.com ICQ: 179154 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Pete Peterson Sent: Wednesday, March 06, 2002 1:07 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: network selective packet loss > Message: 2 > Date: Tue, 05 Mar 2002 14:55:47 -0700 > To: [EMAIL PROTECTED] > From: Aaron M Daley <[EMAIL PROTECTED]> > Subject: network selective packet loss > Reply-To: [EMAIL PROTECTED] > > > > I get the following ping info on my mail server and now one of our file > > servers as well indicating that we may have been hacked or there's a > > virus spreading. Here are two ping results from the same machine. Ping > > results from the file server are identical.<br><br> > > PING 192.168.10.5 (192.168.10.5) from 192.168.10.60 : 56(84) bytes of > > data.<br> > > 64 bytes from 192.168.10.5: icmp_seq=0 ttl=128 time=0.8 ms<br> > > 64 bytes from 192.168.10.5: icmp_seq=1 ttl=128 time=80000.6 ms<br> > > 64 bytes from 192.168.10.5: icmp_seq=2 ttl=128 time=160000.3 ms<br> > > . > > . > > . > > No the interesting parts.<br><br> > > 1. This only happens when I ping from the problem server to another > > server or workstation on our private network. If I ping anything else, it > > comes back fine.<br><br> > > 2. If I ping either of these machines from any other computer on our > > private or public network the results are perfect.<br><br> > > 3. I've tried using different NIC's and also different switches. I've > > taken down the firewall on both machines as well as verified there was > > nothing in hosts deny or allow that might be blocking traffic.<br><br> > > 4. The problem was intermitent until a few days ago<br><br> > > 5. On the mail server mail con still be retrieved fro, anywhere except > > the private side network. If you're on our private side network then you > > can still receive mail but it takes about 3 minutes to make the > > connection, once the connection is made the mail comes through just fine, > > as if there was no packet loss what so ever.<br><br> > > 6. The file server can no longer be connected too from a PC on the > > private side network. We're using samba on the file server. If you're > > using a mac on our private side network it can still connect just fine as > > if there was no packet loss what so ever.<br><br> > > <br> > > OK so anyone ever seen anything like this before?<br><br> You didn't mention whether it mattered whether you specified the target machine by name or by IP. If it only happens when you specify by name, check /etc/resolv.conf and make sure it's specifying properly functioning name-servers. I had a similar problem a few weeks ago that turned out to be caused by a resolv.conf error. -- pete peterson Teradyne, Inc. 7 Technology Park Drive Westford, MA 01886-0033 [EMAIL PROTECTED] or [EMAIL PROTECTED] +1-978-589-7478 (Teradyne); +1-978-589-2088 (Closest FAX); +1-978-589-7007 (Main Teradyne Westford FAX) _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
