This is normal behavior. If you don't want people to connect to that server you either have to remove the server from the published application or stop the IMA service on the server. All 'disable logons' does is prevent people from logging onto the server, it doesn't stop your clients from being directed to that server to access a published application. Chris -----Original Message----- From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Joe Shonk Sent: Tuesday, April 12, 2005 12:51 PM To: thin@xxxxxxxxxxxxx Subject: [THIN] Logon Disabled Hmm... Interesting issue... If we disable logons to a server (from the console or cmd line) it seems that some of the thin-clients try and connect to it and error out even tho there are other servers that serving up this published desktop. Even 10 minutes later the same problems persist until: The thin-client is rebooted or logins are re-enabled. Rebooting the thin-client is not an option. Any ideas? Joe