Well, I have a really strange problem with BeOS. It's about my internet connection. I connect to internet through LAN. Well, usually everything works fine, but the problem is that sometimes the connection "disappears". I just don't know how to call it: I can't browse internet, can't connect to anything. I'm off-line. Sometimes I have to wait for a few minutes for connection to re-appear and sometimes I have to restart net_server manually. After that, everything's OK again. I have no idea of what the problem is. I'm sure that it's a problem with OS, not with ISP. Drivers from BeBits.com didn't solve the problem. My network card is "Realtek 8139 10/100 Ethernet PCI (1)". I would appreciate any help. Thanks.

Can't say if it is a dns, dhcp, or network or what just yet. When it seems to get dead see what your IP is. If it is 0.0.0.0 or whatever it is supposed to be. See if you can ping something like google or better still get an IP of google or somewhere that replies to a ping and try the ping ip number when it seems dead.

It seems that IP doesn't change. It is the one that should be. However, pinging to Google or anywhere else gives no results. Moreover, it doesn't even write "ping timeout", there's just a black rectangular blinking and nothing else.

Can you test a local ping when it seems to go dead? Do you have a router/modem with a local ip web interface? I don't think I ever heard of this problem. Might also seach this and other forums for ideas.

Local ping doesn't work either and no, I don't have router or modem. Damn, this is really annoying. I tried to search Google for the solution, but I think, I've only wasted my time. It seems no-one has ever faced to such a problem. Maybe the best solution this time would be to leave the problem.

Uh..maybe you've already tried this, but as it seems so familiar to a problem i had once..have you tried replacing the ethernet cable between your computer and cable modem? Even if it checks out fine, sometimes they can be buggy, as im my case..despite checking out OK it still caused the identical prob..replacing the cable did the trick... Just a thought... %00

I like dominicus's idea also. Also when it dies try local host 127.0.0.1 (end of sentence). If that fails then yep the network stack is somehow locking up. Guess you could try betips dot net for any clues. How about you look into bios and see if there is a choice for failsafe setting or the slower settings. Might be just a bit too fast on some bus somewhere.