TCP/IP Sockets - can't connect 1

[Virgil]

I have a new 6.5 server (about to go to 7.0, just transferred from old hardware to new), however I cannot connect to the new server using TCP/IP sockets. I possibly missed something here in the 6.5 installation - is there a way to review which sockets are activated on the server and/or a way to activate or edit those already activated?
Named pipes connections work OK and there don't seem to be any other errors in the transfer.......

Like I say, I'm about to move to 7.0, is it easier to do this after the upgrade?

Thanks in advance (I hope)

David Corker.

 

[fluteplr]

You may as well do it after the transfer, you will have to do it again anyway. After the transfer run the 'server network utility' on the server and the 'client network utility' on the client, make sure they are both set up for tcp/ip

 

[pfontyn]

As well, you might need to adjust the time-out settings. To do this, go to the Tools menu in the Enterprise manager, select options and go to the Advanced tab. There are fields there that you can use to adjust the amount of time to wait for a response.

I have found that the default parameters for these settings sometimes so not allow for enough time to connect over a slow WAN or VPN.

 

[Virgil]

Thanks guys,

I had a BIG problem with this, we have a specialist server writing data to this SQL server which has some bizarre configuration in it. Luckily we have a service contract for the s/w so when I noticed it was obviously trying to use TCP/IP sockets I gave them a call. One of their guys obviously doesn't get out much, because without hesitation he knew a simple way to post-add sockets to a SQL 6.5 server.... verbatim!

So here's what he said (in the spirit of sharing);

Start regedt32 on your SQL server
find the key HKEY_LOCAL_MACHINE\Software\Microsoft\MSSQLServer\MSSQLServer\Listenon

if you haven't got TCP/IP active (i.e. just named pipes like I had) that key will be - SSNMP60,\\,\pipe\sql\query

to add TCP/IP, double-click that key and ON A NEW LINE add - SSMSS060,1433 (if you want to use a non-default port pick another number instead of 1433)

Stop MSSQLServer, SQLExecutive and MSDTC services and restart them.

..... and walk away smiling!

It works, I tried it.

Thanks again for your replies, I need some confidence boosting to help me into this 7.0 upgrade!

Cheers,

David.