network resources

Charles Crawford ccrawford at
Tue Dec 19 15:11:00 GMT 2000

All of the cables/NIC's/and Drivers check out fine.

One thing I've noticed (through the very useful program MRTG), is that this
appears to happen most frequently during peak usage hours. When I'm the only
one on the network, it hardly ever happens (I really can't remember it
occuring during such a time period, but I don't want to rule it out when
there is a chance I could be mistaken).

In the meantime, I'll email some RH lists and see what I come up with.



-----Original Message-----
From: Ron Alexander [mailto:rcalex at]
Sent: Tuesday, December 19, 2000 9:28 AM
To: Charles Crawford
Subject: RE: network resources

You appear to have done a very good job of analysis. The fact that the ping
is taking so long is the prime suspect. I am NOT a network expert, but I
have to know a little about it in order to support samba.

First rule out the following / howto:
1. Cables/swap with a known good one.
2. NIC's/swap with a known good one.
3. Drivers/check with manufacturer & newsgroups to make sure latest and no
known bugs that might be causing the problem.

I would then look into Linux. Post a question to the RH, Linux networking
and any others that might be helpfull. Simply post a query that asks what
can cause a ping to be 2x slower than windows.

Good luck, and let us know what it was.

-----Original Message-----
From: samba-technical-admin at
[mailto:samba-technical-admin at]On Behalf Of Charles
Sent: December 19, 2000 8:58 AM
To: Samba Listserve (E-mail)
Cc: Samba-Ntdom Listserve (E-mail); Samba-Technical Listserve (E-mail)
Subject: network resources


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