>>>>> "Gaurav" == CAP  <Sabharwal> writes:

    Gaurav> Hey Raj, hmmm...Interesting. What does tcpdump or some
    Gaurav> other sniffer has to say about this mischief? I have seen
    Gaurav> these problems with the firewalls/masq devices that have
    Gaurav> not been configured properly and tend to slow down the
    Gaurav> connections. You must also be seeing that if you telnet to
    Gaurav> the server you get a prompt after ages. Is it the case? I
    Gaurav> know I am asking a wrong guy this stupid question, but is
    Gaurav> DNS, etc configured properly? I hope you are not trying to
    Gaurav> do any of the LDAP, etc gizmos.

No funky configurations.  The firewall works beautifully for Winduhs
boxen, I'm considering scrapping Linux and moving to Lose2000 now.

[Aargh!  NOT!  Tempting though it may be]

    Gaurav> What on the switch side? Have you checked the ports on the
    Gaurav> switch for any excessive collisions, giants, runts, etc?
    Gaurav> Are the ports configured properly?  If it's a 10/100 Mbps
    Gaurav> switch be sure that it is not configured for
    Gaurav> auto-negotiation for the bandwidth and the parameters are
    Gaurav> same as on the linux machines and vice-versa. The whole
    Gaurav> funda of auto-negotiation sucks in switches because every
    Gaurav> vendor having it's own standards. Connection goes for a
    Gaurav> toss or is disrupted every now and then because of the
    Gaurav> stupid auto-negotiation. I have seen this happening
    Gaurav> between Sun, Compaq and Cisco boxes.

Jeez, what's a giant/runt?  Hmm, s'pose I just force that port on the
switch to 100MB/s (or 10MB/s), might that make a difference?  I
seriously suspect the switch, since I've had this problem between IRIX 
machines connected to a similar (Nortel) switch in the past too.

    Gaurav> AFAIK, tcpdump is your best friend and should be able to
    Gaurav> help you with more clues on the problem or maybe by
    Gaurav> confusing you more :-) Or else put up a sniffer on a
    Gaurav> switch port...span the port to which the server is
    Gaurav> connected to the port sniffer is connected. With the help
    Gaurav> of span you will be able to see the same packets that are
    Gaurav> being sent to the server on the port on which the sniffer
    Gaurav> is connected and hence making packets available to you.

Are packets on 100MB/s ethernet larger than 1500 bytes (the 10MB/s eth 
packet limit)?  Could that be a problem with some machine or the
switch trying fragmentation/defragmentation on the way?

    Gaurav> Better still...hire me for a "small" fees ;-)

Done!  Beer at Float's (if your wife will let you spend the evening
out with the guys).  (Haahaa, gotcha!)

Regards,

-- Raju

    Gaurav> - Gaurav
    >> -----Original Message----- From: Raju Mathur
    >> [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 18, 2000
    >> 8:11 AM To: [EMAIL PROTECTED];
    >> [EMAIL PROTECTED] Subject: [linux-delhi]
    >> Network freezes
    >> 
    >> Hi,
    >> 
    >> I'm facing a weird problem with my network.  I have three
    >> systems (A, B and C) connected to each other using a Nortel
    >> switch.  A is a linux box is on a private IP, B is a Linux Masq
    >> system (both private and public IP's) and C is another Unix box
    >> outside the Masq, on a public IP.
    >> 
    >> I can transfer large files between B and C without problems.
    >> However, whenever I try to copy a large file from any Unix
    >> machine to A (using FTP, rcp, ssh, whatever), the connection
    >> freezes for long periods of time.  If I use a Winduhs machine
    >> instead of A, file transfers go through without any problems.
    >> Anyone seen this freezing problem with a switch earlier?  I
    >> haven't checked with a hub, but for a number of reasons I feel
    >> that the problem will disappear with a hub.
    >> 
    >> Regards,
    >> 
    >> -- Raju

-----------------------------------------------------------------------
For more information on the LIH mailing list see:
http://lists.linux-india.org/lists/LIH

Reply via email to