lmmn

Sorry for the delay in replying, got a bit distracted. If memory serves me, RRAS has it's own DHCP server to cater for remote access clients so I suggest that you disable this for a start and configure RRAS to use your main DHCP server to provide addresses for remote clients. You can quickly check whether RRAS is providing addresses by seeing what addresses your main DHCP server has handed out - if it hasn't handed out the address actually being used by one of your 9x clients then you know you've got another DHCP server on the LAN. You could also use the network monitor (with a suitable filter) to have a shufty at the DHCP traffic on the LAN when you lease an address. Mike

If I've understood you correctly, you're pinging your ISA server by name and the address being reported is the WAN address. Does this occur only when you establish a tunnel or immediatley after booting your 9x clients? I would suggest you get hold of a copy of cyberkit - www.cyberkit.net -, install it on one of your 9x clients and have a nose around with nslookup to see what's happening in name resolution. Using tracert (also in cyberkit) to see what path you're using to your ISA server might help as well. At a wild guess, I suspect you're not looking at your local DNS for initial name resolution. Mike

These fields represent additional information that can be given to DHCP clients. DNS is usually a good one to set up as otherwsie you have to set the DNS address on all your clients which is a bit silly if you're dynamically allocating IP addresses. However, if your clients are all fine and you're not having any problems then the first corollary of Murphy's Law applies - if it aint broke, don't fix it. Mike