My domain operates on a Class B that has been subnetted down to a Class C. My NT RAS box is a member server and is configured to assign IP addresses to remote clients via DHCP. The DHCP server has the proper subnet mask configured into its scope options. However, when the remote clients connect, they get a valid IP, but not the subnet mask. Instead, the remote NT workstations are automatically assuming a Class B subnet mask rather than the assigned Class C. This is preventing them from browsing file servers on the domain, of course. I see where to specify an IP address for a dial-up client to use, at the client, but no way to beat this auto configuration of the subnet mask on the remotes. If I went to a static address pool at the RAS server, there is still no way that I see to tell it the proper subnet mask to use. If I add the option to the DHCP scope to force ICMP subnet mask discovery, I wonder if it will help but am hesitant to try. Is there a way around this?