We are in the process of upgrading a worldwide NT4 domain to Win2K. (A BDC in each office. WAN links between offices in different countries consists of relatively slow VPN connections in RRAS). We have upgraded the PDC (located in Sweden) to Win2k, and everything works fine. The problem is that the administrator in Germany recently installed a Win2k Pro laptop. In Germany they run their own local NT4 DNS server, but I suppose the Win2k client became aware of the Win2k server in Sweden when the laptop joined the domain. Now the laptop only logs on to the Win2k server in Sweden, resulting in long logon times and scripts not running. (Each office have their own scripts on their own BDC). What can I do to make the laptop logon to the local NT4BDC instead of the Win2k server in Sweden? (We cannot upgrade the servers in Germany for another two months, and more workstations with preinstalled Win2k Pro are on their way…)