leased line problem

[deathripple]

hi there,

I'm having a problem setting a leased line. actually, I'm trying to connect a machine running windows 200 prof to a linux server running fedora core 2. the modems I'm using are Zyxel U90E and I've managed to set them up, one in originate mode and the other in answer mode.

here are the changes i've made on the linux box:
etc/inittab:
s1:2345:respawn:/usr/sbin/pppd /dev/ttyS1 38400

/etc/ppp/options:
lock
modem
nodetach

/etc/ppp/options.ttyS1: (modem pe com2)
crtscts
mru 576
mtu 576
passive
192.168.1.1:172.16.1.11
-chap
modem
#noauth
-pap
persist

/etc/ppp/ip-up.local
#!/bin/bash
case $2 in
/dev/ttyS1)
/sbin/route add -net 0.0.0.0 gw 172.16.1.11 netmask 0.0.0.0
;;
esac

for windows I've set up a direct connection.

the problem is when I try to initiate the conncgtion from windows, which stops at the Verifying username and password.... I've been told that this occurs because the windows sends the word CLIENT and expects back CLIENTSERVER. can anyone tell me how should I create a scripts that handles this using expect and send or something? that should be all, or is it something more?

thanks

 

[drag]

It's been a long times since I last messed around with modems and such. Sometimes I'll setup a ppp connection using a null modem cable, but that doesn't require any authentication and such...


Err...

Well modems are communication devices, obviously, and they talk to each other. You can use a terminal program like minicom in Linux or hyperterminal in Windows to do the talking manually... One sends some text like:
Hello and welcome to nextel phone network. Only authorized users.
pppd server blayh blahblahbah

then eventually it sends:
"Login:"

The client machine sees the string "ogin" and then sends the username.

Then the server sends:
"Password:"

The client machines sees the string "assword" and then sends the password.

then sometimes you have extra work, like allow a human to enter a number to get into a shell on the server, but usually after that they begin negotiating the connection modem to modem (connection speed, protocol, stuff like that).

Now in Linux this is taken care off by things called chat scripts.

Now, of course I once had to do this manually and figure out a custom chat script because the default ones from redhat linux stopped working. Why? Becuase the ISP techs setup the server to open up into a shell, instead of going directly to pppd when they were troubleshooting line problems and of course he forgot to switch it back.

Which was nice because I could now get shell access into their server, but it sucked because I had to add a option to the dial up script to echo 1 or whatever to initiate the ppp connection.

So what you need to do is setup a simple little chat script (read about chat at "man chat") and have that executed from your /etc/ppp/options.ttyS1

see here

Scroll down to section "2.4 Serving MS Windows clients"

I never setup a PPPD server before, but this should work.