i just installed Manrake 9.2, and sometimes when i'm doing something over the network OR internet the whole thing will lock up. Most of the time it's when i'm doing something that involves a lot of network traffic; it's happened while i've been downloading files, using vnc over the LAN, or copying files over the LAN. The download will just freeze or vnc will not respond, and then i can't go to any websites because they all timeout, and i can't even ping any computers on my LAN. The only way to fix it is:

service network restart

When i installed Mandrake 9.2, i installed it with all of the available server services, but i'm not really using them right now:

http://www.linuxquestions.org/questi...hreadid=125728

Could one of these possibly be locking up my network? What are some common issues that would possibly cause it to lock up?

i've removed all the services i'm not using, but i'm still having the same problem. it's irritating because i can't transfer large files to or from the computer. a small amount will transfer and then it will just stall, and i have to cancel the transfer and:

service network restart

...anyone have any ideas?

here is a partial dump of my /var/log/messages file right after it locks up again then i restart it:

Dec 28 20:08:04 pionex network: Bringing up interface eth0: succeeded
Dec 28 20:08:13 pionex network: Shutting down interface eth0: succeeded
Dec 28 20:08:14 pionex network: Shutting down loopback interface: succeeded
Dec 28 20:08:14 pionex network: Setting network parameters: succeeded
Dec 28 20:08:16 pionex network: Bringing up loopback interface: succeeded
Dec 28 20:08:17 pionex ifup: Determining IP information for eth0...
Dec 28 20:08:21 pionex dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Dec 28 20:08:21 pionex dhclient: DHCPACK from 192.168.1.1
Dec 28 20:08:21 pionex dhclient: bound to 192.168.1.13 -- renewal in 112194 seconds.
Dec 28 20:08:21 pionex ifup: done.
Dec 28 20:08:22 pionex network: Bringing up interface eth0: succeeded
Dec 28 20:11:40 pionex smbd[21723]: [2003/12/28 20:11:40, 0] lib/util_sock.c:wri
te_socket_data(499)
Dec 28 20:11:40 pionex smbd[21723]: write_socket_data: write failure. Error = Connection reset by peer
Dec 28 20:11:40 pionex smbd[21723]: [2003/12/28 20:11:40, 0] lib/util_sock.c:write_socket(524)
Dec 28 20:11:40 pionex smbd[21723]: write_socket: Error writing 61503 bytes to socket 5: ERRNO = Connection reset by peer
Dec 28 20:11:40 pionex smbd[21723]: [2003/12/28 20:11:40, 0] lib/util_sock.c:send_smb(704)
Dec 28 20:11:40 pionex smbd[21723]: Error writing 61503 bytes to client. -1. (Connection reset by peer)

...and then it locks up again. i was trying to transfer a large file (700 mb) over the network via samba. like i said before, small files transfer just fine. could i maybe get this topic transferred to the linux networking forums??

i guess i'll keep updating this thread until i get some help or fix this problem. i just switched to runlevel 1 (init 1), started up my network (service network start), started up samba (service smb start), and i can copy large files just fine. it seems to me like some other service that is running during one of the other runlevels is conflicting or killing my network somehow. no idea what yet...

This is what happens after I try to view/copy large files on my linux machine from my win2000 machine:

64 bytes from 192.168.1.11: icmp_seq=413 ttl=128 time=12000 ms
64 bytes from 192.168.1.11: icmp_seq=414 ttl=128 time=11000 ms
64 bytes from 192.168.1.11: icmp_seq=415 ttl=128 time=10000 ms
64 bytes from 192.168.1.11: icmp_seq=416 ttl=128 time=9000 ms
64 bytes from 192.168.1.11: icmp_seq=417 ttl=128 time=8000 ms
64 bytes from 192.168.1.11: icmp_seq=418 ttl=128 time=7000 ms
64 bytes from 192.168.1.11: icmp_seq=419 ttl=128 time=6000 ms
64 bytes from 192.168.1.11: icmp_seq=420 ttl=128 time=5000 ms
64 bytes from 192.168.1.11: icmp_seq=421 ttl=128 time=4000 ms
64 bytes from 192.168.1.11: icmp_seq=422 ttl=128 time=3000 ms
64 bytes from 192.168.1.11: icmp_seq=423 ttl=128 time=2000 ms
64 bytes from 192.168.1.11: icmp_seq=424 ttl=128 time=1000 ms
64 bytes from 192.168.1.11: icmp_seq=434 ttl=128 time=0.350 ms
64 bytes from 192.168.1.11: icmp_seq=426 ttl=128 time=8000 ms
64 bytes from 192.168.1.11: icmp_seq=427 ttl=128 time=7000 ms
64 bytes from 192.168.1.11: icmp_seq=428 ttl=128 time=6000 ms
64 bytes from 192.168.1.11: icmp_seq=429 ttl=128 time=5000 ms
64 bytes from 192.168.1.11: icmp_seq=430 ttl=128 time=4000 ms
64 bytes from 192.168.1.11: icmp_seq=431 ttl=128 time=3000 ms
64 bytes from 192.168.1.11: icmp_seq=432 ttl=128 time=2000 ms
64 bytes from 192.168.1.11: icmp_seq=433 ttl=128 time=1000 ms

[1]+ Stopped ping 192.168.1.11
[root@pionex downloads]# service network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0: [ OK ]
[root@pionex downloads]# ping 192.168.1.11
PING 192.168.1.11 (192.168.1.11) 56(84) bytes of data.
64 bytes from 192.168.1.11: icmp_seq=1 ttl=128 time=0.629 ms
64 bytes from 192.168.1.11: icmp_seq=2 ttl=128 time=0.336 ms
64 bytes from 192.168.1.11: icmp_seq=3 ttl=128 time=0.348 ms
64 bytes from 192.168.1.11: icmp_seq=4 ttl=128 time=0.350 ms
64 bytes from 192.168.1.11: icmp_seq=5 ttl=128 time=0.345 ms
64 bytes from 192.168.1.11: icmp_seq=6 ttl=128 time=0.344 ms
64 bytes from 192.168.1.11: icmp_seq=7 ttl=128 time=0.349 ms
64 bytes from 192.168.1.11: icmp_seq=8 ttl=128 time=0.350 ms
64 bytes from 192.168.1.11: icmp_seq=9 ttl=128 time=0.349 ms
64 bytes from 192.168.1.11: icmp_seq=10 ttl=128 time=0.318 ms

doesn't make any sense to me. i did find a similar thread though, so i'll try samba 3.0 which is what it suggests:

http://www.linuxquestions.org/questi...hreadid=119811

can an admin/moderator please move this post to linux networking? i'm obviously not getting any help from this forum. i think it should be possible for someone to move their own post to another forum...

well i installed samba3 and it doesn't fix anything. i am beginning to believe the problem isn't with samba, because to fix it i restart my eth0 interface. it also seems to "lock up" whenever downloading large files, and so samba should have nothing to do with this. i believe it is not locking up completely, but slowing down considerably. normal ping is about 0.3 ms, and after "locking up" it will jump to anywhere from 1000 ms to 12000 ms, which makes it impossible to do anything because everything times out. it looks like my downloads actually still continue, though. i will only get 1 kb every few seconds though, which is completely unfeasible.

Not sure whether you ever solved this, but I've been having pretty much the same problem as you. I finally found, after much searching on Google, something that slightly improves things and maybe will help get a proper solution.

If you look at this link you'll see in the last post that this bloke set his network card on the Windows machine to 10M full duplex. I have now done this and it helps a bit in that I can copy more information before it stalls and the stalls don't seem to last as long.

I was chatting to a friend about it and he was saying a friend of his had a similar issue and it was to do with having a network sniffer running on Linux. AFAIK, I don't have one running, but am not sure what to look for on that.

Whatever it is, I would love to know what it is and how to fix it. It's driving me nuts.

Just curious as to why you haven't upgraded from 9.2? That's quite old, I'd wonder whether whatever remote servers you're dealing with are having trouble "keeping down" (as opposed to "up") with your system. Also, since you haven't upgraded in a while I assume you have older hardware as well... perhaps you're witnessing the beginnings of hardware failure? ...don't know,just guessing here. But you should try at least 2006 and see if your problem persists.

Note that the post was made in 2003

erg~ my eyes are out runnin' my glasses by three lengths...