DHCP Scope for RAS

  • Thread starter Thread starter Mike
  • Start date Start date
M

Mike

Our organization current;y has DHCP setup to distribute addresses to
192.168.1.0. RRAS also uses this scope to get addresses to remote clients.
Is there a way to setup a scope just for RRAS clients in DHCP?

For example:
LAN scope 192.168.1.50 - 192.168.1.74
Remote client scope: 192.168.1.75 - 192.168.1.99

Thanks,

Mike
 
The easiest way is to reserve that block in DHCP . Then set RRAS to use
that block as a static pool.
 
No, but they don't anyway! The settings that the client receives come
from the RRAS server. The server leases IPs from DHCP, and allocates them as
part of the PPP/PPTP negotiation. The IP is valid only for the duration of
the connection, not for the DHCP lease time. The client does not contact the
DHCP server directly.
 
So do you exclude the ip addressing from the scope or reserve it in dhcp? If
it's a reservation, is it against the mac address of the server?\
 
If you are worried about overlap, you can exclude the static pool from
your DHCP scope. I tend to use the top end of the range (like 220-240) for
the pool and have never had any problems.
 
If you use static pools then how do the machines get their IP
addressing?? What simple setting am I missing? If a machine gets a
static IP address from the pool, do you set the machines to get IP
addresses from the server and hardcode the dns server address in the
local machine vpn connection IP properties?
 
If you are using a static pool of IP addresses, the client will receive
an address from that pool as its IP address for the connection. If you set
the clients to obtain name server addresses automatically, they get the DNS
and WINS server addresses from the RRAS server (as part of the PPP/PPTP
negotiation process). If you prefer, you can set these addresses manually on
the client.
 
OK, that is what I have set and it isn't working. The internal nic has
IP settings against it for DNS but they are not getting passed to the
clients.
 
That's odd. Do you have DHCP relay turned on (see KB 232703)? You may need
to enable tracing and look through the logs to see what is going on.
Normally the name servers come across as part of the setup negotiation, but
can be overwritten by DHCPInform replies.
 
Back
Top