This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PPTP with Radius authenication static Client IP

Hi, I am having trouble working out the best way to setup a clients site. Then have remote users all over the country and they currently PPTP VPN into a W2K Server and run Terminal Services.

I am going to be putting in a ASL 5 Box. I need to use Radius as there are too many user to setup in the Astaro.
My Problem is that I need to setup up Static IP on the Client Side. i.e I don't want them to use PPTP pool etc.

The reason I need to do this is so I can map the Printers on the TERMINAL Server box back to the Local pc. For example \windowspc\hplaser.

If I use PPTP pool with Radius Authenication, the windowspc IP may change over time.

You can change the client side IP in the TCP/IP setting on the PPTP connection on the PC, but I get the error 735 "The requested addres was rejected by the server"

Does anyone know if there is a way I can do this, or is the only way to setup each user on the astaro and define their address? [:S]

This thread was automatically locked due to age.

0 Gert Hansen over 21 years ago

Hi there,

as far as i know you can store the IP which gets assigned to the user in the radius server or the user database.

I'll forward this to our PPTP expert.

regards
Gert
Cancel
Vote Up 0 Vote Down

Cancel
0 Tim F over 21 years ago in reply to Gert Hansen

Thanks, I am currently looking through the IAS and the Active Directory Settings. Any help would be much appreciated.

Under the Dailin Tab in Active Directory for a chosen user there is a Static IP Box, but it is greyed out.
Cancel
Vote Up 0 Vote Down

Cancel
0 Stephan_Scholz over 21 years ago in reply to Tim F

Hi Tim F,

you should be able to set the static IP address of a user in the default configuration of Active Directory. I am not aware of any special setting that you need in order to be able to use it.
You may have run into the problem that your domain controller is running in mixed mode (NT domain) though. See the following URLs for details.

http://www.microsoft.com/windows2000/en/server/help/default.asp?url=/windows2000/en/server/help/ras_dom_staticip.htm http://www.winnetmag.com/Article/ArticleID/20346/20346.html

Regards,
Stephan
Cancel
Vote Up 0 Vote Down

Cancel
0 Tim F over 21 years ago in reply to Stephan_Scholz

Great, that did the trick.
1) Upgraded the Domain to Native Mode.
2)Gave user IP in AD of 192.168.80.55
3)Created an Network in ASL 5 of 192.168.80.0/24 called PPTP2
4)Select the PPTP2 network in the PPTP IP Pool.

And it all works.

However I am not sure if Step 4 is the best way.
It does also work in Step 4 is you just use the default PPTP Pool in ASL 5.

Ideas thoughts?

Thanks for all your help.

Regards

Tim
Cancel
Vote Up 0 Vote Down

Cancel
0 Stephan_Scholz over 21 years ago in reply to Tim F

Hi Tim,

actually you don't need to change the PPTP network. The server's IP address will be the first address of the original PPTP pool, but the connection will work fine, even it the addresses of the PPP partners are from different subnets. It works in the same way as for any other point-to-point interface.

Regards,
Stephan
Cancel
Vote Up 0 Vote Down

Cancel