Showing posts with label sbs2003. Show all posts
Showing posts with label sbs2003. Show all posts

Wednesday, March 21, 2012

MSDE on SBS2003 from Network

I have created a new MSDE instance on my SBS 2003 Standard server, using
MSDE setup.
The service is started, and I can access the MSDE instance locally on the
server, but I am unable to access it from other PCs on the network (in the
domain).
Specifically, I am using SQL Server Enterprise Manager. It reports the
message "Sql Server does not exist or access denied" when I try to connect
to the instance (using "myserver\instance-name"). I tried ISQL and also get
access denied.
I installed Enterprise Manager locally on the server and it connects to the
instance without problem.
Looking at the Properties/General/Network Configuration I can see TCPIP is
enabled and now using port 1433 (although it was set to port 0 after
installation?).
My user account is a valid login with the "System Administrator" role an has
dbo access to all databases.
The Windows Firewall allows port 1433 at the client and no firewall on the
server.
What else to check?
richlm wrote:

>I have created a new MSDE instance on my SBS 2003 Standard server, using
>MSDE setup.
>The service is started, and I can access the MSDE instance locally on the
>server, but I am unable to access it from other PCs on the network (in the
>domain).
>Specifically, I am using SQL Server Enterprise Manager. It reports the
>message "Sql Server does not exist or access denied" when I try to connect
>to the instance (using "myserver\instance-name"). I tried ISQL and also
>get access denied.
The default for MSDE is to not listen to the network, only the local
machine.

>I installed Enterprise Manager locally on the server and it connects to
>the instance without problem.
>Looking at the Properties/General/Network Configuration I can see TCPIP is
>enabled and now using port 1433 (although it was set to port 0 after
>installation?).
This was in the Server Network Utility, yes?
Has the MSDE instance been restarted since you enabled a network protocol?

>My user account is a valid login with the "System Administrator" role an
>has dbo access to all databases.
>The Windows Firewall allows port 1433 at the client and no firewall on the
>server.
The Windows Firewall on a client is irrelevant, since it has no impact on
outgoing connections. It would only be of interest if MSDE (or SQL) was
installed on the workstation itself.
Out of interest, where did you get the SQL client utilities from? They're
not included with SBS2003 Standard, nor are you licenced to use them in an
SBS2003 Standard environment.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Yes, TCP 1433 is at the top of the list of "enabled protocols" in the server
network utility, and I restarted the MSDE service after setting the port.
But I just realized that cliconfg does not allow me to choose which MSDE
instance to apply the changes to.
I just found a Microsoft support notice "Server Network Utility may display
incorrect protocol properties in SQL Server 2000" at
http://support.microsoft.com/?kbid=887700 - I'll investigate this further
(although I'm using SP4 so the hotfix does not apply).
As for licencing, I have an MSDN Universal subscription which includes the
use of SQL client tools for development purposes. But thanks for the
reminder, and I'll re-check the licence terms to make sure I've not
misunderstood something about where the tools can be used.
Richard.
|||richlm wrote:

>Yes, TCP 1433 is at the top of the list of "enabled protocols" in the
>server network utility, and I restarted the MSDE service after setting the
>port.
>But I just realized that cliconfg does not allow me to choose which MSDE
>instance to apply the changes to.
Eh?

>I just found a Microsoft support notice "Server Network Utility may
>display incorrect protocol properties in SQL Server 2000" at
>http://support.microsoft.com/?kbid=887700 - I'll investigate this further
>(although I'm using SP4 so the hotfix does not apply).
>As for licencing, I have an MSDN Universal subscription which includes the
>use of SQL client tools for development purposes. But thanks for the
>reminder, and I'll re-check the licence terms to make sure I've not
>misunderstood something about where the tools can be used.
AIUI, the MSDN licence does not cover using the SQL client utilities to
manage a production server. So, unless your SBS is only used for your
development network, you are not legally allowed to use the MSDN licence
to manage SQL services on SBS. But hey, IANAL, nor a member of the licence
police...
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||OK - I should be running svrnetcn.exe and not cliconfg.exe...
Now I can choose the instance - and can confirm that the problem referred to
at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
workaround suggested there (choose another instance then go back to the one
you really wanted) refreshes the UI correctly.
But I still can't connect remotely using EM or OSQL - yet both work locally.
I've googled to the end of the earth and not found other suggestions so my
guess now is it's probably due to the fact I have installed VS2005 on my
client - which also installs SQL 2005 express.
When I try to connect using OSQL I get the following error:
[SQL Native Client]Unable to complete login process due to delay in opening
server connection.
This perhaps implies my client PC is "broken" for connecting to SQL 2000
instances?
The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
I think I'll wait for SQL 2005 launch in a couple of weeks, where
(hopefully) this problem goes away.
Can anyone confirm this?
|||Richard Money wrote:

>OK - I should be running svrnetcn.exe and not cliconfg.exe...
>Now I can choose the instance - and can confirm that the problem referred
>to at http://support.microsoft.com/?kbid=887700 also applies to SP4. The
>workaround suggested there (choose another instance then go back to the
>one you really wanted) refreshes the UI correctly.
>But I still can't connect remotely using EM or OSQL - yet both work
>locally. I've googled to the end of the earth and not found other
>suggestions so my guess now is it's probably due to the fact I have
>installed VS2005 on my client - which also installs SQL 2005 express.
>When I try to connect using OSQL I get the following error:
>[SQL Native Client]Unable to complete login process due to delay in
>opening server connection.
>This perhaps implies my client PC is "broken" for connecting to SQL 2000
>instances?
>The version of "SQL Server Native Client" I currently use is 9.00.1314.06.
>I think I'll wait for SQL 2005 launch in a couple of weeks, where
>(hopefully) this problem goes away.
>Can anyone confirm this?
I don't know whether SQL2005 beta client tools can communicate with
SQL2000. I suspect that that is something likely to be left until very
close to RTM (and may require that SQL2000 gets an update of some sort).
I'd stick to trying with SQL2000 client utilities.
Steve Foster [SBS MVP]
MVPs do not work for Microsoft. Please reply only to the newsgroups.
|||Pretty sure that my problem connecting to MSDE over network was due to a
pre-release version of SQL2005 Express (sept. CTP) on my client.
Have just successfully installed the RTM of SQL Express on SBS as a named
instance, enabled networking using the SQL Server Configuration Manager, and
I can connect to the instance from VS2005 (RTM) running on another machine.
The default SBS instances for Sharepoint and SBSMonitoring are still running
MSDE (and still work!).
Now I'm happy:-)

MSDE on SBS2003

Hi, I'm about going to be using a database on the MSDE installed with
Windows SBS 2003. The problem is that in the service manager there are no
servers or services listed. Do I have to reinstall? Thanks.
Message posted via http://www.droptable.com
Supposed to be based on a security update.
"
Known issue, it doesn't matter. SQL/MSDE is actually running, and if you
want, you can delete the link to the SQL Manager in Start Menu -> All
Programs -> Startup, if you don't want to see the icon"
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Ben Harrison via droptable.com" <forum@.nospam.droptable.com> schrieb im
Newsbeitrag news:fb473d43c11745b68136ae18440f2383@.droptable.co m...
> Hi, I'm about going to be using a database on the MSDE installed with
> Windows SBS 2003. The problem is that in the service manager there are no
> servers or services listed. Do I have to reinstall? Thanks.
> --
> Message posted via http://www.droptable.com
|||hi Ben,
Ben Harrison via droptable.com wrote:
> Hi, I'm about going to be using a database on the MSDE installed with
> Windows SBS 2003. The problem is that in the service manager there
> are no servers or services listed. Do I have to reinstall? Thanks.
MSDE installs by default disabling network protocols and remote connections,
and this can prevent instances to be enlisted in the service manager combo,
as described in
http://support.microsoft.com/default...b;EN-US;814132
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE Not connecting remotely

Hi Guys,
I have a client who is running SBS2003. We are in the process of moving an
msde 2000 database from WIN2000 server to this server.
We have installed MSDE 2000 and it is running on the new server. We can
connect and access the DB locally. However, we cannot establish a connection
from any PCs on the network. There is no firewall between the PCs and the
server. We have done a port scan on both servers and port 1433 is open on
the old server and not the new one. The netstat command however says the
port is open on the new server.
Can anyone tell me how to open up port 1433 on the server or any other
solutions?Dave,
You should be able to use C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\svrnetcn.exe to configure which library the instance
listens on (like TCP/IP).
If you do a netstat -aon | find ":1433" is sql have the port open?
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving
an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a
connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?|||Dave,
Are you trying to get to the MSDE from the external side or internal side?
Do you have ISA installed? Is the SBS 2003 Std. Ed. or Premium Edition?
--
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving
an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a
connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?|||Hi Dave,
Use Client Network Utility from the client to configure for Network
Library(TCP/IP) and connection parameters (server name, 1433).
Ravi
"Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?|||> Are you trying to get to the MSDE from the external side or internal side?
> Do you have ISA installed? Is the SBS 2003 Std. Ed. or Premium Edition?
I am trying to access the MSDE from the internal network.
We are running SBS 2003 Std which does not include SQL server or ISA (It
sounds like it would have been a good idea to buy premium now doesn't it?)
I have run the svrnetcn.exe and TCP\IP is included. I have run the netstat
command you asked me to run and received the following information:
TCP 0.0.0.0:1433 0.0.0.0:0 Listening 5596|||Where will I find the Client Network Utility on MSDE2000? Will I need to
install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
connection. It works locally on the server.
I have tried creating an ODBC connection to the server, specifying port
1433, but this connection failed.
Is there a way to open port 1433 on SBS2003?
"Ravi" wrote:
> Hi Dave,
> Use Client Network Utility from the client to configure for Network
> Library(TCP/IP) and connection parameters (server name, 1433).
> Ravi
> "Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
> > Hi Guys,
> >
> > I have a client who is running SBS2003. We are in the process of moving an
> > msde 2000 database from WIN2000 server to this server.
> >
> > We have installed MSDE 2000 and it is running on the new server. We can
> > connect and access the DB locally. However, we cannot establish a connection
> > from any PCs on the network. There is no firewall between the PCs and the
> > server. We have done a port scan on both servers and port 1433 is open on
> > the old server and not the new one. The netstat command however says the
> > port is open on the new server.
> >
> > Can anyone tell me how to open up port 1433 on the server or any other
> > solutions?
>|||If you install the sql server client tools you will get this client
network utility.
"Dave" <Dave@.discussions.microsoft.com> wrote in message news:<F83A4647-58A5-4D55-8FAB-23D900D6070A@.microsoft.com>...
> Where will I find the Client Network Utility on MSDE2000? Will I need to
> install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
> connection. It works locally on the server.
> I have tried creating an ODBC connection to the server, specifying port
> 1433, but this connection failed.
> Is there a way to open port 1433 on SBS2003?
> "Ravi" wrote:
> > Hi Dave,
> >
> > Use Client Network Utility from the client to configure for Network
> > Library(TCP/IP) and connection parameters (server name, 1433).
> >
> > Ravi
> >
> > "Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
> > > Hi Guys,
> > >
> > > I have a client who is running SBS2003. We are in the process of moving an
> > > msde 2000 database from WIN2000 server to this server.
> > >
> > > We have installed MSDE 2000 and it is running on the new server. We can
> > > connect and access the DB locally. However, we cannot establish a connection
> > > from any PCs on the network. There is no firewall between the PCs and the
> > > server. We have done a port scan on both servers and port 1433 is open on
> > > the old server and not the new one. The netstat command however says the
> > > port is open on the new server.
> > >
> > > Can anyone tell me how to open up port 1433 on the server or any other
> > > solutions?|||Dave,
At least on the server take a look at \%systemroom$\system32\cliconfg.exe.
If you run the tasklist /svc with the process id from the netstat -aon for
port 1433 does it show it as being owned by SQL? For example
netstat -aon | find ":1433"
TCP 0.0.0.0:1433 0.0.0.0:0 Listening 5596
tasklist /svc | find "5596"
You might also take a look in \program files\microsoft sql
server\instancename\log directory at the ERRORLOG files to verify that the
instance you are expecting on TCP Port 1433 is the one you expect.. since by
default SBS 2003 will install an SBSMonitoring (MSDE) and SharePoint (WMSDE)
instance (both of which are only configured to use Shared Memory)
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Ravi" <sayravi@.yahoo.com> wrote in message
news:838d29e0.0410180905.f443d40@.posting.google.com...
> If you install the sql server client tools you will get this client
> network utility.
> "Dave" <Dave@.discussions.microsoft.com> wrote in message
news:<F83A4647-58A5-4D55-8FAB-23D900D6070A@.microsoft.com>...
> > Where will I find the Client Network Utility on MSDE2000? Will I need
to
> > install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
> > connection. It works locally on the server.
> >
> > I have tried creating an ODBC connection to the server, specifying port
> > 1433, but this connection failed.
> >
> > Is there a way to open port 1433 on SBS2003?
> >
> > "Ravi" wrote:
> >
> > > Hi Dave,
> > >
> > > Use Client Network Utility from the client to configure for Network
> > > Library(TCP/IP) and connection parameters (server name, 1433).
> > >
> > > Ravi
> > >
> > > "Dave" <Dave@.discussions.microsoft.com> wrote in message
news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
> > > > Hi Guys,
> > > >
> > > > I have a client who is running SBS2003. We are in the process of
moving an
> > > > msde 2000 database from WIN2000 server to this server.
> > > >
> > > > We have installed MSDE 2000 and it is running on the new server. We
can
> > > > connect and access the DB locally. However, we cannot establish a
connection
> > > > from any PCs on the network. There is no firewall between the PCs
and the
> > > > server. We have done a port scan on both servers and port 1433 is
open on
> > > > the old server and not the new one. The netstat command however
says the
> > > > port is open on the new server.
> > > >
> > > > Can anyone tell me how to open up port 1433 on the server or any
other
> > > > solutions?

MSDE Not connecting remotely

Hi Guys,
I have a client who is running SBS2003. We are in the process of moving an
msde 2000 database from WIN2000 server to this server.
We have installed MSDE 2000 and it is running on the new server. We can
connect and access the DB locally. However, we cannot establish a connection
from any PCs on the network. There is no firewall between the PCs and the
server. We have done a port scan on both servers and port 1433 is open on
the old server and not the new one. The netstat command however says the
port is open on the new server.
Can anyone tell me how to open up port 1433 on the server or any other
solutions?
Dave,
You should be able to use C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\svrnetcn.exe to configure which library the instance
listens on (like TCP/IP).
If you do a netstat -aon | find ":1433" is sql have the port open?

Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving
an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a
connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?
|||Dave,
Are you trying to get to the MSDE from the external side or internal side?
Do you have ISA installed? Is the SBS 2003 Std. Ed. or Premium Edition?
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving
an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a
connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?
|||Hi Dave,
Use Client Network Utility from the client to configure for Network
Library(TCP/IP) and connection parameters (server name, 1433).
Ravi
"Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?
|||> Are you trying to get to the MSDE from the external side or internal side?
> Do you have ISA installed? Is the SBS 2003 Std. Ed. or Premium Edition?
I am trying to access the MSDE from the internal network.
We are running SBS 2003 Std which does not include SQL server or ISA (It
sounds like it would have been a good idea to buy premium now doesn't it?)
I have run the svrnetcn.exe and TCP\IP is included. I have run the netstat
command you asked me to run and received the following information:
TCP 0.0.0.0:1433 0.0.0.0:0 Listening 5596
|||Where will I find the Client Network Utility on MSDE2000? Will I need to
install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
connection. It works locally on the server.
I have tried creating an ODBC connection to the server, specifying port
1433, but this connection failed.
Is there a way to open port 1433 on SBS2003?
"Ravi" wrote:

> Hi Dave,
> Use Client Network Utility from the client to configure for Network
> Library(TCP/IP) and connection parameters (server name, 1433).
> Ravi
> "Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
>
|||If you install the sql server client tools you will get this client
network utility.
"Dave" <Dave@.discussions.microsoft.com> wrote in message news:<F83A4647-58A5-4D55-8FAB-23D900D6070A@.microsoft.com>...[vbcol=seagreen]
> Where will I find the Client Network Utility on MSDE2000? Will I need to
> install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
> connection. It works locally on the server.
> I have tried creating an ODBC connection to the server, specifying port
> 1433, but this connection failed.
> Is there a way to open port 1433 on SBS2003?
> "Ravi" wrote:
|||Dave,
At least on the server take a look at \%systemroom$\system32\cliconfg.exe.
If you run the tasklist /svc with the process id from the netstat -aon for
port 1433 does it show it as being owned by SQL? For example
netstat -aon | find ":1433"
TCP 0.0.0.0:1433 0.0.0.0:0 Listening 5596
tasklist /svc | find "5596"
You might also take a look in \program files\microsoft sql
server\instancename\log directory at the ERRORLOG files to verify that the
instance you are expecting on TCP Port 1433 is the one you expect.. since by
default SBS 2003 will install an SBSMonitoring (MSDE) and SharePoint (WMSDE)
instance (both of which are only configured to use Shared Memory)

Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Ravi" <sayravi@.yahoo.com> wrote in message
news:838d29e0.0410180905.f443d40@.posting.google.co m...
> If you install the sql server client tools you will get this client
> network utility.
> "Dave" <Dave@.discussions.microsoft.com> wrote in message
news:<F83A4647-58A5-4D55-8FAB-23D900D6070A@.microsoft.com>...[vbcol=seagreen]
to[vbcol=seagreen]
news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...[vbcol=seagreen]
moving an[vbcol=seagreen]
can[vbcol=seagreen]
connection[vbcol=seagreen]
and the[vbcol=seagreen]
open on[vbcol=seagreen]
says the[vbcol=seagreen]
other[vbcol=seagreen]

MSDE Not connecting remotely

Hi Guys,
I have a client who is running SBS2003. We are in the process of moving an
msde 2000 database from WIN2000 server to this server.
We have installed MSDE 2000 and it is running on the new server. We can
connect and access the DB locally. However, we cannot establish a connectio
n
from any PCs on the network. There is no firewall between the PCs and the
server. We have done a port scan on both servers and port 1433 is open on
the old server and not the new one. The netstat command however says the
port is open on the new server.
Can anyone tell me how to open up port 1433 on the server or any other
solutions?Dave,
You should be able to use C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\svrnetcn.exe to configure which library the instance
listens on (like TCP/IP).
If you do a netstat -aon | find ":1433" is sql have the port open?
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving
an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a
connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?|||Dave,
Are you trying to get to the MSDE from the external side or internal side?
Do you have ISA installed? Is the SBS 2003 Std. Ed. or Premium Edition?
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving
an
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a
connection
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?|||Hi Dave,
Use Client Network Utility from the client to configure for Network
Library(TCP/IP) and connection parameters (server name, 1433).
Ravi
"Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-ACB5-4C46-B652-9E29E
E39DC0C@.microsoft.com>...
> Hi Guys,
> I have a client who is running SBS2003. We are in the process of moving a
n
> msde 2000 database from WIN2000 server to this server.
> We have installed MSDE 2000 and it is running on the new server. We can
> connect and access the DB locally. However, we cannot establish a connect
ion
> from any PCs on the network. There is no firewall between the PCs and the
> server. We have done a port scan on both servers and port 1433 is open on
> the old server and not the new one. The netstat command however says the
> port is open on the new server.
> Can anyone tell me how to open up port 1433 on the server or any other
> solutions?|||> Are you trying to get to the MSDE from the external side or internal side?
> Do you have ISA installed? Is the SBS 2003 Std. Ed. or Premium Edition?
I am trying to access the MSDE from the internal network.
We are running SBS 2003 Std which does not include SQL server or ISA (It
sounds like it would have been a good idea to buy premium now doesn't it?)
I have run the svrnetcn.exe and TCP\IP is included. I have run the netstat
command you asked me to run and received the following information:
TCP 0.0.0.0:1433 0.0.0.0:0 Listening 5596|||Where will I find the Client Network Utility on MSDE2000? Will I need to
install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
connection. It works locally on the server.
I have tried creating an ODBC connection to the server, specifying port
1433, but this connection failed.
Is there a way to open port 1433 on SBS2003?
"Ravi" wrote:

> Hi Dave,
> Use Client Network Utility from the client to configure for Network
> Library(TCP/IP) and connection parameters (server name, 1433).
> Ravi
> "Dave" <Dave@.discussions.microsoft.com> wrote in message news:<AE297F27-AC
B5-4C46-B652-9E29EE39DC0C@.microsoft.com>...
>|||If you install the sql server client tools you will get this client
network utility.
"Dave" <Dave@.discussions.microsoft.com> wrote in message news:<F83A4647-58A5-4D55-8FAB-23D90
0D6070A@.microsoft.com>...[vbcol=seagreen]
> Where will I find the Client Network Utility on MSDE2000? Will I need to
> install MSDE onto my PC? I am using MSDE Plus 2.1 to try to establish a
> connection. It works locally on the server.
> I have tried creating an ODBC connection to the server, specifying port
> 1433, but this connection failed.
> Is there a way to open port 1433 on SBS2003?
> "Ravi" wrote:
>|||Dave,
At least on the server take a look at \%systemroom$\system32\cliconfg.exe.
If you run the tasklist /svc with the process id from the netstat -aon for
port 1433 does it show it as being owned by SQL? For example
netstat -aon | find ":1433"
TCP 0.0.0.0:1433 0.0.0.0:0 Listening 5596
tasklist /svc | find "5596"
You might also take a look in \program files\microsoft sql
server\instancename\log directory at the ERRORLOG files to verify that the
instance you are expecting on TCP Port 1433 is the one you expect.. since by
default SBS 2003 will install an SBSMonitoring (MSDE) and SharePoint (WMSDE)
instance (both of which are only configured to use Shared Memory)
Hope that helps,
David Copeland
Microsoft Small Business Server Support
This posting is provided "AS IS" with no warranties, and confers no rights.
SBS Newsgroups:
SBS v4.x: microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs
"Ravi" <sayravi@.yahoo.com> wrote in message
news:838d29e0.0410180905.f443d40@.posting.google.com...
> If you install the sql server client tools you will get this client
> network utility.
> "Dave" <Dave@.discussions.microsoft.com> wrote in message
news:<F83A4647-58A5-4D55-8FAB-23D900D6070A@.microsoft.com>...[vbcol=seagreen]
to[vbcol=seagreen]
news:<AE297F27-ACB5-4C46-B652-9E29EE39DC0C@.microsoft.com>...[vbcol=seagreen]
moving an[vbcol=seagreen]
can[vbcol=seagreen]
connection[vbcol=seagreen]
and the[vbcol=seagreen]
open on[vbcol=seagreen]
says the[vbcol=seagreen]
other[vbcol=seagreen]