SQL Server does not exist or access is denied

[johnhig]

Hi All,

I can not figure out what I am doing wrong. I installed SQL Server 2000 with SP4 on a Windows 2003 Server.

When I run the New SQL Server registration from the server I can connect to the other SQL server just fine.

When I run it from my workstation I get the error message "SQL Server Does not Exist or Access is Denied"

I also can not connect to via my ODBC driver for a Coldfusion Web Site.

So I know I setup something wrong and I can not figure what I did. I have the MSSQL Server Service and the SQL Agent running under an login that myself has rights to.

What am I missing? Thanks John

 

[onpnt]

Did you use a default intsance or named?




[sub]____________ signature below ______________
I am Tedward Keyboardhands!!!
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]

 

[johnhig]

I unchecked the default and named it.

 

[onpnt]

ok are you putting in <machinename>\<db server name> then?

or just <db server name>?

Because the first is the correct way


[sub]____________ signature below ______________
I am Tedward Keyboardhands!!!
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]

 

[johnhig]

My Server Name is EESFS2 and my DB name is EES.

So under the Server Registration it does not appear in the list, so I type

EESFS2\EES and then connect.

I have tried using the Windows login information and sa login information. Either way it tells me that access is denied.

 

[onpnt]

are remote connections enabled on the server?

Just to be sure. When you say "DB name" you mean database server name right?


[sub]____________ signature below ______________
I am Tedward Keyboardhands!!!
You are a amateur developer until you realize all your code sucks.
Jeff Atwood[/sub]

 

[johnhig]

Not sure about remote connections? Do you know where I need to check for that?

Yes. I believe so...EES is my SQL Instance name.

So my Windows 2003 server is EESFS2 and when I installed SQL Server I named the instance EES

 

[gmmastros]

Have a look here: faq962-5481



-George

"the screen with the little boxes in the window." - Moron

 

[johnhig]

George - thank you.

I was able to determine that SQL is using a different port than 1433. Why I don't know. I did not tell it to and I don't know what service is using that port currently.

I was then able to telnet to the server using that port.

Now how to do I fix this?

 

[gmmastros]

First, determine the port that it does use. Then, make an exception in the firewall for that port.




Click Start -> Programs -> Microsoft SQL Server -> Server Network Utility

Make sure TCP/IP is an enabled protocol.
Click TCP/IP and then Properties
The port SQL Server is using will be displayed.



Now... make an exception for that port.

Click Start -> Control Panel -> Windows Firewall
Click the exceptions tab
Click 'Add Port'
Give it a name and specify the port you found from the first part.

-George

"the screen with the little boxes in the window." - Moron

 

[johnhig]

Can more than 1 server use a port?

 

[gmmastros]

It's possible to have multiple instances of SQL Server installed on the same computer. It is NOT possible for multiple instances of SQL Server to use the same port.

If you have multiple instances of sql server, then each instance will have its own port. IF this is the case, when you run the 'SQL Server Network Utility', you will see a combo box on the general tab named, 'Instance(s) on this server'.

Thanks to onpnt for bringing up the instance issue. In your case, make sure it says... 'EESFS2\EES' in the combo box, and then look at the TCP/IP properties.



-George

"the screen with the little boxes in the window." - Moron

 

[zircon06]

First thing check you did apply service pack on server. YOu can check by running select @@version