Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
DBADave
Constraint Violating Yak Guru
366 Posts |
 Posted - 2005-07-20 : 14:58:12
|
| Our data center was recently moved. The development servers were moved to a virtualized environment using Ghost to copy the server from the old location to the new location. Ever since the migration our virtualized development and test servers have been generating the error "Cannot generate SSPI context" when we try to connect using NT Authentication. When I switch the client to Named Pipes instead of TCP\IP, as specified by a Microsoft workaround, the NT authentication works without problem. Only the default instances are failing. The named instances on these virtualized servers work as expected.Could this problem be related to VMWare or Ghost? The consulting company who performed the migration said they verified the SPN does exist. Any suggestions.Thanks, Dave |
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2005-07-21 : 12:12:20
|
| Have you looked over this (http://support.microsoft.com/?id=811889) KB article? From what I gather by your error the problem is with your DNS or Active Directory. Maybe it's different due to the move?DanielSQL Server DBAwww.dallasteam.com |
 |
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2005-07-21 : 12:19:08
|
| Yes. I've seen it. Our consultant was to check the SPN, but I'm not sure if he did. When I try to run SETSPN -L servername I receive ldap_search_s failed: No Such Object. Not sure what I am doing wrong.I just changed the port from 1433 to a different port and it worked. There must be some type of contention with that port. The strange thing is the non-virtualized (stand-alone) servers use 1433 and experience no problems.Thanks, Dave |
|
|
|
SQLServerDBA_Dan
Aged Yak Warrior
752 Posts |
Posted - 2005-07-21 : 12:45:01
|
quote:
Originally posted by DBADave
Yes. I've seen it. Our consultant was to check the SPN, but I'm not sure if he did. When I try to run SETSPN -L servername I receive ldap_search_s failed: No Such Object. Not sure what I am doing wrong.I just changed the port from 1433 to a different port and it worked. There must be some type of contention with that port. The strange thing is the non-virtualized (stand-alone) servers use 1433 and experience no problems.Thanks, Dave
When I can, I always change the port to something other than the default 1433. It doesn't really matter if you're behind a firewall but I still like to do it.  DanielSQL Server DBAwww.dallasteam.com |
|
|
|
frankr
Starting Member
1 Post |
Posted - 2005-07-21 : 15:13:59
|
| Are you using ESX or GSX for vmware? I have had this problem twice but on standalone boxes not in the VMware world yet. I did the same thing you did to fix. We did have a problem with MSDE about the vmtools back reving a shared dll and MSDE would not start. Thanks Frank |
|
|
|
DBADave
Constraint Violating Yak Guru
366 Posts |
Posted - 2005-07-21 : 15:32:33
|
| I'm fairly certain they setup ESX. |
|
|
|
|
|
|
Cannot Generate SSPI Context - VMWare