Hi folks, Thanks in advance for any assistance. For reasons beyond my control we have a laptop running Windows 7 that lives in our companies domain. Every couple of weeks this laptop has to be taken to a client site to connect to their SQL Server, more specifically it need to connect to the MSSQLSEVER file streaming share so our software can work. The clients site does not have a domain, the server there (2008 R2 standard) exists in a workgroup. When trying to access the file share created via SQL Server if we connect via \\IPAddress we connect without any issues, however if we connect using \\servername we encounter a security prompt with the following error "The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you.". Unfortunately, again for reasons beyong our control we have to connect via server name rather than IP address. To a certain extent, the above error message does make sense as we can't communicate with our domain at the time and we're logged on to the domain account using cached credentials. What I don't understand is why this should only be a problem when connecting via \\servername and is ok when using \\IPaddress. To add further confusion this only seems to be a problem in Windows 7 (hence posting in this forum). As a laptop running Windows XP connects with no issues at all using both \\ipaddress and \\servername. If I take the Windows 7 laptop out of our domain it connects with no problem at all but this isn't a viable solution so I suspect Windows 7 specific GPO or somwthing of that nature being picked up from out domain. I've tried editing the hosts file to associate the IPaddress with the servername but it made no difference. Thanks for any help you can provide, this ones got me stumped for now. H

Hi Folks, I've found the solution to this so thought I'd post it here to help others. Running the following command on the Win 7 box fixed the issue. net use \\Servername /user:domain\username Regards H