Dial-in server blues....

Dial-in server blues....

Post by Kees Spranger » Sun, 31 Dec 1899 09:00:00



Hi all,

I'm trying to set up a dialin server for ISDN, but I only get it working
for WIN95 clients.
With a analog modem things are working allright for every client.....

When a WIN95 client logs in I can see the login name and password coming
in in the metty.ttyI0 log file, but with other clients username and
password doesn't seem to be transmitted, and the server tries to startup

With the same dialer (client)  I can dial to other ISP's succesfull
though...

nb. I use CHAP as authentication protocol, and HDLC for ISDN.
Anybody any idea what I'm doing wrong here? Are there some good howto's
or FAQ's? I can only find info about ISP hookup's through ISDN.
Please let me know if you need more information...

Kees
--


OMEGAM Environmental Research
PO box  94685
1096 AR  Amsterdam
The Netherlands
Tel: ++31 20 5976666
Fax: ++31 20 5976777
http://www.omegam.nl

 
 
 

Dial-in server blues....

Post by Raymonds Doetje » Sun, 31 Dec 1899 09:00:00


Hoi kees, met welke andere systemen probeer jij het dan?!

Want je moet wel duidelijk opletten dat deze systemen LCP en PAP aware
zijn. (Chap is nog steeds behoorlijk schaars in de wereld van PPP).
Bovendien is HDLC alleen vaak tricky, want sommige ISDN ta's proberen
alleen X.75, V120 of V110, maar goed dat is een kleinigheidje de meeste
nieuwe adapters doen ook frame-relay (HDLC).
Waarom er eigenlijk in gods naam nog een protocol over het ISDN protocol is
getrokken is mij nog steeds een raadsel.  Met name is het belangrijk dat de
DUN clients van de andere systemen LCP en PAP ondersteuning moeten kennen
in jou geval zelfs chap. Anders ontkom je er niet aan om een inlog script
te moeten maken dat de gebruiker inlogged en vervolens de pppd op start met
server:lokaal adres.

Raymond


> Hi all,

> I'm trying to set up a dialin server for ISDN, but I only get it working
> for WIN95 clients.
> With a analog modem things are working allright for every client.....

> When a WIN95 client logs in I can see the login name and password coming
> in in the metty.ttyI0 log file, but with other clients username and
> password doesn't seem to be transmitted, and the server tries to startup

> With the same dialer (client)  I can dial to other ISP's succesfull
> though...

> nb. I use CHAP as authentication protocol, and HDLC for ISDN.
> Anybody any idea what I'm doing wrong here? Are there some good howto's
> or FAQ's? I can only find info about ISP hookup's through ISDN.
> Please let me know if you need more information...

> Kees
> --


> OMEGAM Environmental Research
> PO box  94685
> 1096 AR  Amsterdam
> The Netherlands
> Tel: ++31 20 5976666
> Fax: ++31 20 5976777
> http://www.omegam.nl


 
 
 

1. Problems with dialing out when dial-ins are enabled

I'm having trouble getting dial-outs to work when dial-ins are
enabled.  I can dial out on /dev/cua1 when getty isn't running
on /dev/ttyS1, but when getty is running I get a message that
the port I'm trying to dial-out on (/dev/cua1) is in use.  I
read the FAQs and everything seems to be set up right.  What
am I doing wrong?  

[I'm running SLS 1.02 (0.99pl9).]
--
Eric Dittman                  Texas Instruments - Component Test Facility

Disclaimer:  Not even my opinions.  I found them by the side of the road.

2. Red Hat Installation HELP !!!

3. Remote unix (RS/6000) servers with dial-ins

4. PC/IX and multiscreen video RAM's - help needed

5. Dial-In Blues (help me!)

6. Debug woes with Solaris cc

7. PPP problems with multiport dial-in/dial-out server

8. Acer TravelMate 730 and middle mouse button

9. Dial-up / Dial-In Linux Server to Windows Network for Mobile Users

10. dial ins

11. PPP dial-ins refused, OSR-5 with net100

12. Setting up firewall for dial-ins: How?

13. supraexpress modems (28.8) problems w/dial-ins