Help with MSSQL

[liquid One]

I am in the process of setting up my own webserver at my storefront but am
having some troubles connecting from outside. I have a machine with server
2003 standard R2 installed and CF7 and SQL server 2000. I connect to the
server using the console remote desktop, which works fine. And sql server seems
to be running fine. I used windows authentication on my installation, but have
also tried a named instance with mixed.

I just want to connect to the sql server using query analyzer from my
workstation(win xp pro).
Its on the network perfect and I can access its c$ folder no problem, so I
dont htink its a connection issue. Its probably something incredibly stupid
that im doing, but ive spent several hours troubleshooting, so i may as well
ask you guys.....


The name of the webserver is "WEBSERVER-DOMES" and there is a default
instance, and an instance named "TRADE". The default instance is the only one
im really concerned about connecting to. In the connect dialog box I have tried
the following combinations to connect:
\\WEBSERVER-DOMES
\\WEBSERVER-DOMES\
WEBSERVER-DOMES
\\WEBSERVER-DOMES/DEFAULT(\)with and without end slash
\\WEBSERVER-DOMES/TRADE(\)
\\IP-address\default
\\IP-ADDRESS

All of these combinations come with the exact same error as follows:

Unable to connect to server -whatever i typed-:

Server: Msg 17, level 16, State 1
[Microsoft][ODBC Sql Server Driver][DBNETLIB] Sql Server does not exist or
access denied

What am I doing wrong?

Thanks

[JMGibson3]

Have you tried the Browse (three periods) Button. It takes awhile but it
should traverse your network and present in the drop-down a list of every
"listening" SQL Server on the Network. If you don't see it then it's not
"listening". If you do see it, then clicking on it will at least ensure you're
going to the correct instance. If you see any others they should work if you
have a Logon. You could use them to test/ensure QA itself is working. If you
don't have any others and don't see it, then something is wrong with the
"listening" process, that is typically set to port 1433. Make sure your SQL
Server instance has been set to 1433 and that you don't have a firewall getting
in the way of that port on your own machine. Or perhaps a firewall on the
server/organization side is prohibiting "external" 1433's. Do you have any
inside-inside machines you could try with?

[liquid One]

First of all thanks for replying.
When I click on the browse ... button, all I get in there is local host.
I am using a machine that is local to this network, its sitting within 3 feet
of it actually.
I have no firewall at all on my workstation.
My workstation and 1 of the webserver's gigabit cards are connected to the
same 24 port switch. The webserver then has a different gigbit card going into
a firewall for external access via our website.
I can connect to the webserver by opening a explorer and typing
\\webserver-domes\c$ into it, and that works perfect, which leads me to believe
that its not the network.
In the tcp properties for the server network utility, it says 1433, and the
hide checkbox is NOT checked.
Any other ideas?

[liquid One]

Also, there is no firewall(software) on the web server. It only has the external firewall, which my computer does not have to pass through.

[liquid One]

Well I fixed the problem, while im not sure if it was the right way or not....

I registered the sql database on my workstations enterprise manager.

Then I was able to connect with query analyzer right away just by typing in
WEBSERVER-DOMES.

I was under the immpression that this is not the normal way to do what i am
doing, so if any of you can confirm that this is not normal, i would appreciate
it. Also, if you have a more proper solution, send it this way as well.

[The ScareCrow]

The sql server instance has to be "registered" to be able to connect to it.
(this adds the instance to the browse list)

This can be done via enterprise manager, then by expanding to the db and using
the "tools" menu you can directly open analyzer.
Expand "Microsoft SQL Servers"
Right Click "SQL Server Group"
Select "New SQL Server registration"

Another way is to use the client network utility which should have been
installed along with em and qa.
Click "Start"
Mouse Over "Programs"
Mouse Over "Microsoft SQL Server"
Click "Client Network Utility"



Ken