slow network speed

[threadhead]

hi i have a LAN consisting of 3 machines.
one slackware server with two NICS.
one win xp and one slackware client.

the ping times between the gateway and the windows machinea are good.
but always when i ping the slack client or vice versa the client pings one of those machines, the packet reply times are about 1000ms.
IMHO thats too high, isnt it? ;)

my problem is, that i dont know why this is happening.
the NIC in the slack client is using the tulip module.
do you need anything else to know?

thanks for your help

[je_fro]

What are the IP's involved?

[threadhead]

gateway - 192.168.0.1
win xp - 192.168.0.2
slack client - 192.168.0.3

[je_fro]

I don't really know why this worked for me, but I used different ##'s and it works...

try:

win xp - 192.168.10.2
slack client - 192.168.100.2

And the internal nic's 192.168.10.1 and 192.168.100.1

[threadhead]

hmm i think you have have a wrong imagination of what my network looks like


outgoing NIC
I
[slackware gateway]
I
other NIC (192.168.0.1)
I
I
I HUB I
/ \
/ \
win xp slack client

sorry for that bad image but i have no ascii art skills, lol.
you think i should change the ips?

EDIT: my god, this picture looks even worse when posting it. :D

[mdwatts]

IP address/hostnames setup for each client/server in their respective /etc/hosts?

[threadhead]

for the two slackware machines, the setup of the /etc/hosts file looks the same like that

192.168.0.1 host.slack host
192.168.0.2 win.slack win
192.168.0.3 linux.slack linux

thats it

[mdwatts]

Try the same for each client/server.

[threadhead]

i have this configuration on two of my boxes.
on windows this isnt required/ not needed by me.

so both of the linux slackware computers are configured that way.

[je_fro]

But I think you're getting collisions on your hub.
I'd try changing the IP's like this:

192.168.0.1 host.slack host
192.168.10.2 win.slack win
192.168.100.2 linux.slack linux

and leaving the gateways as 192.168.0.1 for both internal computers.
However, that's trial-and-error stuff from me. I don't know much about the multicast/routing/tcp-ip stuff......

[threadhead]

thanks for your help! both of you. ;)

i am tired, i am going to try that tomorrow. :)

[cowanrl]

Many times when you are pinging FROM a Linux machine, long ping times can be the result of the inability of the Linux machine to do a reverse DNS lookup on the IP address being pinged.
When you ping from your Slack machine try:

ping 192.168.0.2 -n

The -n prevents the Linux machine from doing the reverse DNS lookup and can really improve the ping times.

If that doesn't help any, do an ifconfig command before you execute the ping and note the number of errors and collisions on the Ethernet interface. Next, do the ping again and let it run about 10 iterations or more, then execute the ifconfig command again and see if the number of errors or collisions went up. If they did, you may have some kind of a physical problem on your network causing errors.

[threadhead]

hmm this is a tough problem.
today i tried it again.
when both computers, the server and the client, were ready i tried to ping the server from the slack client.
the ping times were great. something like 0.4ms.
but then a little later the ping times were horrible high again. like 1003.4ms.
i pinged the server about 20 times and made an ifconfig on eth0.
no errors or collisions.

the high ping times/network lag cannot be caused by the iptables firewall because when i flushed all the rules on the server. the network still lagged like ****.

i am confused by the fact, that it sometimes works between these two and between the windows box and server it works frequently.

the slack client was the gateway before in that network.
before it were two computers, one windows and the gateway.
now i got another box and installed again slack on it and configured it as the gateway.
maybe i forgot to remove something from the old gateway?
its not the iptable rules.
hope that helps...

this is messing me up :(

thanks