Re: RRAS and FQDN ('connection-specific dns suffix' is blank)



"Ace Fekay [Microsoft Certified Trainer]" <aceman@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:e7N3u666JHA.5828@xxxxxxxxxxxxxxxxxxxxxxx
"Jim in Arizona" <tiltowait@xxxxxxxxxxx> wrote in message news:e%23FSOt46JHA.1764@xxxxxxxxxxxxxxxxxxxxxxx
Well, if I change some settings with the connection itself, I can add the domain within the DNS tab of TCP/IP properties so that names are resolved properly but this doesn't solve the issue with the server not being able to hand out the domain suffix to the vpn client when the clien logs in. Normally, this would be done via DHCP but I'm using a static set of IP addresses for vpn clients. I can't seem to find a location in RRAS to add a specific suffix that can be handed out to clients so that clients don't have to go deep into their connections settings and add it themselves. What a pain!



As you said, normally with DHCP Option 015, you can specify the suffix. Otherwise, if using static entries, the other config options should be mirrored from what server's own config, such as if the server has a Primary DNS Suffix, DNS addresses, etc, they should be provided automatically to the static RRAS clients.

So how is the server setup?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
aceman@xxxxxxxxxxxxxxxxxxxxxxx

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay



Jim,

I would have thought that what you see is the expected behavior. The client does not get its network config directly from DHCP even if you use the DHCP option. I would expect to set the DNS suffix manually in the client. If you have a lot of them you can use CMAK.

A remote client gets its network config from the RRAS server (it is part of the PPP negotiation to set up the connection). It has to, because the network config is only valid for the duration of the connection, not for the DHCP lease period. The only difference between a static pool and DHCP is that the server leases a batch of IPs from DHCP to use as its address pool.

Having said that, the client can send a DHCP discover after it has connected to get extra info from the DHCP server. I'm not sure exactly what parameters it can pick up that way.


.

Relevant Pages

  • Re: DHCP IP lease renewal ok, but a new PC can not obtain an IP ("An e
    ... I guess the problem seen with DHCP from PC's is a symptom of another ... Note that both robert and tina are blade servers within the save blade ... Connection-specific DNS Suffix. ... I.e. DNS servers has their own IP as the first DNS server and another as ...
    (microsoft.public.windows.server.networking)
  • RE: RPC Service unavailable
    ... Below are settings with fixed and DHCP settings on one op the clients: ... DNS Suffix search list: maddogs.local ... also when setting things on DHCP I can still access the client woth RDP ... is that the dhcp server is assigning some options incorrectly, ...
    (microsoft.public.windows.server.dns)
  • Re: Application Hang
    ... If the workstation ip is expired, the lease time is exceeded, delete the ip on the DHCP server "address leases" and run ipconfig /renew on the workstation. ... The forwarders ip is only used form the DNS server, all domain members will ask the domain DNS server for the www.whatever.com address, if the server doesn't know it, it will automatically forward ther request to the ip addresses under the forwarders tab. ... When I do a "ipconfig /all" on the client, ...
    (microsoft.public.windows.server.networking)
  • Re: Internet Speed
    ... I think what we are trying to say is to use the DHCP from the SBS and NOT ... DNS and WINS point to the SBS. ... as the server IP address. ... it is recommend to configure all SBS client computers' IP and DNS ...
    (microsoft.public.windows.server.sbs)
  • RE: Understanding ISA Server System Policy
    ... for dhcp and dns the system policies do able isa to be dhcp and dns CLIENT ... I know it is best having ISA on another server but that is what the primary ... Client for Microsoft Windows, QoS, File and Printer sharing, TCP/IP. ...
    (microsoft.public.isa.configuration)