Hi I have an issue with XP PRO laptop users that use their laptops to login locally on the LAN and also remotely via a VPN connection at night/weekends. After logging in remotely the next time they login locally on the LAN they experience extreme slowness with opening applications such as Word, printing and browsing print queues etc. The problem appears to be that the entry for their computername in the wins database is still pointing to the IP address they had while connected remotely - the delays/slowness are caused by timeouts while the smbd/spoolss process tries to connect to the wrong IP address (sample from smbd log below). I can get around this issue for some sites by setting disable spoolss = yes in smb.conf thus preventing the spoolss connection to the PC and the timeouts. The only other option I can think of is to not hand out a wins server address when the laptops connect via the VPN - presumably this would prevent the re-registration in wins with the VPN IP address. The downside to this is that all laptops would need an LMHOSTS file so that can resolve netbios names on the LAN when connected remotely. Any suggestions appreciated - running 2.2.7-security-rollup-fix on RedHat 7.2 - Samba is acting as the wins server (wins support = yes), name resolve order is lmhosts wins hosts bcast. Thanks Simon [2003/05/07 19:49:30, 2] lib/util_sock.c:open_socket_out(874) error connecting to 192.168.100.11:445 (No route to host) [2003/05/07 19:49:33, 2] lib/util_sock.c:open_socket_out(874) error connecting to 192.168.100.11:139 (No route to host) [2003/05/07 19:49:33, 1] libsmb/cliconnect.c:cli_connect(775) Error connecting to 192.168.100.11 (No route to host) [2003/05/07 19:49:33, 0] rpc_client/cli_spoolss_notify.c:spoolss_connect_to_client(91) connect_to_client: unable to connect to SMB server on machine SM. Error was : SUCCESS - 0.