M
Marcel
Hi,
We recently upgraded from RAS on NT4 to Windows2003 and a weird problem
appeared. When users dial in to our RAS server (Primary Rate ISDN adapter),
their domain suffix and search list is blank (I can see this by using
nslookup, set all). This means that they now have to use the fqdn to
connect to any server, where previously they only had to use the server's
name.
Where do RAS clients get their domain name and domain search list settings
from? At first I assumed the client inherits it from the RAS server, but
the settings on the server's network adapter are correct (should it be
configured anywhere else on the server?) I tried assigning IP addresses
for RAS clients from a static pool and using DHCP and neither made any
difference. I've also tried specifying the domain suffixes in the local
group policy, but it also didn't work.
Thanks for any help
We recently upgraded from RAS on NT4 to Windows2003 and a weird problem
appeared. When users dial in to our RAS server (Primary Rate ISDN adapter),
their domain suffix and search list is blank (I can see this by using
nslookup, set all). This means that they now have to use the fqdn to
connect to any server, where previously they only had to use the server's
name.
Where do RAS clients get their domain name and domain search list settings
from? At first I assumed the client inherits it from the RAS server, but
the settings on the server's network adapter are correct (should it be
configured anywhere else on the server?) I tried assigning IP addresses
for RAS clients from a static pool and using DHCP and neither made any
difference. I've also tried specifying the domain suffixes in the local
group policy, but it also didn't work.
Thanks for any help