Connection Failed

[link9]

Morning all --

So I came in and sat down at my computer this morning and started working with my stuff, and the first time I tried to connect to my SQL Server machine down the hall, it wouldn't let me.

Hmmmmm.... So I start rooting around, and I figure out that my machine is the only one that is having problems. All other computers in the office are fine. And, everything was working perfectly when I left yesterday. I'm using TCP/IP as my protocol (both server and client) and 1433 as my port... etc.. etc..

I log in to the server, and everything appears to be fine. SQL Server is running, DSNs work properly. Everything appears to be A-OK until I try to connect to the database from my machine.

Here are the errors it gives when I try to test the DSN from control panel:

Connection Failed:
SQL State: '01000'
SQL Server Error: 10061
Connection Open (connect()) <--- There's more on that line, but that's the punchline

Connection Failed:
SQL State: '08001'
SQL Server Error: 11
General Network Error (check documentation) <--- Same, there's more, but that's the gist

Anyone have any ideas? I'm sort of dumbfounded by this.

Thanks!
Paul Prewett

 

[link9]

Well, I started and stopped the service, and that cleared it up.

**sigh**

go figure.

 

[foxdev]

Paul, I'd have been interested to know what would have happened if you had reboot your machine (the troubled client) - or did you try that step before restarting the service? Robert Bradley
Support operation moo!
Visit the OpCow page

http://www.agrainofhope.org/opcow.shtml

to help in this cause

 

[link9]

Oh yes, I &quot;rebooted and repented&quot; about three times before I broke down and restarted the service.

To tell you the truth, I still don't have any idea why the server just decided it didn't like my computer. It gets a little stranger though, because not only would my DSN not connect, but I also could not open my client version of Enterprise Manager and connect -- neither with my Query Analyzer --

But here's the kicker -- I could connect to other external SQL Servers (I have two others registered at my ISP), and they worked perfectly.

Eh... I guess it's like I always say -- it's amazing what restarting something can do for you. Never ceases to amaze me what problems that will solve.

Oh well...

 

[ValJean]

Thanks.
This same thing is happening with my computer. My computer is the only one in this whole building that cannot connect to SQL Server in a client-server environment! I can't stop the service until 5 pm, though, after everyone goes home. We just had an IP conversion - all our static IP addresses, including the server's - were changed, and this is what triggered it OR it may not have anything to do with it.
Who knows??!?!
Thanks,
valjean_elander@stlouisco.com

 

[foxdev]

Are you guys using Standard or NT security?

I've had goofy, unexplainable problems that were similar to these. Paul, out of curiousity, could you connect to the server in any way other than for SQL Server (IOW, could you browse its directories through Windows Explorer, for example)?

When this has happened to me, we traced it down to the Domain Controller being out of whack - such as the PDC and BDC not being in sync. Robert Bradley

http://www.agrainofhope.org

http://www.lowcostprints.com

http://www.foxdev.com

 

[Guest_imported]

I had the same problem. Thanks for the help!