Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a basic peer network (WORKGROUP) with PCs connected to sql server 2008 on a Windows 7 machine. I took one XP pc and the server home and connected to the server with no problems. When I plugged them back in at the office, I got the following error with my sql server tcpip odbc connection (sql server login not windows auth):

---------------------------
Microsoft SQL Server Login
---------------------------
Connection failed:
SQLState: '01000'
SQL Server Error: 67
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

The next day I took a different client machine running windows 7 and the server home again. The client could login fine but when I plugged them back in at the office I got the same issue. I can ping the server no problems and share files. Same problem with Firewall turned off on all machines. TPC enabled on server port 1433. The two client machines cant log in using SQL server management studio either when they were working fine before.

All other pcs which remained in the office can still connect no problem.

share|improve this question
    
Log in via SSMS on the SQL server machine itself, and check the accounts and permissions. –  adaptr Jan 11 '12 at 9:31
    
In ssms logins are unchanged. All clients are connecting using the same sqlserver login and pwd –  Paul Jan 11 '12 at 10:05
    
faulty client can see the server instance using osql -l –  Paul Jan 11 '12 at 10:25
    
error - both clients (the xp and the windows 7 one) are 32bit but the server is 64bit –  Paul Jan 11 '12 at 11:12
    
using ms network monitor from client gets 'Icmp: Destination Unreachable Message, Port Unreachable, 81.200.**.**:1434' –  Paul Jan 11 '12 at 11:34

1 Answer 1

-Allocated the client a static IP in its TCPIPv4 settings identical to its DHCP asigned IP -reserved that address in the netgear router lan ip table -ipconfig /release -ipconfig /renew -rebooted pc and router Now connects via servername -Took both home again and back without issue

share|improve this answer
    
Great to see that you found a solution to your problem. Please come back and put this answer as your accepted one, so that it won't stay open (and get repeatably bumped up). –  pauska Jan 14 '12 at 2:23

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.