I am trying to troubleshoot a SQL Server connection from my home machine
to an instance of SQL server running on my client's network using
Enterprise Manger and I am going through the steps in the MS KB article
How to troubleshoot connectivity issues in SQL Server 2000,
http://support.microsoft.com/default...;en-us;827422, which
suggests using odbcping.exe.
However, I cannot find this in my local SQL Server directories or in the
server Sql Server directories.
Doe anyone know where it is?
It's not installed by default with SQL 2000. The utility can
be found in the \x86\Binn directory on the SQL Server 2000
CD.
-Sue
On Sun, 12 Dec 2004 00:05:34 -0500, Douglas Forrest
<dforrest@.optonline.net> wrote:
>I am trying to troubleshoot a SQL Server connection from my home machine
>to an instance of SQL server running on my client's network using
>Enterprise Manger and I am going through the steps in the MS KB article
>How to troubleshoot connectivity issues in SQL Server 2000,
>http://support.microsoft.com/default...;en-us;827422, which
>suggests using odbcping.exe.
>However, I cannot find this in my local SQL Server directories or in the
>server Sql Server directories.
>Doe anyone know where it is?
|||Sue Hoegemeier wrote:
> It's not installed by default with SQL 2000. The utility can
> be found in the \x86\Binn directory on the SQL Server 2000
> CD.
> -Sue
> On Sun, 12 Dec 2004 00:05:34 -0500, Douglas Forrest
> <dforrest@.optonline.net> wrote:
>
>
Thanks
Showing posts with label home. Show all posts
Showing posts with label home. Show all posts
Thursday, March 22, 2012
Sunday, February 19, 2012
Cant connect to SQL server at work from home project
HI All,
i have copied a project from work i am working on and have created the same project at home in visual studio.net - everything is the same as it is at my work - for some reason though i cannot connect to the servers from my home project
can anyone help me with this - i get the message "SQL Server does not exist or access denied"
my web config has exactly the same set up with a key in appSettings as
<add key="My_Connection" value="User ID=myID;Password=myPassword;Initial Catalog=myCatalog;Data Source=xx.xx.xx.xx" />
can anyone tell me why i would not be able to even see my work database from home?
thanks in advance
GilesbAre you trying to point to the databases that are at work or new ones that you have created at home?
If they are at home have you checked to ensure that all the correct logins have been recreated?
If you are pointing to databases at work then it is likely that you can't access from outside of the work network.|||Few things u need to check.
1) Is there a firewall protecting your "Work" LAN? If yes, ask your system administrator to open the SQL port in your firewall and be sure to ask your system administrator to set a rules to restrict for your IP address or connecting by VPN.
2) You ve to configure your connection through Client utility. Specify a server name and External network IP address. That will direct your application to call external IP address.|||Sounds like someone where you work might actually know what they're doing. You shouldn't be able to connect unless connected by VPN. If you can, then you have bigger problems then the fact you copied your work project to a home computer. If you have permissions to work from home, have the network admins grant you remote user access and set you up to use the VPN. If not, either work more hours at work, or explain to your bosses why you can't work from home.|||Thanks for your help guys but i dont think i would need a VPN to merely access a database just to "login" as it were - basically i have an asp.net project that runs fine when testing at work - servers are at work, but when i run it from home i cant get a connection - should be just like running the site from home and hooking in to the database right ?
I am fairly new to the database scene - will ask someone at wotk whether any special configuration is required
thanks once again to all that replied
Gilesb|||Okie, yes and at the same time a resounding no!
If your home computer were part of the work network then yes, it would be exactly the same but it is not. If you VPN in to the work network then yes, you would be part of the same network.
To put a sql server onto your network with open ports to the real world is asking for trouble (yeah, there are probably ways of making sure it is mostly secure, but only mostly...). I'd estimate 90% of SQL Servers are safely hidden behind firewalls to prevent anything other then the machines on the internal network connecting to it.
i have copied a project from work i am working on and have created the same project at home in visual studio.net - everything is the same as it is at my work - for some reason though i cannot connect to the servers from my home project
can anyone help me with this - i get the message "SQL Server does not exist or access denied"
my web config has exactly the same set up with a key in appSettings as
<add key="My_Connection" value="User ID=myID;Password=myPassword;Initial Catalog=myCatalog;Data Source=xx.xx.xx.xx" />
can anyone tell me why i would not be able to even see my work database from home?
thanks in advance
GilesbAre you trying to point to the databases that are at work or new ones that you have created at home?
If they are at home have you checked to ensure that all the correct logins have been recreated?
If you are pointing to databases at work then it is likely that you can't access from outside of the work network.|||Few things u need to check.
1) Is there a firewall protecting your "Work" LAN? If yes, ask your system administrator to open the SQL port in your firewall and be sure to ask your system administrator to set a rules to restrict for your IP address or connecting by VPN.
2) You ve to configure your connection through Client utility. Specify a server name and External network IP address. That will direct your application to call external IP address.|||Sounds like someone where you work might actually know what they're doing. You shouldn't be able to connect unless connected by VPN. If you can, then you have bigger problems then the fact you copied your work project to a home computer. If you have permissions to work from home, have the network admins grant you remote user access and set you up to use the VPN. If not, either work more hours at work, or explain to your bosses why you can't work from home.|||Thanks for your help guys but i dont think i would need a VPN to merely access a database just to "login" as it were - basically i have an asp.net project that runs fine when testing at work - servers are at work, but when i run it from home i cant get a connection - should be just like running the site from home and hooking in to the database right ?
I am fairly new to the database scene - will ask someone at wotk whether any special configuration is required
thanks once again to all that replied
Gilesb|||Okie, yes and at the same time a resounding no!
If your home computer were part of the work network then yes, it would be exactly the same but it is not. If you VPN in to the work network then yes, you would be part of the same network.
To put a sql server onto your network with open ports to the real world is asking for trouble (yeah, there are probably ways of making sure it is mostly secure, but only mostly...). I'd estimate 90% of SQL Servers are safely hidden behind firewalls to prevent anything other then the machines on the internal network connecting to it.
Friday, February 10, 2012
Can't connect remotely to MSDE 2000 DB on WinXP Home Machine
Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
Hello,
I notice that you have posted the same question in our SQLServer newsgroup,
which community member have already responded. Please check the answers
there and if you need any further assistance on this particular issue,
please reply in that thread. Thanks for your understanding and cooperation.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
Hello,
I notice that you have posted the same question in our SQLServer newsgroup,
which community member have already responded. Please check the answers
there and if you need any further assistance on this particular issue,
please reply in that thread. Thanks for your understanding and cooperation.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Can't connect remotely to MSDE 2000 DB on WinXP Home Machine
Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopDe...aspx?tabid=37.
John
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>
|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopDe...aspx?tabid=37.
John
Can't connect remotely to MSDE 2000 DB on WinXP Home Machine
Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
ThanksHello,
I notice that you have posted the same question in our SQLServer newsgroup,
which community member have already responded. Please check the answers
there and if you need any further assistance on this particular issue,
please reply in that thread. Thanks for your understanding and cooperation.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
ThanksHello,
I notice that you have posted the same question in our SQLServer newsgroup,
which community member have already responded. Please check the answers
there and if you need any further assistance on this particular issue,
please reply in that thread. Thanks for your understanding and cooperation.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
========================================
=============
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.
Can't connect remotely to MSDE 2000 DB on WinXP Home Machine
Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
ThanksHi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37.
John
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
ThanksHi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/distsql/distsql_84xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=37.
John
Can't connect remotely to MSDE 2000 DB on WinXP Home Machine
Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
Hello,
I notice that you have posted the same question in our SQLServer newsgroup,
which community member have already responded. Please check the answers
there and if you need any further assistance on this particular issue,
please reply in that thread. Thanks for your understanding and cooperation.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
Hello,
I notice that you have posted the same question in our SQLServer newsgroup,
which community member have already responded. Please check the answers
there and if you need any further assistance on this particular issue,
please reply in that thread. Thanks for your understanding and cooperation.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Can't connect remotely to MSDE 2000 DB on WinXP Home Machine
Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
hi,
Macsicarr wrote:
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but
> my queries are:
> Is it a problem with the original MSDE 2000 installer being installed
> on a WinXP SP2 machine or just a later version, ie MSDE SP3?
just up from service pack 3/3a.. before that sp, MSDE installed enabling
network protocols..
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they
> did on SP1?
both sp3 (and MSDE Rel A) and sp4 can be installed on WinXP sp2..
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original
> MSDE 2000 installer or do you have to update it to Service Pack 3 to
> perform this task?
the very first package did not support that parameter, that is new with sp3
(and MSDE Rel A)
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
0= enable network protocols
> Is there anyway of patching/fixing this installation to correct it or
> have I got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
>
you can enable the desired network protocol you can use the Server Network
Utility (svrnetcn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3kfaa4Ftvsl3U1@.individual.net...
hi,
Macsicarr wrote:
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but
> my queries are:
> Is it a problem with the original MSDE 2000 installer being installed
> on a WinXP SP2 machine or just a later version, ie MSDE SP3?
just up from service pack 3/3a.. before that sp, MSDE installed enabling
network protocols..
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they
> did on SP1?
both sp3 (and MSDE Rel A) and sp4 can be installed on WinXP sp2..
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original
> MSDE 2000 installer or do you have to update it to Service Pack 3 to
> perform this task?
the very first package did not support that parameter, that is new with sp3
(and MSDE Rel A)
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
0= enable network protocols
> Is there anyway of patching/fixing this installation to correct it or
> have I got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
>
you can enable the desired network protocol you can use the Server Network
Utility (svrnetcn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:e4aBmFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi Andrea
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3kfaa4Ftvsl3U1@.individual.net...
hi,
Macsicarr wrote:
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but
> my queries are:
> Is it a problem with the original MSDE 2000 installer being installed
> on a WinXP SP2 machine or just a later version, ie MSDE SP3?
just up from service pack 3/3a.. before that sp, MSDE installed enabling
network protocols..
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they
> did on SP1?
both sp3 (and MSDE Rel A) and sp4 can be installed on WinXP sp2..
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original
> MSDE 2000 installer or do you have to update it to Service Pack 3 to
> perform this task?
the very first package did not support that parameter, that is new with sp3
(and MSDE Rel A)
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
0= enable network protocols
> Is there anyway of patching/fixing this installation to correct it or
> have I got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
>
you can enable the desired network protocol you can use the Server Network
Utility (svrnetcn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi,
Macsicarr wrote:
> Hi Andrea
> My version of MSDE is:
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
and this is MSDE retail version (RTM) on WinXP sp2
> But I still can't get a remote LAN or WAN machine to connect to my
> MSDE installation. It still says SQL Server does not exist or access
> denied, even though local machine use is fine and I have no firewall
> security on to block it.
are you sure the Windows Firewall, automatically enabled when installing
WinXP sp2, is not trapping you?
> I've even run the Server Network Utility (svrnetcn.exe) that you
> suggested and found that Named Pipes and TCP/IP are already enabled
> and ready to go.
MSDE retail version default behavior...
try a telnet connection on the MSDE port..
c:\..\>telnet ComputerName port_used_by_MSDE
if the screen becomes black you are connected to MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||HI Andrea
Thanks for the prompt reply.
In Windows Firewall it is set to Off. Although I would have thought
Microsoft would dim the other tabs (eg Exceptions and Advanced) seeing as
I've turned the firewall off I'm presuming that these have no effect.
The problem I have is that the error log quite clearly states that it is
listening on Shared Memory and Named Pipes - no TCP/IP is mentioned. Why is
this so?
The telnet test confirmed that it couldn't connect.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3kkp0tFull7hU1@.individual.net...
hi,
Macsicarr wrote:
> Hi Andrea
> My version of MSDE is:
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
and this is MSDE retail version (RTM) on WinXP sp2
> But I still can't get a remote LAN or WAN machine to connect to my
> MSDE installation. It still says SQL Server does not exist or access
> denied, even though local machine use is fine and I have no firewall
> security on to block it.
are you sure the Windows Firewall, automatically enabled when installing
WinXP sp2, is not trapping you?
> I've even run the Server Network Utility (svrnetcn.exe) that you
> suggested and found that Named Pipes and TCP/IP are already enabled
> and ready to go.
MSDE retail version default behavior...
try a telnet connection on the MSDE port..
c:\..\>telnet ComputerName port_used_by_MSDE
if the screen becomes black you are connected to MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello,
You may need to backup you registry file first, then check if you have the
following registry key:
HKLM/Software/Microsoft/Microsoft SQL
Server/mssql$<instancename>/MSSQLServer/SuperSocketNetLib/Tcp/
If not, add above registry key. Restart SQL server. Check the SQL log again
to see if it is listening on the TCP port.
The following articles are for your reference:
841251 How to enable SQL Server connectivity on Windows XP Service Pack 2
http://support.microsoft.com/?id=841251
841252 How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
http://support.microsoft.com/?id=841252
328306 Potential causes of the "SQL Server does not exist or access denied"
http://support.microsoft.com/?id=328306
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
Thanks
hi,
Macsicarr wrote:
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but
> my queries are:
> Is it a problem with the original MSDE 2000 installer being installed
> on a WinXP SP2 machine or just a later version, ie MSDE SP3?
just up from service pack 3/3a.. before that sp, MSDE installed enabling
network protocols..
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they
> did on SP1?
both sp3 (and MSDE Rel A) and sp4 can be installed on WinXP sp2..
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original
> MSDE 2000 installer or do you have to update it to Service Pack 3 to
> perform this task?
the very first package did not support that parameter, that is new with sp3
(and MSDE Rel A)
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
0= enable network protocols
> Is there anyway of patching/fixing this installation to correct it or
> have I got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
>
you can enable the desired network protocol you can use the Server Network
Utility (svrnetcn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3kfaa4Ftvsl3U1@.individual.net...
hi,
Macsicarr wrote:
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but
> my queries are:
> Is it a problem with the original MSDE 2000 installer being installed
> on a WinXP SP2 machine or just a later version, ie MSDE SP3?
just up from service pack 3/3a.. before that sp, MSDE installed enabling
network protocols..
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they
> did on SP1?
both sp3 (and MSDE Rel A) and sp4 can be installed on WinXP sp2..
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original
> MSDE 2000 installer or do you have to update it to Service Pack 3 to
> perform this task?
the very first package did not support that parameter, that is new with sp3
(and MSDE Rel A)
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
0= enable network protocols
> Is there anyway of patching/fixing this installation to correct it or
> have I got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
>
you can enable the desired network protocol you can use the Server Network
Utility (svrnetcn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:e4aBmFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi Andrea
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3kfaa4Ftvsl3U1@.individual.net...
hi,
Macsicarr wrote:
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but
> my queries are:
> Is it a problem with the original MSDE 2000 installer being installed
> on a WinXP SP2 machine or just a later version, ie MSDE SP3?
just up from service pack 3/3a.. before that sp, MSDE installed enabling
network protocols..
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they
> did on SP1?
both sp3 (and MSDE Rel A) and sp4 can be installed on WinXP sp2..
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original
> MSDE 2000 installer or do you have to update it to Service Pack 3 to
> perform this task?
the very first package did not support that parameter, that is new with sp3
(and MSDE Rel A)
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
0= enable network protocols
> Is there anyway of patching/fixing this installation to correct it or
> have I got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
>
you can enable the desired network protocol you can use the Server Network
Utility (svrnetcn.exe)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi,
Macsicarr wrote:
> Hi Andrea
> My version of MSDE is:
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
and this is MSDE retail version (RTM) on WinXP sp2
> But I still can't get a remote LAN or WAN machine to connect to my
> MSDE installation. It still says SQL Server does not exist or access
> denied, even though local machine use is fine and I have no firewall
> security on to block it.
are you sure the Windows Firewall, automatically enabled when installing
WinXP sp2, is not trapping you?
> I've even run the Server Network Utility (svrnetcn.exe) that you
> suggested and found that Named Pipes and TCP/IP are already enabled
> and ready to go.
MSDE retail version default behavior...
try a telnet connection on the MSDE port..
c:\..\>telnet ComputerName port_used_by_MSDE
if the screen becomes black you are connected to MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||HI Andrea
Thanks for the prompt reply.
In Windows Firewall it is set to Off. Although I would have thought
Microsoft would dim the other tabs (eg Exceptions and Advanced) seeing as
I've turned the firewall off I'm presuming that these have no effect.
The problem I have is that the error log quite clearly states that it is
listening on Shared Memory and Named Pipes - no TCP/IP is mentioned. Why is
this so?
The telnet test confirmed that it couldn't connect.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3kkp0tFull7hU1@.individual.net...
hi,
Macsicarr wrote:
> Hi Andrea
> My version of MSDE is:
> Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
> Aug 6 2000 00:57:48
> Copyright (c) 1988-2000 Microsoft Corporation
> Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
and this is MSDE retail version (RTM) on WinXP sp2
> But I still can't get a remote LAN or WAN machine to connect to my
> MSDE installation. It still says SQL Server does not exist or access
> denied, even though local machine use is fine and I have no firewall
> security on to block it.
are you sure the Windows Firewall, automatically enabled when installing
WinXP sp2, is not trapping you?
> I've even run the Server Network Utility (svrnetcn.exe) that you
> suggested and found that Named Pipes and TCP/IP are already enabled
> and ready to go.
MSDE retail version default behavior...
try a telnet connection on the MSDE port..
c:\..\>telnet ComputerName port_used_by_MSDE
if the screen becomes black you are connected to MSDE...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello,
You may need to backup you registry file first, then check if you have the
following registry key:
HKLM/Software/Microsoft/Microsoft SQL
Server/mssql$<instancename>/MSSQLServer/SuperSocketNetLib/Tcp/
If not, add above registry key. Restart SQL server. Check the SQL log again
to see if it is listening on the TCP port.
The following articles are for your reference:
841251 How to enable SQL Server connectivity on Windows XP Service Pack 2
http://support.microsoft.com/?id=841251
841252 How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
http://support.microsoft.com/?id=841252
328306 Potential causes of the "SQL Server does not exist or access denied"
http://support.microsoft.com/?id=328306
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
Business-Critical Phone Support (BCPS) provides you with technical phone
support at no charge during critical LAN outages or "business down"
situations. This benefit is available 24 hours a day, 7 days a week to all
Microsoft technology partners in the United States and Canada.
This and other support options are available here:
BCPS:
https://partner.microsoft.com/US/tec...rview/40010469
Others: https://partner.microsoft.com/US/tec...pportoverview/
If you are outside the United States, please visit our International
Support page:
http://support.microsoft.com/common/international.aspx
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
Can't connect remotely to MSDE 2000 DB on WinXP Home Machine
Hi All
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
ThanksHi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/d...
4xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/d...
4xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lo
ck
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/d...
4xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopD...aspx?tabid=37.
John
Having 'Google-ised' I've found that there does appear to be a problem
connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN), but
I haven't found what the concrete solution is.
It definitely appears to be a Windows inflicted problem, as I can connect to
the DB no problem if I create and connect to the ODBC DSN on the same
machine as the MSDE installation and if I use a remote Apple Mac machine to
connect to it via a combo of a router program and the local ODBC DSN then it
works fine.
I have also eliminated the other possibilities by disabling all of the
firewalls (ie Windows' own and Norton) and ultimately when I put the full
blown version of SQL Server on the same machine the remote connection works
perfectly.
Looking through the sites it appears that you have to put
DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
queries are:
Is it a problem with the original MSDE 2000 installer being installed on a
WinXP SP2 machine or just a later version, ie MSDE SP3?
Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
SP1?
Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE 2000
installer or do you have to update it to Service Pack 3 to perform this
task?
Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
Is there anyway of patching/fixing this installation to correct it or have I
got to de-tach the DBs and re-install MSDE with this
DISABLENETWORKPROTOCOLS=0 switch in the ini?
ThanksHi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/d...
4xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/d...
4xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||I've just checked the log and it still doesn't state that it's using TCP/IP
even though the network util only has TCP/IP in the right-hand box:
2005-07-25 18:42:40.29 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2005-07-25 18:42:40.60 server SQL Server configured for thread mode
processing.
2005-07-25 18:42:40.60 server Using dynamic lock allocation. [500] Lo
ck
Blocks, [1000] Lock Owner Blocks.
2005-07-25 18:42:40.62 spid3 Starting up database 'master'.
2005-07-25 18:42:41.04 server Using 'SSNETLIB.DLL' version '8.0.194'.
2005-07-25 18:42:41.07 spid5 Starting up database 'model'.
2005-07-25 18:42:41.12 spid3 Server name is 'FREDPC'.
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 4
2005-07-25 18:42:41.12 spid3 Skipping startup of clean database id 5
2005-07-25 18:42:41.35 spid5 Clearing tempdb database.
2005-07-25 18:42:42.54 spid5 Starting up database 'tempdb'.
2005-07-25 18:42:42.65 spid3 Recovery complete.
2005-07-25 18:42:56.09 server SQL server listening on Shared Memory,
Named Pipes. <<<<
2005-07-25 18:42:56.09 server SQL Server is ready for client connections
2005-07-25 18:43:17.17 spid51 Starting up database 'DemoData'.
2005-07-25 19:08:22.85 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
What am I doing wrong?
"Macsicarr" <No3@.Spam67.com> wrote in message
news:ulbflFUkFHA.3164@.TK2MSFTNGP15.phx.gbl...
Hi John
My version of MSDE is:
Microsoft SQL Server 2000 - 8.00.194 (Intel X86)
Aug 6 2000 00:57:48
Copyright (c) 1988-2000 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
But I still can't get a remote LAN or WAN machine to connect to my MSDE
installation. It still says SQL Server does not exist or access denied,
even though local machine use is fine and I have no firewall security on to
block it.
I've even run the Server Network Utility (svrnetcn.exe) that you suggested
and found that Named Pipes and TCP/IP are already enabled and ready to go.
What am I doing wrong?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:O6Rcs%237jFHA.2644@.TK2MSFTNGP09.phx.gbl...
Hi
If you have not service packed the MSDE installation what is @.@.VERSION?
Use DISABLENETWORKPROTOCOLS=0 if you want to have the protocols
automatically enabled on a new installation see
http://msdn.microsoft.com/library/d...
4xl.asp
for more.
You can enable them afterwards by running the command utility svrnetcn.exe
John
"Macsicarr" <nospam@.nospam.com> wrote in message
news:uW2w$E5jFHA.3064@.TK2MSFTNGP15.phx.gbl...
> Hi All
> Having 'Google-ised' I've found that there does appear to be a problem
> connecting to an MSDE 2000 DB from a remote machine (either LAN or WAN),
> but
> I haven't found what the concrete solution is.
> It definitely appears to be a Windows inflicted problem, as I can connect
> to
> the DB no problem if I create and connect to the ODBC DSN on the same
> machine as the MSDE installation and if I use a remote Apple Mac machine
> to
> connect to it via a combo of a router program and the local ODBC DSN then
> it
> works fine.
> I have also eliminated the other possibilities by disabling all of the
> firewalls (ie Windows' own and Norton) and ultimately when I put the full
> blown version of SQL Server on the same machine the remote connection
> works
> perfectly.
> Looking through the sites it appears that you have to put
> DISABLENETWORKPROTOCOLS=0 in the setup ini of the MSDE installer, but my
> queries are:
> Is it a problem with the original MSDE 2000 installer being installed on a
> WinXP SP2 machine or just a later version, ie MSDE SP3?
> Is it that no MSDE 2000 installer will work on WinXP SP2 when they did on
> SP1?
> Can you use this DISABLENETWORKPROTOCOLS=0 command on the original MSDE
> 2000
> installer or do you have to update it to Service Pack 3 to perform this
> task?
> Is it DISABLENETWORKPROTOCOLS=0 or DISABLENETWORKPROTOCOLS=1?
> Is there anyway of patching/fixing this installation to correct it or have
> I
> got to de-tach the DBs and re-install MSDE with this
> DISABLENETWORKPROTOCOLS=0 switch in the ini?
> Thanks
>
>|||Hi
You need to make sure that TCP/IP is in the client protocols (using the
client network configuration utitilty on the client) as well as on the
server. You may want to try pinging the server from the client. If it
responds try using telnet to connect to the port you are using (the
default port is 1433).
You @.@.VERSION shows that no patches or service packs have been
installed. http://www.sqlsecurity.com/DesktopD...aspx?tabid=37.
John
Subscribe to:
Posts (Atom)