June 6, 2005 at 12:30 pm
Hello,
I am not able to connect to the default instance from a different machine (ServerB) but I am able to connect to named instance on the same server (ServerA). Here is what I am trying,
On ServerA: Both the following commands work fine.
osql -SServerName -E
osql -SServerName\InstanceName -E
On ServerB:
osql -SServerName -E -- Doesn't work.
osql -SServerName\InstanceName -E -- Works fine.
Thanks,
R
June 7, 2005 at 4:11 am
Check out the Network Configuration properties of your MSDE. I think by default when you install MSDE the Network Configuration isn't configured.
Go to Enterprise Manager right click on the instance and click properties and enable the network configuration.
Hope this helps.
Jon
June 7, 2005 at 7:55 am
I do not have EM on ServerA where I am having problem with. Is there a SQL command that I can use to change the network configuration?
I modified the windows registry \\HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer value for LoginMode to 2 (and also tried 1). That didn't help either.
June 7, 2005 at 9:17 am
You want to run the sp_configure stored proc.
Check the books online for more help.
From my cursory perusal of the BOL, you want to do something like:
-- ========== Sample SCRIPT ===============
USE master
EXEC sp_configure 'remote access', '1'
RECONFIGURE
EXEC sp_configure
-- ========== END Sample SCRIPT ===============
You should be able to run that script through oSQL.
hth,
Ray
June 7, 2005 at 3:06 pm
The sp_configure above won't work for what you need to do.
It's used for remote stored procedure calls.
If the the default instance on ServerA was installed with the default options, then network access to that instance is disabled. You can use svrnetcn.exe to enable the network libraries you wish to use (e.g.; TCP/IP.)
Also, if that doesn't work (sometimes it doesn't) MS has a KB article showing how to correct the network library config.
http://support.microsoft.com/default.aspx?scid=kb;en-us;827204
Hope this helps!
-- J.Kozloski, MCDBA, MCITP
June 8, 2005 at 6:26 am
I have had simular problems even using enterprise manager on the second server server B.
my server A, w2k3 and a default msde sp3 install
what worked for me was to reinstall msde with security mode set to sql and strong passwords disabled. then I was able to connect.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply