Can''t connect to SQL Server - ''null user name''

Question

Can''t connect to SQL Server - ''null user name''

victor zayas-197939

SSC-Addicted

Points: 465
More actions
January 30, 2005 at 8:33 am

#164450

I have 2 Windows XP Pro desktops which connect to a database on a server running SQLServer using Windows Authentication. I have been trying to connect a laptop to the same database but get an error message saying that authentication failed because of a null user name. I log on to the laptop with the same user name and password that I use successfully on the desktop but I am unable to connect to the database. Furthermore, on the laptop, when I try to open a mapped network drive (F which resides on the server, I have to enter a user name (\\OFFICESERVER\username&nbsp and password before I get access to F:. On the 2 desktops, F: is accessible as soon as I boot-up.
I know that this sounds more like a Windows network issue than SQL Server issue but I am stumped. Thank you in advance.

Viewing 9 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Kathi Kellenberger SSChampion Points: 11811 More actions · Answer 1

Just a guess here, but is it possible that the desktops and the server are in the same domain or workgroup and that the laptop is not a member?

Aunt Kathi Data Platform MVP
Author of Expert T-SQL Window Functions
Simple-Talk Editor

victor zayas-197939 SSC-Addicted Points: 465 More actions · Answer 2

The workgroup for all of them seems to be the same (the very original WORKGROUP). Can a user name be different than what it says on the Windows log-in dialog box?

Kathi Kellenberger SSChampion Points: 11811 More actions · Answer 3

Have you tried connecting to SQL after mapping F?

Aunt Kathi Data Platform MVP
Author of Expert T-SQL Window Functions
Simple-Talk Editor

Peter Wright SSCommitted Points: 1966 More actions · Answer 4

This sounds more like a Windows Authentication issue than a SQL Server connectivity issue, possibly the laptop has extra security patches installed?

Map a drive to a share on the SQL Server box (as Kathy says) then you should be able to map using Windows Authentication. If it still doesn't work then use the SQL Client Network Utility on the laptop to force connections using names pipes.

victor zayas-197939 SSC-Addicted Points: 465 More actions · Answer 5

victor zayas-197939

SSC-Addicted

Points: 465

January 31, 2005 at 4:33 pm

#539834

I will try that, Kathy. Thanks.

victor zayas-197939 SSC-Addicted Points: 465 More actions · Answer 6

Even after I connect to the F: drive, I still can't connect to SQL Server. I assume you mean connecting to F by typing in my username and password?

victor zayas-197939 SSC-Addicted Points: 465 More actions · Answer 7

By forcing connections using named pipes, do you mean removing TCP/IP and leaving only named pipes as a protocol in SQL Server? thnx

victor zayas-197939 SSC-Addicted Points: 465 More actions · Answer 8

Thank you both for your help. I did 3 things which solved the problem. As you suggested, I connected to the network drive first, I removed TCP/IP as a protocol from SQL Server (only named pipes) and I installed SQL Server SP3. I am not sure if I needed SP3 but I clearly needed the 2 things you suggested. Thanks again.