Hi all,
WSUS is installed on my windows 2003 server. During the install, parameter DISABLENETWORKPROTOCOLS was not specified, and so no remote connection was possible.
I used SVRNETCN.exe to enable TCP/IP remote connection on port 1433. However it seems not to work.
FROM THE SERVER :
osql -E -S MYSERVER\WSUS works fine but
osql -E -S 127.0.0.1\WSUS doesn't work, i get the famous error
[DBNETLIB]Serveur SQL spcifi non trouv.
[DBNETLIB]ConnectionOpen (Connect()).
If i user "osql -L" command, my instance doesn't appear in the list
FROM A CLIENT COMPUTER
osql -E -S MYSERVER\WSUS and
osql -E -S MY_SERVER_IP\WSUS don't work, i get the same error
I've tried tried to understand for hours, and i'm lost. I thought there may be a problem between SQL and 2003, and read SQL sp3a was required. I ran
select @.@.version from osql and got result
Microsoft SQL Server 2000 - 8.00.881 (Intel X86)
8.00.881 is not referenced in ms support as a patched version number !!!!!
Can anyone help me please ?
hi,
Shogre wrote:
Hi all,
WSUS is installed on my windows 2003 server. During the install, parameter DISABLENETWORKPROTOCOLS was not specified, and so no remote connection was possible.
I used SVRNETCN.exe to enable TCP/IP remote connection on port 1433. However it seems not to work.
FROM THE SERVER :
osql -E -S MYSERVER\WSUS works fine but
osql -E -S 127.0.0.1\WSUS doesn't work, i get the famous error
[DBNETLIB]Serveur SQL spcifi non trouv.
[DBNETLIB]ConnectionOpen (Connect()).If i user "osql -L" command, my instance doesn't appear in the list
FROM A CLIENT COMPUTER
osql -E -S MYSERVER\WSUS and
osql -E -S MY_SERVER_IP\WSUS don't work, i get the same error
I've tried tried to understand for hours, and i'm lost. I thought there may be a problem between SQL and 2003, and read SQL sp3a was required. I ran
select @.@.version from osql and got result
Microsoft SQL Server 2000 - 8.00.881 (Intel X86)
8.00.881 is not referenced in ms support as a patched version number !!!!!
Can anyone help me please ?
yep, I did not find 8.00.881 build as well... http://www.aspfaq.com/SQL2000Builds.asp ... where did you get it?
anyway... usually named instances do not listen on TCP/IP 1433 port as this one is "reserved" for default instances... using the Server Network Utility you shoud check if your named instance is listening on a dynamic associated port or on a fixed port as you should define a firewall exception as well for it... have a look at http://support.microsoft.com/kb/841249/en-us and http://support.microsoft.com/kb/841251/en-us for further info about the built in W2003 Windows Firewall and how to configure it for remote connections...
regards
No comments:
Post a Comment