outgoing TCP connectiosn stop aftes several hours working in suse8.2

i've a server workin 24 hours/day, with suse8.2. I've amule working on
it. When it work during 2 or 3 days it stops connecting inet. I open a
navigator window an .... no posible connection but if i tri a ping or
a dig or someting similar it works. it seem that tcp connectiosn are
blocked but no udp connections. I dont know how to solve it, if a do a
/etc/init.d/network restart it continuos the same, the unique way to
solve it is to restart the server.

¿any ideas?

TIA

Fernando Peral <(E-Mail Removed)> wrote:
> i've a server workin 24 hours/day, with suse8.2. I've amule working on
> it. When it work during 2 or 3 days it stops connecting inet. I open a
> navigator window an .... no posible connection but if i tri a ping or
> a dig or someting similar it works. it seem that tcp connectiosn are
> blocked but no udp connections.

Can you connect using TCP to anything on the same subnet?

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!

Fernando Peral <(E-Mail Removed)> wrote:
> Cameron Kerr wrote:

>> Can you connect using TCP to anything on the same subnet?

> yes, i cant open any http conextion with any "outside" server, but i can
> with "my own" webserver or with the webserver on the ADSL router.

Running any firewalls?

Does it happen on other machines behind the router?

What if you boot something like Knoppix on the same machine?

This is ringing a bell in my head somewhere, something about NAT
timouts IIRC.

--
Cameron Kerr
(E-Mail Removed) : http://nzgeeks.org/cameron/
Empowered by Perl!

Cameron Kerr wrote:
> Fernando Peral <(E-Mail Removed)> wrote:
>
>>i've a server workin 24 hours/day, with suse8.2. I've amule working on
>>it. When it work during 2 or 3 days it stops connecting inet. I open a
>>navigator window an .... no posible connection but if i tri a ping or
>>a dig or someting similar it works. it seem that tcp connectiosn are
>>blocked but no udp connections.
>
>
> Can you connect using TCP to anything on the same subnet?
>

yes, i cant open any http conextion with any "outside" server, but i can
with "my own" webserver or with the webserver on the ADSL router.

On 18 Jun 2004, Cameron Kerr <(E-Mail Removed)> wrote:
> Fernando Peral <(E-Mail Removed)> wrote:
>> Cameron Kerr wrote:
>
>>> Can you connect using TCP to anything on the same subnet?
>
>> yes, i cant open any http conextion with any "outside" server, but i can
>> with "my own" webserver or with the webserver on the ADSL router.
>
> Running any firewalls?
>
> Does it happen on other machines behind the router?
>
> What if you boot something like Knoppix on the same machine?
>
> This is ringing a bell in my head somewhere, something about NAT
> timouts IIRC.

Most likely the common problem of internet file sharing (amule) consuming
all NAT ports on the firewall. Or, if your upload becomes saturated
(choked) it can choke downloading, because acknowledgements for received
packets have to wait in line in the choked upload stream.

--
David Efflandt - All spam ignored http://www.de-srv.com/

David Efflandt wrote:
> On 18 Jun 2004, Cameron Kerr <(E-Mail Removed)> wrote:
>
>>Fernando Peral <(E-Mail Removed)> wrote:
>>
>>>Cameron Kerr wrote:
>>
>>>>Can you connect using TCP to anything on the same subnet?
>>
>>>yes, i cant open any http conextion with any "outside" server, but i can
>>>with "my own" webserver or with the webserver on the ADSL router.
>>
>>Running any firewalls?


there is no firewall. There is an ADSL router with NAT but


>>
>>Does it happen on other machines behind the router?

no


>>
>>What if you boot something like Knoppix on the same machine?
>>
>>This is ringing a bell in my head somewhere, something about NAT
>>timouts IIRC.
>
>
> Most likely the common problem of internet file sharing (amule)


we have amule running in that computer, but it stops downloading but no
uploading. Before we had amule in it, the same thing happen (blocked
connections and need to restart), but more or less once or twice a
month, now with the mule it happens each two or three days.

> consuming
> all NAT ports on the firewall. Or, if your upload becomes saturated
> (choked) it can choke downloading, because acknowledgements for received
> packets have to wait in line in the choked upload stream.

but if i clean all the NAT connections in the router or even if i
restart the router the network connection in the computer continues
blocked, the only way i found for solving it is restarting the computer



>