PPTP VPN Static IP Address Problem

[Bob]

I can connect to a PPTP VPN Server with a VPN Client that asks for its
IP address to be assigned automatically.

However when I set up the VPN Client with a static IP, I get Error
735, which says "the requested address was rejected by the server".

I have the VPN Server set up to provide an IP address in a specified
range, which matches with the IP address I request in the VPN Client.

I am assuming that the VPN Server is assigning the VPN Client's IP
address and the router is not being involved. Is that correct? If the
router is involved, how is it involved in terms of DHCP?

I restricted the range of DHCP addresses in the router so I could make
the VPN Server have a static LAN IP in order to forward port 1723 and
GRE. I did not want any possibility that some other machine would
accidentally grab that IP when the VPN Server was turned off.
Therefore the IP I am requesting with the VPN Client is not active in
the router.

However, when I request a static IP in the range where the rotuer DHCP
is enabled, I still get the same error. However that IP is outside the
range of approved addresses set up in the VPN Server. I will have to
wait for my associate to correct that.

In general what is the best way to deal with IP addressing on a PPTP
VPN? I am having trouble mapping the share and I am considering a
static IP with a HOSTS table entry as a possible solution.

Anyone know what is happening with Error 735? Thanks.


--

Map Of The Vast Right Wing Conspiracy:
http://www.freewebs.com/vrwc/

You know you are in Hell when you have to make a
distinction between what is moral and what is legal.

 

[Sharoon Shetty K [MSFT]]

You need to specify in the RRAS policy that the client can request for a
static IP.

MMC -> RRAS snap-in
Select node Remote Access Policies
Select the policy on the right pane.
Right click, select "Properties"
Edit Profile
Select IP tab
Select "Client may request an IP"

--

Thanks
Sharoon
(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Bob]

You need to specify in the RRAS policy that the client can request for a
static IP.

MMC -> RRAS snap-in
Select node Remote Access Policies
Select the policy on the right pane.
Right click, select "Properties"
Edit Profile
Select IP tab
Select "Client may request an IP"

Just to make sure I understand you, please indicate which computers
need this procedure"

1) Win2K VPN Server

2)Win2K Client

3)XP Home VPN Server

4)XP Home VPN Client

Assume any one of those VPN Clients can connect to any one of those
VPN Servers.




--

Map Of The Vast Right Wing Conspiracy:
http://www.freewebs.com/vrwc/

You know you are in Hell when you have to make a
distinction between what is moral and what is legal.

 

[Sharoon Shetty K [MSFT]]

The process is applicable to Win2k Server.

In case of XP VPN Server, incoming connections simulates some of the RRAS
features. You can do the following
Right click and select Properties on the incoming connection connectoid,
Select Networking Tab,
TCP/IP Properties
Check "Allow calling computer to specify its own IP Address"

--

Thanks
Sharoon
(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Bob]

The process is applicable to Win2k Server.

The irony of all this is that name resolution worked when I set up a
Win2K VPN Server on my machine and my associate set up an XP VPN
Client on his machine. Why did it work then?

In case of XP VPN Server, incoming connections simulates some of the RRAS
features. You can do the following
Right click and select Properties on the incoming connection connectoid,
Select Networking Tab,
TCP/IP Properties
Check "Allow calling computer to specify its own IP Address"

We will try that.


--

Map Of The Vast Right Wing Conspiracy:
http://www.freewebs.com/vrwc/

You know you are in Hell when you have to make a
distinction between what is moral and what is legal.

 

[Jeffrey Randow (MVP)]

You had access to a WINS or local DNS server...

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone

 

[Bob]

You had access to a WINS or local DNS server...

There is no WINS server nor is there any local DNS server.

This is a simple peer to peer PPTP VPN using XP Home.

Take a look to see if NetBIOS is implemented in the WINS panel.

--

Map Of The Vast Right Wing Conspiracy:
http://www.freewebs.com/vrwc/

You know you are in Hell when you have to make a
distinction between what is moral and what is legal.

 

[Bob]

You had access to a WINS or local DNS server...

I looked at an XP PPTP VPN Client and sure enough on the WINS panel
there it was - NetBIOS. That's why you can do name resolution.

It was deliberately left off the Win2K PPTP VPN Client. That's why you
cannot do name resolution.

Microsoft has had 4 Service Packs to fix this glaring deficiency on
Win2K, but has chosen not to. They want to force you to buy XP, if you
must have name resolution.

Fortunately I don't - I use raw IP addresses anyway. The VPN Server is
always the first address in the range of addresses you configure for
the VPN - and therefore it is static for the VPN - and if you
configure the VPN correctly you can set up a static IP address for the
VPN Client.

Now all you need to do is use those raw IP addresses to access the
shares on either machine, e.g. \\192.168.1.100, etc.

I find it a bit strange that no one on these forums knew all this.


--

Map Of The Vast Right Wing Conspiracy:
http://www.freewebs.com/vrwc/

You know you are in Hell when you have to make a
distinction between what is moral and what is legal.

 

[Jeffrey Randow (MVP)]

See my other post to you on this topic...

I looked at an XP PPTP VPN Client and sure enough on the WINS panel
there it was - NetBIOS. That's why you can do name resolution.

It was deliberately left off the Win2K PPTP VPN Client. That's why you
cannot do name resolution.

Microsoft has had 4 Service Packs to fix this glaring deficiency on
Win2K, but has chosen not to. They want to force you to buy XP, if you
must have name resolution.

Fortunately I don't - I use raw IP addresses anyway. The VPN Server is
always the first address in the range of addresses you configure for
the VPN - and therefore it is static for the VPN - and if you
configure the VPN correctly you can set up a static IP address for the
VPN Client.

Now all you need to do is use those raw IP addresses to access the
shares on either machine, e.g. \\192.168.1.100, etc.

I find it a bit strange that no one on these forums knew all this.