network resources

Charles Crawford ccrawford at
Tue Dec 19 16:50:23 GMT 2000

WINS/DNS enables one to ping by hostname. The response time is irrelevant if
the machine cannot locate the host.

When I say the response time is doubled, I mean the total round-trip time,
not the time it took for the machine being pinged to respond to the ping

The NIC's are fine, and so are the Cisco Switches. The problem appears to be
an issue of how NT and Samba/Linux interact with each other. The response
time being doubled indicates to me that the traffic is traveling twice the
distance, not being held up somewhere... BTW, it is EXACTLY twice the time,
so I think that that indicates an extra trip for each packet to the
destination machine.


-----Original Message-----
From: Welsh, Armand [mailto:armand.welsh at]
Sent: Tuesday, December 19, 2000 11:46 AM
To: Samba Listserve (E-mail)
Cc: Samba-Ntdom Listserve (E-mail); Samba-Technical Listserve (E-mail)
Subject: RE: network resources

WINS/DNS, and other stuff like that, won't help your ping times.  The only
way to improve your ping time, is to determine what is slowing it down.    I
suggest you check the network port your linux box is connected to, to verify
that you are not receiving excessive collisions, or excessive line chatter.
I would also suggest trying to swap your network interface cards, and such.
Of course, make sure your server is on a switch, not a hub, so that traffic
to the server is limited to only server bound traffic.

-> -----Original Message-----
-> From: Charles Crawford [mailto:ccrawford at]
-> Sent: Tuesday, December 19, 2000 5:58 AM
-> To: Samba Listserve (E-mail)
-> Cc: Samba-Ntdom Listserve (E-mail); Samba-Technical 
-> Listserve (E-mail)
-> Subject: network resources
-> Hi, 
-> I'm having problems getting Samba shares to respond quickly 
-> enough to not
-> time-out on our NT network.
-> I've got a login script that creates a mapped drive to a 
-> share, but it tells
-> me that the server is not responding and that I might not have enough
-> network resources available to make the connection.
-> The systems that run Samba are all Red Hat Linux 6.1 
-> systems, with Samba
-> 2.0.5a-12 on one, and Samba 2.0.7-4 on the other. I don't 
-> think that this is
-> a Samba issue directly, but it is causing some difficulty 
-> and is causing
-> concern among management in regards to the effective use of 
-> Samba in our
-> networking environment.
-> Once the connection is made, which sometimes takes several 
-> login attempts,
-> there appear to be no problems. One item worth noting, 
-> however, is that
-> pinging any of the Linux machines brings a response time 2 
-> times that of the
-> Windows machines. I've made sure that the IP addresses are 
-> included in the
-> WINS database, the host and lmhost files, and in the Server Manager.
-> The names resolve to the correct machines, but sometimes the 
-> connection is
-> very slow. I'm starting to think that Linux is misconfigured 
-> to allow a
-> small number of network connections, or that the switches 
-> are bottle-necking
-> the network connections. Anyone have any ideas?
-> Charlie Crawford, 
-> ccrawford at

More information about the samba-technical mailing list