Glad you figured it out.

>Please accept my apologies for the delay in responding. I feel like a thread necromancer, resurrecting old topics.
>
>I thought it worth noting that firstly, using the IP address resolved the issue within ODBC.
>
>Secondly, the cause of this issue (and others that some of our VB team were encountering) was the network's domain controller.
>
>In August our Exchange 2003 server, also our primary (and only) domain controller (also 2003), finally gave up the ghost.
>
>We migrated to Windows Server 2008 and Exchange 2010. Since then I have not seen one "Cannot Generate SSPI Context message" when using the server name instead of IP.
>
>Thanks for your help Sergey and apologies again for not replying sooner.