🚀 go-pugleaf

 In article <819705156_OASIS_@ajrose.demon.co.uk>
  andrew@ajrose.demon.co.uk (Andrew Rose) said:-

> In article <4bf1j1$fss@lily.csv.warwick.ac.uk>
>  csulw@csv.warwick.ac.uk (Paul Donovan) said:-
>
>>In article <819400858_OASIS_@nanonano.demon.co.uk>,
>>        scotty@nanonano.demon.co.uk writes:
>>>Hi,
>>>
>>>I am having problems making a PPP connection with some PoPs, 
>>>especially my local one in Blandford (01258) 398666. When I log in it 
>>>justs returns to the the 'NET>' prompt and does nothing. Other PoPs 
>>>like Workington, Wolverhampston, and Wetherby work fine and retrieve 
>>>the news/mail.
>>>
>>>I am using Oasis 1.35E, with the standard DIAL.TXT and STARTUP.NOS files.
>>>
>>>Is this problem because of the PPP bug in KA9Q which is mentioned when 
>>>you finger status@gate.demon.co.uk.
>>>
>>>Is anyone else having the same problem on their local PoP and is there 
>>>a way round it? A guy at demon support suggested that I add a 2 second 
>>>delay after the HELLO message, but this did not fix the problem.
>>>
>>>Would it help if I configurated NOS to use slip instead of PPP?, if so 
>>>does anyone know how to do this?

>>Hi,
>>I'm having exactly the same problem with the Chelmsford PoP. I'm using 
>>Oasis 1.34 on a Falcon with a Frontier XL 28.  I get 'HELLO', but then 
>>it just gives up.  The guy on the support line suggested sending a few 
>>'\r's after HELLO, but it didn't work either.  I haven't made a 
>>successful connection yet......grrrrrrrrrrrrr.
>>
>>I'm posting from my old Uni account, which may expire at any day, so a 
>>quick reply would be gratefully received.
>>
>
>I find when logging into the London POP that this problem only occurs 
>when I'm attached to a Finch server. When I'm lucky enough to find a 
>ttyc server everything runs smoothly.
>
>Anyone know the difference? BTW I was going to say this happens every 
>time, but since last night I'll have to admit it's only the case 99 
>per cent of the time. The plot thickens slightly....

From what I've worked out from threads, the Ascend lines (ones with no 
ringing tone before answering) take a little too long to initialize so 
they miss the request from your end to complete the connection. The 
end result of this, is that after the motd, both ends sit there 
waiting for the other to start the conversation. Neither does, so one 
end will time out and drop the line. These appear to be the "finch" 
servers.

This can be verified after log-on by typing "ppp sl0". There will be a 
line "LCP -- waiting for remote host to open". Typing this line after 
a non ascend line log-on will show you what should be there if one of 
the solutions works.

Typing "ifconfig sl0 up" is just the solution I find to work 100% of 
the time. Others have reported "status up" to work and that modifying 
the startup file to add a delay followed by either "status up" or some 
carriage returns works also.

A subsequent "ppp sl0" will reveal if the cure has worked. The "LCP" 
line will have changed to some text indicating the connection has been 
made. There will also be the usual sequence of flickering modem SD/RD 
lights that normally occurs a few seconds after a non "finch" log-on 
which saves having to check once you get the feel for it.

There was mention of an upcoming version of NOS. Can this be confirmed 
by anybody "in the know" and will this problem be resolved along with 
the news posting bug?


__

Guy Harrison

guy@swampdog.demon.co.uk