Problem registering sql server

I am attempting to connect to a SQL Server across the Internet, when I
attempt to register the server through the Enterprise Manager using the IP
provided by the web hosting provider, I get the following error :"SQL Server
does not exist or access denied" , I was told by them that I should change
the default port from 1433 to 4000. I don't know where in SQL Servre i could
make this modification. Anybody knows how?
I have 2 instances of SQL Server, the default one and another named
instance, I am using the named instance, the default one has problems & is
not working, so changing this port thing would be related to the instance I
am working on or to the SQL Server as a whole?
Thanks in advance.
You can use the Client Network Utility to specify ports -
select properties for the TCP IP protocol and define the
port. The named instance would normally go through the
resolution service to determine what port it is listening
on.
Either way, you can always just create an alias using the
Client Network Utility and specify the ports when setting up
the alias.
-Sue
On Wed, 26 Jan 2005 04:19:03 -0800, JessyEzzy
<JessyEzzy@.discussions.microsoft.com> wrote:

>I am attempting to connect to a SQL Server across the Internet, when I
>attempt to register the server through the Enterprise Manager using the IP
>provided by the web hosting provider, I get the following error :"SQL Server
>does not exist or access denied" , I was told by them that I should change
>the default port from 1433 to 4000. I don't know where in SQL Servre i could
>make this modification. Anybody knows how?
>I have 2 instances of SQL Server, the default one and another named
>instance, I am using the named instance, the default one has problems & is
>not working, so changing this port thing would be related to the instance I
>am working on or to the SQL Server as a whole?
>Thanks in advance.

Problem registering sql server

I am attempting to connect to a SQL Server across the Internet, when I
attempt to register the server through the Enterprise Manager using the IP
provided by the web hosting provider, I get the following error :"SQL Server
does not exist or access denied" , I was told by them that I should change
the default port from 1433 to 4000. I don't know where in SQL Servre i could
make this modification. Anybody knows how?
I have 2 instances of SQL Server, the default one and another named
instance, I am using the named instance, the default one has problems & is
not working, so changing this port thing would be related to the instance I
am working on or to the SQL Server as a whole?
Thanks in advance.You can use the Client Network Utility to specify ports -
select properties for the TCP IP protocol and define the
port. The named instance would normally go through the
resolution service to determine what port it is listening
on.
Either way, you can always just create an alias using the
Client Network Utility and specify the ports when setting up
the alias.
-Sue
On Wed, 26 Jan 2005 04:19:03 -0800, JessyEzzy
<JessyEzzy@.discussions.microsoft.com> wrote:

>I am attempting to connect to a SQL Server across the Internet, when I
>attempt to register the server through the Enterprise Manager using the IP
>provided by the web hosting provider, I get the following error :"SQL Serve
r
>does not exist or access denied" , I was told by them that I should change
>the default port from 1433 to 4000. I don't know where in SQL Servre i coul
d
>make this modification. Anybody knows how?
>I have 2 instances of SQL Server, the default one and another named
>instance, I am using the named instance, the default one has problems & is
>not working, so changing this port thing would be related to the instance I
>am working on or to the SQL Server as a whole?
>Thanks in advance.sql

Problem registering server in Enterprise manager

Hi,
I've recently installed SQL Server 2000 on a laptop. The laptop has a
wireless connection to the LAN. I am able to register the other SQL Servers
on the network on the intance on the laptop, but I cannot register the
instance on the laptop from the others; I get the error message "SQL Server
does not existor access denied.|ConnectionOpen (Connect()"
*SQL Server is running on the laptop
*SQL Server agent is also running
*The login and password I use are correct (and I use SQL Server
authentication).
*I have installed SP3a
*I have disabled the Windows XP SP2 firewall and even uninstalled my other
firewall.
*The instance of SQL Server I am trying to register does show up as an
available server in the Register SQL Server Wizard.
What might be the problem? I would also very much appreciate if someone
could point me in the right direction regarding how to troubleshoot this
better, so I can find out where the failure occurs.Try registering the instance of SQL on the laptop FROM the laptop, but do no
t
use the localhost syntax, use the same syntax which is failing from across
the wireless network, whether that's using a netbios name, or rcpip
addresss... What happens then?
"Daniel" wrote:

> Hi,
> I've recently installed SQL Server 2000 on a laptop. The laptop has a
> wireless connection to the LAN. I am able to register the other SQL Server
s
> on the network on the intance on the laptop, but I cannot register the
> instance on the laptop from the others; I get the error message "SQL Serve
r
> does not existor access denied.|ConnectionOpen (Connect()"
> *SQL Server is running on the laptop
> *SQL Server agent is also running
> *The login and password I use are correct (and I use SQL Server
> authentication).
> *I have installed SP3a
> *I have disabled the Windows XP SP2 firewall and even uninstalled my other
> firewall.
> *The instance of SQL Server I am trying to register does show up as an
> available server in the Register SQL Server Wizard.
> What might be the problem? I would also very much appreciate if someone
> could point me in the right direction regarding how to troubleshoot this
> better, so I can find out where the failure occurs.
>|||I am using the Register SQL Server Wizard in Enterprise manager. From the
list of available servers, I choose Laptop3 (the name of the laptop). If I d
o
the same thing FROM the laptop there are no problems. Does this indicate tha
t
the problem is not actually SQL Server related, but rather something with th
e
network? I had the same symptoms a while back when registering other
instances of SQL Server, and that time I solved it by allowing incoming
traffic on ports TCP 1433, UDP 1434 and file and printer sharing in the
Windows XP Firewall. This time that didn't solve the problem and neither did
deactivating the firewall altogether.
Perhaps I should also say that when I installed SQL Server on the laptop, I
had to choose to let SQL Server and SQL Server Agent log in on the local
system account, because for some reason the domain user account I tried coul
d
not be validated. I changed this after the installation so now they both log
in on a domain user account.
The activated protocols are TCP/IP (1433) and named pipes.
"CBretana" wrote:

> Try registering the instance of SQL on the laptop FROM the laptop, but do
not
> use the localhost syntax, use the same syntax which is failing from across
> the wireless network, whether that's using a netbios name, or rcpip
> addresss... What happens then?|||I'd have whoever is responsible for your wireless access point check it out.
Sometimes traffic is filtered either to or from the wireless network for
security reasons. There may be necessary components of the registration
process that aren't allowed to pass through the wireless access point.
"Daniel" <daXniel_kriXstensXen_@.hotmail.com (remove the Xs)> wrote in
message news:26EEB241-9BAA-40D5-8846-DAC1AB702E7D@.microsoft.com...
> Hi,
> I've recently installed SQL Server 2000 on a laptop. The laptop has a
> wireless connection to the LAN. I am able to register the other SQL
Servers
> on the network on the intance on the laptop, but I cannot register the
> instance on the laptop from the others; I get the error message "SQL
Server
> does not existor access denied.|ConnectionOpen (Connect()"
> *SQL Server is running on the laptop
> *SQL Server agent is also running
> *The login and password I use are correct (and I use SQL Server
> authentication).
> *I have installed SP3a
> *I have disabled the Windows XP SP2 firewall and even uninstalled my other
> firewall.
> *The instance of SQL Server I am trying to register does show up as an
> available server in the Register SQL Server Wizard.
> What might be the problem? I would also very much appreciate if someone
> could point me in the right direction regarding how to troubleshoot this
> better, so I can find out where the failure occurs.
>|||When you attempt to register the server, you are logging in. There are two
ways to do this, with a userID and password, or using what is called
"Integrated security" which uses the userID / password of whomever is logged
on to the box you're doing it from. Which of these you are using depends on
how you installed SQL Server. When you installed SQL, did you select
Integrated Secutrity only, or did you choose Itegrated security AND SQL
Server Security ?
When you attempt to register the SQL Server, are you asked to enter a UserID
And Password? My guess is that you are not.. If that's true, then when you
attempt to register from another box, the SQL Server is not recognozing the
UserID of whomever is logged on there as being a valid Login...
Try to actually enter the "sa" and the sa password from the remote
Enterprise manager, AND from the laptop Enterprise Manager, and see if
there's a difference...
"Daniel" wrote:

> I am using the Register SQL Server Wizard in Enterprise manager. From the
> list of available servers, I choose Laptop3 (the name of the laptop). If I
do
> the same thing FROM the laptop there are no problems. Does this indicate t
hat
> the problem is not actually SQL Server related, but rather something with
the
> network? I had the same symptoms a while back when registering other
> instances of SQL Server, and that time I solved it by allowing incoming
> traffic on ports TCP 1433, UDP 1434 and file and printer sharing in the
> Windows XP Firewall. This time that didn't solve the problem and neither d
id
> deactivating the firewall altogether.
> Perhaps I should also say that when I installed SQL Server on the laptop,
I
> had to choose to let SQL Server and SQL Server Agent log in on the local
> system account, because for some reason the domain user account I tried co
uld
> not be validated. I changed this after the installation so now they both l
og
> in on a domain user account.
> The activated protocols are TCP/IP (1433) and named pipes.
>
> "CBretana" wrote:
>
>|||"CBretana" wrote:
> When you attempt to register the server, you are logging in. There are tw
o
> ways to do this, with a userID and password, or using what is called
> "Integrated security" which uses the userID / password of whomever is logg
ed
> on to the box you're doing it from. Which of these you are using depends
on
> how you installed SQL Server. When you installed SQL, did you select
> Integrated Secutrity only, or did you choose Itegrated security AND SQL
> Server Security ?
I chose mixed mode.

> When you attempt to register the SQL Server, are you asked to enter a User
ID
> And Password? My guess is that you are not.. If that's true, then when yo
u
> attempt to register from another box, the SQL Server is not recognozing th
e
> UserID of whomever is logged on there as being a valid Login...
> Try to actually enter the "sa" and the sa password from the remote
> Enterprise manager, AND from the laptop Enterprise Manager, and see if
> there's a difference...
Actually that's precisely what I do, and it only works from the laptop.
Sorry I didn't mention this already.|||Unfortunately, the guy responsible for these things are on vacation. I've
been able to register SQL Servers on laptops connected to the wireless acces
s
point previously. However, I did tamper with the wireless access point to ge
t
the new laptops to be able to connect to it. Pretty stupid of me not to chec
k
whether the SQL Servers on the old laptops are still accesible... That will
be the first thing I'll do on Monday. Even if it doesn't solve the problem i
t
will narrow down the possible causes of it.
"Mike Jansen" wrote:

> I'd have whoever is responsible for your wireless access point check it ou
t.
> Sometimes traffic is filtered either to or from the wireless network for
> security reasons. There may be necessary components of the registration
> process that aren't allowed to pass through the wireless access point.
> "Daniel" <daXniel_kriXstensXen_@.hotmail.com (remove the Xs)> wrote in
> message news:26EEB241-9BAA-40D5-8846-DAC1AB702E7D@.microsoft.com...
> Servers
> Server
>
>|||Ok, sorry, I should have asked this last time but forgot, since I askedit
first time...
From laptop, when you register, are you using "local" or typing the
laptop's server name, or IP Address to specify the server?
If you are using "local", then try using the same thing, on the laptop, that
is failing from over the network...
Say it's ServerName...
If that then also fails, on laptop, same as it fails from over network,
then your problem is related to networking. Try using the IPAddress
directly instead of server name. If that works, then problem is name
resolution (DNS or WINs resolution) issues.
"Daniel" wrote:

> "CBretana" wrote:
> I chose mixed mode.
>
> Actually that's precisely what I do, and it only works from the laptop.
> Sorry I didn't mention this already.

Problem Registering Existing Server

I am trying to reregister an existing server that we've been able to
register previously.
I can successfully register it inside the network, i.e., from another
workstation on the network, but when I try to register via a gateway, i.e.,
over the internet I can't. I can ping the server, and the router has port
forwarding setup correctly (port 1433), I've turned off the firewall, and
nothing else has changed that I am aware of, but it just won't respond. I
am confident that the SA password is correct.
I'm stumped. I have remote users who need to access this server, but can't
get in.
Can anyone give me any suggestions. I've tried everything I can imagine.
The one change on this system is that we had to reinstall the Server, and
we've installed CA Antivirus. But I've uninstalled the CA firewall
software, and turned off the Windows Firewall (just to get this up...we had
it running before with SQL traffic allowed).
Any Ideas are welcome!!
Bob
Hi Bob
"Bob Bartel" wrote:

> I am trying to reregister an existing server that we've been able to
> register previously.
> I can successfully register it inside the network, i.e., from another
> workstation on the network, but when I try to register via a gateway, i.e.,
> over the internet I can't. I can ping the server, and the router has port
> forwarding setup correctly (port 1433), I've turned off the firewall, and
> nothing else has changed that I am aware of, but it just won't respond. I
> am confident that the SA password is correct.
> I'm stumped. I have remote users who need to access this server, but can't
> get in.
> Can anyone give me any suggestions. I've tried everything I can imagine.
> The one change on this system is that we had to reinstall the Server, and
> we've installed CA Antivirus. But I've uninstalled the CA firewall
> software, and turned off the Windows Firewall (just to get this up...we had
> it running before with SQL traffic allowed).
> Any Ideas are welcome!!
> Bob
>
It would be safer to use a VPN for this rather than leaving the server open.
http://support.microsoft.com/kb/287932 describes the communication between
the client and server, make sure you are using TCP/IP protcols and the client
is not blocking the returning traffic. If you have set up this correctly you
should be in-undated with people trying to hack in.
John
|||As I mentioned, I have already had this working before. And only shut down
my firewall for this test. I agree a VPN is a good choice and I'll probably
turn it on, but...
But the real problem is that even with the router correctly forwarding 1433
and the firewall configured to allow the traffic, I can't register the
server remotely.
The only thing I can think of that may be effecting it is that I had to
reinstall the server. Can anyone think of anything that would keep remote
users from registering with a new install? Is there some setting on the
server that I neglected to turn back on?
Bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5E55FAA1-601D-4DED-8E5C-0324E2ED46B6@.microsoft.com...
> Hi Bob
> "Bob Bartel" wrote:
> It would be safer to use a VPN for this rather than leaving the server
> open.
> http://support.microsoft.com/kb/287932 describes the communication between
> the client and server, make sure you are using TCP/IP protcols and the
> client
> is not blocking the returning traffic. If you have set up this correctly
> you
> should be in-undated with people trying to hack in.
> John
|||Hi
"Bob Bartel" wrote:

> As I mentioned, I have already had this working before. And only shut down
> my firewall for this test. I agree a VPN is a good choice and I'll probably
> turn it on, but...
> But the real problem is that even with the router correctly forwarding 1433
> and the firewall configured to allow the traffic, I can't register the
> server remotely.
> The only thing I can think of that may be effecting it is that I had to
> reinstall the server. Can anyone think of anything that would keep remote
> users from registering with a new install? Is there some setting on the
> server that I neglected to turn back on?
> Bob
>
If this is SQL Express you may not have turned on remote access. If this is
a named instance then it would not be using the default ports.
John
|||Its a named instance...where to I specify the port?
bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1B0EB2A5-8E12-41C2-9D87-5C38176D1783@.microsoft.com...
> Hi
> "Bob Bartel" wrote:
> If this is SQL Express you may not have turned on remote access. If this
> is
> a named instance then it would not be using the default ports.
> John
|||Hi Bob
"Bob Bartel" wrote:

> Its a named instance...where to I specify the port?
> bob
In the SQL Server Configuration manager there will be an entry in the SQL
Server 2005 Network Configuration branch for your instance. This will shows
which protocols are installed and enabled. Right clicking TCP/IP and choosing
properties and on the IP Address tab you can set the protocol to be enabled
and also set the port. You will need to make sure that there are no other
instances using this port.
John

Problem Registering Existing Server

I am trying to reregister an existing server that we've been able to
register previously.
I can successfully register it inside the network, i.e., from another
workstation on the network, but when I try to register via a gateway, i.e.,
over the internet I can't. I can ping the server, and the router has port
forwarding setup correctly (port 1433), I've turned off the firewall, and
nothing else has changed that I am aware of, but it just won't respond. I
am confident that the SA password is correct.
I'm stumped. I have remote users who need to access this server, but can't
get in.
Can anyone give me any suggestions. I've tried everything I can imagine.
The one change on this system is that we had to reinstall the Server, and
we've installed CA Antivirus. But I've uninstalled the CA firewall
software, and turned off the Windows Firewall (just to get this up...we had
it running before with SQL traffic allowed).
Any Ideas are welcome!!
BobHi Bob
"Bob Bartel" wrote:
> I am trying to reregister an existing server that we've been able to
> register previously.
> I can successfully register it inside the network, i.e., from another
> workstation on the network, but when I try to register via a gateway, i.e.,
> over the internet I can't. I can ping the server, and the router has port
> forwarding setup correctly (port 1433), I've turned off the firewall, and
> nothing else has changed that I am aware of, but it just won't respond. I
> am confident that the SA password is correct.
> I'm stumped. I have remote users who need to access this server, but can't
> get in.
> Can anyone give me any suggestions. I've tried everything I can imagine.
> The one change on this system is that we had to reinstall the Server, and
> we've installed CA Antivirus. But I've uninstalled the CA firewall
> software, and turned off the Windows Firewall (just to get this up...we had
> it running before with SQL traffic allowed).
> Any Ideas are welcome!!
> Bob
>
It would be safer to use a VPN for this rather than leaving the server open.
http://support.microsoft.com/kb/287932 describes the communication between
the client and server, make sure you are using TCP/IP protcols and the client
is not blocking the returning traffic. If you have set up this correctly you
should be in-undated with people trying to hack in.
John|||As I mentioned, I have already had this working before. And only shut down
my firewall for this test. I agree a VPN is a good choice and I'll probably
turn it on, but...
But the real problem is that even with the router correctly forwarding 1433
and the firewall configured to allow the traffic, I can't register the
server remotely.
The only thing I can think of that may be effecting it is that I had to
reinstall the server. Can anyone think of anything that would keep remote
users from registering with a new install? Is there some setting on the
server that I neglected to turn back on?
Bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5E55FAA1-601D-4DED-8E5C-0324E2ED46B6@.microsoft.com...
> Hi Bob
> "Bob Bartel" wrote:
>> I am trying to reregister an existing server that we've been able to
>> register previously.
>> I can successfully register it inside the network, i.e., from another
>> workstation on the network, but when I try to register via a gateway,
>> i.e.,
>> over the internet I can't. I can ping the server, and the router has
>> port
>> forwarding setup correctly (port 1433), I've turned off the firewall,
>> and
>> nothing else has changed that I am aware of, but it just won't respond.
>> I
>> am confident that the SA password is correct.
>> I'm stumped. I have remote users who need to access this server, but
>> can't
>> get in.
>> Can anyone give me any suggestions. I've tried everything I can imagine.
>> The one change on this system is that we had to reinstall the Server, and
>> we've installed CA Antivirus. But I've uninstalled the CA firewall
>> software, and turned off the Windows Firewall (just to get this up...we
>> had
>> it running before with SQL traffic allowed).
>> Any Ideas are welcome!!
>> Bob
> It would be safer to use a VPN for this rather than leaving the server
> open.
> http://support.microsoft.com/kb/287932 describes the communication between
> the client and server, make sure you are using TCP/IP protcols and the
> client
> is not blocking the returning traffic. If you have set up this correctly
> you
> should be in-undated with people trying to hack in.
> John|||Hi
"Bob Bartel" wrote:
> As I mentioned, I have already had this working before. And only shut down
> my firewall for this test. I agree a VPN is a good choice and I'll probably
> turn it on, but...
> But the real problem is that even with the router correctly forwarding 1433
> and the firewall configured to allow the traffic, I can't register the
> server remotely.
> The only thing I can think of that may be effecting it is that I had to
> reinstall the server. Can anyone think of anything that would keep remote
> users from registering with a new install? Is there some setting on the
> server that I neglected to turn back on?
> Bob
>
If this is SQL Express you may not have turned on remote access. If this is
a named instance then it would not be using the default ports.
John|||Its a named instance...where to I specify the port?
bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1B0EB2A5-8E12-41C2-9D87-5C38176D1783@.microsoft.com...
> Hi
> "Bob Bartel" wrote:
>> As I mentioned, I have already had this working before. And only shut
>> down
>> my firewall for this test. I agree a VPN is a good choice and I'll
>> probably
>> turn it on, but...
>> But the real problem is that even with the router correctly forwarding
>> 1433
>> and the firewall configured to allow the traffic, I can't register the
>> server remotely.
>> The only thing I can think of that may be effecting it is that I had to
>> reinstall the server. Can anyone think of anything that would keep
>> remote
>> users from registering with a new install? Is there some setting on the
>> server that I neglected to turn back on?
>> Bob
>>
> If this is SQL Express you may not have turned on remote access. If this
> is
> a named instance then it would not be using the default ports.
> John|||Hi Bob
"Bob Bartel" wrote:
> Its a named instance...where to I specify the port?
> bob
In the SQL Server Configuration manager there will be an entry in the SQL
Server 2005 Network Configuration branch for your instance. This will shows
which protocols are installed and enabled. Right clicking TCP/IP and choosing
properties and on the IP Address tab you can set the protocol to be enabled
and also set the port. You will need to make sure that there are no other
instances using this port.
John

Problem Registering Existing Server

I am trying to reregister an existing server that we've been able to
register previously.
I can successfully register it inside the network, i.e., from another
workstation on the network, but when I try to register via a gateway, i.e.,
over the internet I can't. I can ping the server, and the router has port
forwarding setup correctly (port 1433), I've turned off the firewall, and
nothing else has changed that I am aware of, but it just won't respond. I
am confident that the SA password is correct.
I'm stumped. I have remote users who need to access this server, but can't
get in.
Can anyone give me any suggestions. I've tried everything I can imagine.
The one change on this system is that we had to reinstall the Server, and
we've installed CA Antivirus. But I've uninstalled the CA firewall
software, and turned off the Windows Firewall (just to get this up...we had
it running before with SQL traffic allowed).
Any Ideas are welcome!!
BobHi Bob
"Bob Bartel" wrote:

> I am trying to reregister an existing server that we've been able to
> register previously.
> I can successfully register it inside the network, i.e., from another
> workstation on the network, but when I try to register via a gateway, i.e.
,
> over the internet I can't. I can ping the server, and the router has port
> forwarding setup correctly (port 1433), I've turned off the firewall, and
> nothing else has changed that I am aware of, but it just won't respond. I
> am confident that the SA password is correct.
> I'm stumped. I have remote users who need to access this server, but can'
t
> get in.
> Can anyone give me any suggestions. I've tried everything I can imagine.
> The one change on this system is that we had to reinstall the Server, and
> we've installed CA Antivirus. But I've uninstalled the CA firewall
> software, and turned off the Windows Firewall (just to get this up...we ha
d
> it running before with SQL traffic allowed).
> Any Ideas are welcome!!
> Bob
>
It would be safer to use a VPN for this rather than leaving the server open.
http://support.microsoft.com/kb/287932 describes the communication between
the client and server, make sure you are using TCP/IP protcols and the clien
t
is not blocking the returning traffic. If you have set up this correctly you
should be in-undated with people trying to hack in.
John|||As I mentioned, I have already had this working before. And only shut down
my firewall for this test. I agree a VPN is a good choice and I'll probably
turn it on, but...
But the real problem is that even with the router correctly forwarding 1433
and the firewall configured to allow the traffic, I can't register the
server remotely.
The only thing I can think of that may be effecting it is that I had to
reinstall the server. Can anyone think of anything that would keep remote
users from registering with a new install? Is there some setting on the
server that I neglected to turn back on?
Bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:5E55FAA1-601D-4DED-8E5C-0324E2ED46B6@.microsoft.com...
> Hi Bob
> "Bob Bartel" wrote:
>
> It would be safer to use a VPN for this rather than leaving the server
> open.
> http://support.microsoft.com/kb/287932 describes the communication between
> the client and server, make sure you are using TCP/IP protcols and the
> client
> is not blocking the returning traffic. If you have set up this correctly
> you
> should be in-undated with people trying to hack in.
> John|||Hi
"Bob Bartel" wrote:

> As I mentioned, I have already had this working before. And only shut dow
n
> my firewall for this test. I agree a VPN is a good choice and I'll probab
ly
> turn it on, but...
> But the real problem is that even with the router correctly forwarding 143
3
> and the firewall configured to allow the traffic, I can't register the
> server remotely.
> The only thing I can think of that may be effecting it is that I had to
> reinstall the server. Can anyone think of anything that would keep remote
> users from registering with a new install? Is there some setting on the
> server that I neglected to turn back on?
> Bob
>
If this is SQL Express you may not have turned on remote access. If this is
a named instance then it would not be using the default ports.
John|||Its a named instance...where to I specify the port?
bob
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1B0EB2A5-8E12-41C2-9D87-5C38176D1783@.microsoft.com...
> Hi
> "Bob Bartel" wrote:
>
> If this is SQL Express you may not have turned on remote access. If this
> is
> a named instance then it would not be using the default ports.
> John|||Hi Bob
"Bob Bartel" wrote:

> Its a named instance...where to I specify the port?
> bob
In the SQL Server Configuration manager there will be an entry in the SQL
Server 2005 Network Configuration branch for your instance. This will shows
which protocols are installed and enabled. Right clicking TCP/IP and choosin
g
properties and on the IP Address tab you can set the protocol to be enabled
and also set the port. You will need to make sure that there are no other
instances using this port.
John