Re: Probably no solution to this...
§ñühw¤£f
> §ńühw¤Łf wrote:
>> Mike Easter wrote:
>
>>> Have you checked with any of the help groups from the bebits wiki?
>
>> I posted the question to alt.os.beos also...
>
> I figgered that group must be pretty dead since the last post there
> was in
> July, but you got a reply there already.
>
>> I think the problem is either in the crappy modem/router or
> centurytel
>> dsl blocklists https requests.
>
> I know almost nothing about BeOS or DSL, except what I read in the
> wiki
> and a few other places.
>
It needs the net_server_patches.zip to play properly with any broadband
connection.
I'm using it now and it seems to have fixed the issue.
Should thank the guy who wrote it. Some nice work there!
> When I'm trying to troubleshoot connectivity to a server, I try to go
> around/ without intervening/ browsers or mailuser agents or
> newsreaders
> and use some tool that is more direct, such as IDServe or telnet or a
> telnet-like tool or even SamSpade or NetDemon, so that I can see what
> is
> happening rather than 'nothing' or some kind of dumb status line.
>
I think theres a BeOS app that will function the same way.
It winds up being basicly this though" MTU. The BeOS wants to use the
full 1500 MTU with no padding (as I understand it) but the ISP expects
an MTU of 1492 or *less* so when it encouters the default of 1500 packet
size it hangs.
Thanks to all who helped and my appologies to anywon wot got flaem'd as
I am a irrational hothead :)
--
Last night while sitting in my chair
I pinged a host that wasn't there
It wasn't there again today
The host resolved to NSA.