Windows Forum

Ask something
Discussion Locked

Routing and Remote Access Server

0 helpful
4 replies

by mprzytarski 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We recently upgraded one of our servers that we use to send EDI via a static address to our lockbox. We have installed the latest version of RRAS (1/99) onto the system. We have set up manual Dial-up, and configured the RRAS exactly the same. Thepassword, and logon ID's are the same, as are the TCP/IP information and logon script. If I use the manual Dialup, its ok and everything works, if I use the automatic dialup (the perl script we use basicaly sends the the information to the static route we set up and the system dials out to the lockbox). The system connects, and within 24 seconds drops carrier, my guess the the PPP or such is not quite right, but I cannot find anything in the logs to help. The system is NT4.0 SP5, and this setup worked before on the system like it. The last time we set this up I remember that we had to install the RRAS and not reinstall SP5 to get it to work. When we do that now though the demand dialer causes the blue screen of death.

Anyone else seen something like th

4 replies

by calves

I worked a lot with RRAS, and the only thing I can't think of is the dialup or user login info been wrong. But, you said that it works fine if dialed manually. There must be something in the perl script.
I don't know how usefull that could be to you, but for a situation somewaht similar, I've done was to setup a ISP local dialup, and then setup the RRAS through VPN, now I have a permanent connection to another server accross country for $20 month (keep in mind you can probably get a free ISP).
You should apply the service pack anytime the system files changes or any service is (re)installed.
Have you tried the persistent connection?
Could be that the 24 seconds is the time that takes to authenticate the user, and the server is denying access?
Did you create a backup on RRAS of the configuration to a diskette of file (you can do that under the file menu)when it was working so you can now re-load it.
I hope I have helped you any.
Good luck!

by mprzytarski

Thanks for the reply, in regards:

A) The PERL script only tells the system to send the specified file to the static IP address, which causes the system to automaticaly dial and send the file to the Lockbox. It basicaly has no other control function.

B) I have tried the persistent connection, no luck, and I have set the activity disconnect to 180 seconds with no luck.

C) I have a backup, and have installed it on a blank server and such, but that shows nothing different than what we have.

by mprzytarski

Thanks for the reply, in regards:

A) The PERL script only tells the system to send the specified file to the static IP address, which causes the system to automaticaly dial and send the file to the Lockbox. It basicaly has no other control function.

B) I have tried the persistent connection, no luck, and I have set the activity disconnect to 180 seconds with no luck.

C) I have a backup, and have installed it on a blank server and such, but that shows nothing different than what we have.

by mprzytarski

Well, I sloved the problem. Seems the server we replaced also was a DHCP server, and one of the reasons we replaced it was that we are now 100% static IP do the DHCP was disabled. Well, for some reason the RRAS was looking for a DHCP server on ourend. We turned the DHCP on, and everything works fine.

This discussion is closed to new replies.