can ping, can't connect

Ok, I have a sever box running Debian stable with a 2.6 kernel (686).

It was working fine.
Suddenly after about a month up time it stopped, I think it was an IP
ipdate form the cable modem but whatever happened I rebooted and when it
came back up it cuold no longer make connections.

It is now sitting behind my emergency windows box ICS.
It can ping www.google.com with no problem but links www.google.com sits
there with "Making connection".

I did have it running a firewall that caused no probs for outbound
connections like that but i have turned that off.

It wont let me ssh in from either side.
It happily DCHPs from the modem or the windlw box, although it wont
route through the modem for some reason, but that is for later.

Does anyone have any idea what is going on and what I can do to fix it?

Thanks,
Rage

Rage wrote:

> Ok, I have a sever box running Debian stable with a 2.6 kernel (686).
>
> It was working fine.
> Suddenly after about a month up time it stopped, I think it was an IP
> ipdate form the cable modem but whatever happened I rebooted and when it
> came back up it cuold no longer make connections.
>
> It is now sitting behind my emergency windows box ICS.
> It can ping www.google.com with no problem but links www.google.com sits
> there with "Making connection".
>
> I did have it running a firewall that caused no probs for outbound
> connections like that but i have turned that off.
>
> It wont let me ssh in from either side.
> It happily DCHPs from the modem or the windlw box, although it wont
> route through the modem for some reason, but that is for later.
>
> Does anyone have any idea what is going on and what I can do to fix it?
>
> Thanks,
> Rage
If it can ping www.google.com by name, it isn't a DNS issue. Is it perhaps
that it can get a reply from ping but not from http? Have you looked at
your modem settings? I have usually found this to be a setting in my ADSL
modem/router. The best solution has been to reset it to the defaults and
start again. Working from Windows doesn't exclude the modem.

HTH,

Doug.
--
Registered Linux User No. 277548. My true email address has hotkey for
myaccess.
If the data doesn't fit the hypotheis, discard the data.
- Murphy's Law.

I have no idea WTF was wrong with it.
I was like the TCP stack had walked off, No _connections_ would work.
I reinstalled up about where I was untill I discovered that installing
bind9 killed dhcp from the modem... er WTF?
My firewall script is a copy of the one from the old install so it's not
that which killed the dhcp...
Anyhow I am now running very happily with dnsmasq serving all my
dhcp/dns needs. It is MUCH easier to configure as well.

Thanks for the help.

Rage

Doug Laidlaw wrote:
> Rage wrote:
>
>
>>Ok, I have a sever box running Debian stable with a 2.6 kernel (686).
>>
>>It was working fine.
>>Suddenly after about a month up time it stopped, I think it was an IP
>>ipdate form the cable modem but whatever happened I rebooted and when it
>>came back up it cuold no longer make connections.
>>
>>It is now sitting behind my emergency windows box ICS.
>>It can ping www.google.com with no problem but links www.google.com sits
>>there with "Making connection".
>>
>>I did have it running a firewall that caused no probs for outbound
>>connections like that but i have turned that off.
>>
>>It wont let me ssh in from either side.
>>It happily DCHPs from the modem or the windlw box, although it wont
>>route through the modem for some reason, but that is for later.
>>
>>Does anyone have any idea what is going on and what I can do to fix it?
>>
>>Thanks,
>>Rage
>
> If it can ping www.google.com by name, it isn't a DNS issue. Is it perhaps
> that it can get a reply from ping but not from http? Have you looked at
> your modem settings? I have usually found this to be a setting in my ADSL
> modem/router. The best solution has been to reset it to the defaults and
> start again. Working from Windows doesn't exclude the modem.
>
> HTH,
>
> Doug.


--
FREE FPS DEATHMATCH:
http://www.nexuiz.com
PLAY IT FREE!