Why remotely connecting to SQL 2005 express failed?

Question

Why remotely connecting to SQL 2005 express failed?

Viewing 15 posts - 16 through 30 (of 35 total)

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

halifaxdal SSCoach Points: 19741 More actions · Answer 1

SKYBVI (2/7/2012)
halifaxdal (2/7/2012)
SKYBVI (2/7/2012)
halifaxdal (2/7/2012)
I did some configuration on Windows Firewall, not sure if I did it correctly, it is still not working, please see the attachments for the screenshots.
Thanks.
Can you do this from cmd :-
telnet server name 1433
Regards,
Skybvi
I think you got the point: 1433 is blocked.
To Bru: In my environment, I cannot arbitrarily turn the firewall on or off, I sent the request to our admin and am waiting for further answer. Thanks for your suggest, I believe the firewall is preventing the port being used.
However, the problem is: I already added 1433 in the exception list in Firewall, why it is still being blocked?
maybe, u r not using 1433 as sql server port, u might be using some other port for sql server.
Regards,
Skybvi

Although that sounds to be possible but I don't think the initial installation changed the default setting, I can double check though.

Lowell SSC Guru Points: 323518 More actions · Answer 2

since this is a named instance and not the default instance, I'm sure it is using dynamic ports, which will NOT be 1433.

to make it easier, i'd recommend changing it to a static port, here's an example screenshot (lot of them this thread, right?)

erase the dynamic port value and enter a value that is NOT 1433/1434 into the TCP Port value circled below;

stop and start the instance and go back to the firewall again to allow that port for that application.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

halifaxdal SSCoach Points: 19741 More actions · Answer 3

You are right, I opened Configuration Manager, and checked protocol for TCP/IP there, it says it is configured as using dynamic port and the port option is empty, so I put 1433 in both entries in that TCP/IP setting.

I stopped and tried to restart the SQLExpress service, it now says the service is started but stopped automatically. I'll check the event to see what happened

Lowell SSC Guru Points: 323518 More actions · Answer 4

halifaxdal (2/7/2012)
You are right, I opened Configuration Manager, and checked protocol for TCP/IP there, it says it is configured as using dynamic port and the port option is empty, so I put 1433 in both entries in that TCP/IP setting.
I stopped and tried to restart the SQLExpress service, it now says the service is started but stopped automatically. I'll check the event to see what happened

I think it stopped because there are now TWO services fighting for port 1433....the default instance and the named one you are trying to connect to, I'm betting.

that's why i said change it to a port that is NOT 1433...so you wouldn't conflict with the default instance.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

Bru Medishetty SSC-Insane Points: 23606 More actions · Answer 5

Yes, I too would assume there is an issue due to port number. Try changing it to a newer value and restart the SQLExpress instance.

Bru Medishetty

Blog -- LearnSQLWithBru

Join on Facebook Page Facebook.comLearnSQLWithBru

Twitter -- BruMedishetty

halifaxdal SSCoach Points: 19741 More actions · Answer 6

The event says I can't put 1433 on both entries, so I made the changes and now it is exactly the same as another server that I have no issue remoting to it via VPN.

But issue still persist on this express server, same error.

TCP/IP setting is shown in the attachment.

Thanks.

halifaxdal SSCoach Points: 19741 More actions · Answer 7

when I telnet the server with port 1433, it gives me a blank screen other than a blinking cursor, is that normal?

SkyBVI SSCoach Points: 15128 More actions · Answer 8

halifaxdal (2/7/2012)
when I telnet the server with port 1433, it gives me a blank screen other than a blinking cursor, is that normal?

Yes, its normal.

Regards,

Skybvi

Regards
Sushant Kumar
MCTS,MCP

halifaxdal SSCoach Points: 19741 More actions · Answer 9

halifaxdal

SSCoach

Points: 19741

February 7, 2012 at 1:52 pm

#1444117

Issue persists, no more clue?:crying:

SkyBVI SSCoach Points: 15128 More actions · Answer 10

halifaxdal (2/7/2012)
Issue persists, no more clue?:crying:

Did you follow closely what lowell told about changing Port number?

Regards,

Skybvi

Regards
Sushant Kumar
MCTS,MCP

halifaxdal SSCoach Points: 19741 More actions · Answer 11

SKYBVI (2/7/2012)
halifaxdal (2/7/2012)
Issue persists, no more clue?:crying:
Did you follow closely what lowell told about changing Port number?
Regards,
Skybvi

I think I did, as you can see from the attached screenshot.

Lowell SSC Guru Points: 323518 More actions · Answer 12

the screenshot you posted showed port 1433, which is wrong. it cannot be 1433,

choose another port.

i personally like 14330., but that's me.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

halifaxdal SSCoach Points: 19741 More actions · Answer 13

Lowell (2/7/2012)
the screenshot you posted showed port 1433, which is wrong. it cannot be 1433,
choose another port.
i personally like 14330., but that's me.

I am sorry I am confused here, isn't SQL using 1433 by default as the TCP/IP port?

Lowell SSC Guru Points: 323518 More actions · Answer 14

you skipped over the reason i stated previously. slow down and read a little deeper.

there are TWO instances of SQL on the server.

the default instance, which is already using 1433, and the express instance named TISMJPVV62\SQLEXPRESS.

you can see them by going to Administrative tools...Services.

each service must listen to a different port, as that is the only way to tell one instance from another.

...

Lowell (2/7/2012)
I think it stopped because there are now TWO services fighting for port 1433....the default instance and the named one you are trying to connect to, I'm betting.
that's why i said change it to a port that is NOT 1433...so you wouldn't conflict with the default instance.

Lowell

--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

halifaxdal SSCoach Points: 19741 More actions · Answer 15

Thanks.

I don't see two SQL instances on that server, where did you see it?

I changed the port number to 14330, it still gives me the same error.