RichB

Ah, the wonders of the Scoobynet IT community...

Todays question is:

If a machine is running SQLserver 2000 what would cause a certain port to be unaccessible.
We are sure it 'used' to work and there are no rules in the Firewall stopping it.

Where should I look to find what is blocking this port.

Is it possible that something else is using the same port? We have recently installed some software called NowPlanner. Is there any easy way to find out if that software is using that port?

Any help gratefully received, I'm just a simply Mac user who knows nothing about windoze etc.
Rich.

Ga22ar

Is the port on the server actually active ???

Run netstat -n on the server to see if it is...

If it is you "could" run a port scan against the bix to see if the service/app that is using it responds in some way.. That might give you a clue

RichB

Ah, should have mentioned that we have run a port scan and the particular port does not 'respond'

Any thoughts?

David_Wallis

Hi,

Most firewalls need to be configured to permit traffic in both directions... be sure that you are open in both directions.

What port is it that is conflicting??

David

RichB

the firewall is not interferring.
Port is 1433.

dowser

netstat -a will show all listening ports.

Are all of the sql services running? What event log entries?

Are you *sure* it used to work? Back out the changes if so.

Richard

David_Wallis

Start the SQL Server Network Utility in SQL Server 2000. Select TCP, click Properties, and then enter the additional port separated by a comma; for example: 1433,5000.


Stop and then restart the SQL Server server, and review the errorlog. Your errorlog should resemble the following:


SQL server listening on TCP, Shared Memory, Named Pipes.<BR/>
SQL server listening on 157.54.178.42:1433, 157.54.178.42:5000, 127.0.0.1:1433, 127.0.0.1:5000.
Use the SQL Server Client Network Utility to modify your clients to spread the load accross the TCP ports. For example, two Web servers, both connecting to the same SQL Server on port 1433, can now split the load across 1433 and 5000. This allows the administrator to separate the traffic across multiple ports and increases the connection throughput.

David_Wallis

Sorry meant to say you could use that as a basis to check... is from the following:

RichB

Thanks for the info guys.

David - Did what you said:
Start the SQL Server Network Utility in SQL Server 2000. Select TCP, click Properties, and then enter the additional port separated by a comma; for example: 1433,5000.


Stop and then restart the SQL Server server, and review the errorlog. Your errorlog should resemble the following:


SQL server listening on TCP, Shared Memory, Named Pipes.<BR/>
SQL server listening on 157.54.178.42:1433, 157.54.178.42:5000, 127.0.0.1:1433, 127.0.0.1:5000.

All of that I did but the port seems to revert back to 2433 when I definatley typed in 1433. It said listening on 2433.
There were no errors in the event log viewer. This machine is running Windows98.

Arrrghhh. Any more ideas?

RichB

OK, so what does the hide server check box actually do?
After turning that off that doing it all again the port is now open.

Thanks for the info guys.

dowser

Er...hides the SQL server, perhaps...disabling tcp/1433 even? lol!

RichB

I really do not like computers....

David_Wallis

eh... do you mean the computer you are trying to connect to it with is running windows 98??

Mail me direct at work if you want david dot wallis at ventura dash uk dot com.. (sorry dont want junk mail!)

David