Connections Require Port and listener is not working

Question

Connections Require Port and listener is not working

Dan Cioffi

SSC Veteran

Points: 202
More actions
September 27, 2006 at 10:08 am

#60869

I have a situation that will require some replication in the next phase
of this project. The first part is to resolve a connection issue we've
had for a while.
We have a dedicated hosted Webserver that serves websites, running
Windows Server 2003 Standard. 2 of these sites use SQL Server 2000,
SP3.
The first issue is that there is a default instance named WDC061. The
instance that is used is WDC061\FTDBDATABASE.
Here's the connection issues I have...
After we reboot the server, no one can connect to the server from an
application or Enterprise Manager. This does not happen using query
analyzer though, but QA will only see the default instance unless we do
this...
If we reboot the server, users can only connect to SQL Server using
OLEDB or ADO or Enterprise Manager unless we bring up SQL Server
Network Configuration, and save the TCP/IP Properties on top of the
existing values. Even though Port 1433 is listed for the port, it's as
if the server doesn't exist to any remote clients.
The listener doesn't seem to be working. If I open Enterprise Manager,
my Registration to the server doesn't show connected, and when I right
click the server to connect, I receive a popup message that says "The
SQL Server <ServerName> doesn't seem to be running, are you sure you
want to connect?"
The last issue is that users have to connect to the database using the
IP Address of the server and the port, ie 192.168.1.1,1433. This is
even though I have mssql.domainname.com configured in DNS and port 1433
open on the firewall.
Anyone have any ideas to keep me from having to stop, save & start SQL
Server, get the listener working and allow users to use the domain name
rather than the IP address with the port specified?
Thanks

Viewing 3 posts - 1 through 2 (of 2 total)

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

Rudyx - the Doctor SSC-Forever Points: 43695 More actions · Answer 1

I would think that it is DNS on your last issue. Since your users are web users my guess is that your DNS server is not in thier configuration.

As for connecting with QA and not being able to connect with EM, well a few questions.

Is your authentication Windows or Mixed ?
When you connect with QA what credentials are you supplying ?
When you connect with EM what credentials are you supplying in the connection properties ?

Now a good reference for your application connection string(s):

http://www.connectionstrings.com/

Also have you checkde the SQL Server errorlog for message on what port(s) and protocols that it is listening on ?

RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."

Dan Cioffi SSC Veteran Points: 202 More actions · Answer 2

I was able to connect to the database, I was just connecting to the incorrect instance, the default instance which didn't contain the production databases. I finally said "enough", 2 instances isn't necessary, I moved all the production databases to the default instance, dropped the 2nd instance and everything is working fine now.

Now I just need to figure out why replication doesn't want to work.