Hi.
I have installed Microsoft SQL Server Desktop on Windows XP Pro. I can
connect to database from remote machines with Windows 98Se, but i can't
connect from machines with Windows XP.
ChrisI think that it is a problem with not having the 'correct' client network
utilities installed.
On the Start menu, select [All Programs], [Microsoft SQL Server], th
en
[Client Network Utility].
In the [Enabled Protocols] window, you should have both TCP/IP and Named
Pipes.
If one is missing, select the missing protocol from the list on the left
side, and click the [Enable] button.
Hopefully, if my memory is correct, that will take care of the problem.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Krzysztof" <colinkj@.poczta.onet.pl> wrote in message
news:eb0a61$jov$1@.nemesis.news.tpi.pl...
> Hi.
> I have installed Microsoft SQL Server Desktop on Windows XP Pro. I can
> connect to database from remote machines with Windows 98Se, but i can't
> connect from machines with Windows XP.
> Chris
>
>|||Have you tried temporarily disabling the firewall on the XP machines?
John Opincar
john.opincar@.sundesksoftware.com
"Krzysztof" <colinkj@.poczta.onet.pl> wrote in message
news:eb0a61$jov$1@.nemesis.news.tpi.pl...
> Hi.
> I have installed Microsoft SQL Server Desktop on Windows XP Pro. I can
> connect to database from remote machines with Windows 98Se, but i can't
> connect from machines with Windows XP.
> Chris
>
>
Showing posts with label machines. Show all posts
Showing posts with label machines. Show all posts
Tuesday, March 27, 2012
Connection problem
I have 2 sql servers running on different machines. I want to manage both
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>sqlsql
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> > I have 2 sql servers running on different machines. I want to manage both
> > servers from one machine. When I try to add the other server in the
> > enterprise manager it gives me the error "sql server does not exist or
> access
> > denied". I am using a valid log on user name that is set up on the
> server, I
> > have even tried using a windows username. I know that the problem has to
> lie
> > in authentication because I know the server exist. Anyone know of
> anything I
> > may be doing wrong?
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>sqlsql
Sunday, March 25, 2012
Connection problem
I have 2 sql servers running on different machines. I want to manage both
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?
"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve
|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
sqlsql
servers from one machine. When I try to add the other server in the
enterprise manager it gives me the error "sql server does not exist or access
denied". I am using a valid log on user name that is set up on the server, I
have even tried using a windows username. I know that the problem has to lie
in authentication because I know the server exist. Anyone know of anything I
may be doing wrong?
"Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> I have 2 sql servers running on different machines. I want to manage both
> servers from one machine. When I try to add the other server in the
> enterprise manager it gives me the error "sql server does not exist or
access
> denied". I am using a valid log on user name that is set up on the
server, I
> have even tried using a windows username. I know that the problem has to
lie
> in authentication because I know the server exist. Anyone know of
anything I
> may be doing wrong?
To rule out the server permissions issue, in other words your account has
permissions on the server itself -- try using an account that has
administrative rights on the target server and sysadmin permissions on SQL
Server.
Steve
|||Ok here is what I tried. I went to the remote sql server and created a
windows user that is part of the admin group. I then went to the enterprise
manager on the remote sql server and created a user which I browsed for and
got from the windows users list. I gave that login SA rights on the sql
server. I then went back to the other server and tried to register the
remote sql server using sql authentication. I used the username and password
that I had created and I still get the same error message. Any ideas?
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Another thing I forgot to mention. I also tried to register the other server
on the remote server (the reverse of what I have been trying). When I go to
register the server I see seven or so other servers that we have here at
work; however when I have been doing it on the other computer I only see one
server (that being the remote sql server). I am wondering what may cause
this and if it might have something to do with the login issue.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Other things I have tried:
Pinging the remote sql server - works fine
telnet to port 1433 on the remote server - does NOT work
there is not a firewall between the two machines.
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
|||Problem Solved: I was really simple actually, all I had to do was go to the
properties of the remote sql server and configure the network configuration
to enable tcp/ip using port 1433
"Steve Thompson" wrote:
> "Benjamin" <Benjamin@.discussions.microsoft.com> wrote in message
> news:BBB264F3-FF58-40CD-9725-4BAC18E71A64@.microsoft.com...
> access
> server, I
> lie
> anything I
> To rule out the server permissions issue, in other words your account has
> permissions on the server itself -- try using an account that has
> administrative rights on the target server and sysadmin permissions on SQL
> Server.
> Steve
>
>
sqlsql
Monday, March 19, 2012
Connection issue with named instance
Hi all,
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instances
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
SylvainCan you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
&
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connection
> of these new machines ot My different SQL Servers. On this configuration we
> only speak of client/server connected on the same LAN without any antivirus
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse network
> they can't see named instance (only default instance is displayed (port 1433)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instances
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instance
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
> Can you please follow below links and let us know if it was helpful for you.
> http://sqljunkies.com/How%20To/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
> &
> http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
> > Hi all,
> >
> > Since the replacement of new client workstation I've trouble for connection
> > of these new machines ot My different SQL Servers. On this configuration we
> > only speak of client/server connected on the same LAN without any antivirus
> > enabled.
> > When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> > to my server via for example ODBC and in this case when they browse network
> > they can't see named instance (only default instance is displayed (port 1433)
> > !). Next to it if they force the name in the connection string they still
> > can't connect ot the server, because of the port resolution. My workaround
> > today is to force the port in the connection string of each client (quite
> > heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> > enable.
> > I've performed different test of connection (telnet 1433 work, PortQRY
> > return that 1433 and 1434 are working (but it didn't return all the instances
> > name), ping OK, tracert ok,...)
> >
> > Any help would be appreciated, thanks in advance
> > Sylvain
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instances
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
SylvainCan you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
&
http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connection
> of these new machines ot My different SQL Servers. On this configuration we
> only speak of client/server connected on the same LAN without any antivirus
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse network
> they can't see named instance (only default instance is displayed (port 1433)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instances
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instance
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
> Can you please follow below links and let us know if it was helpful for you.
> http://sqljunkies.com/How%20To/2E1101E0-D5C1-4DBD-A398-FE485DFA439B.scuk
> &
> http://support.microsoft.com/default.aspx?scid=kb;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
> > Hi all,
> >
> > Since the replacement of new client workstation I've trouble for connection
> > of these new machines ot My different SQL Servers. On this configuration we
> > only speak of client/server connected on the same LAN without any antivirus
> > enabled.
> > When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> > to my server via for example ODBC and in this case when they browse network
> > they can't see named instance (only default instance is displayed (port 1433)
> > !). Next to it if they force the name in the connection string they still
> > can't connect ot the server, because of the port resolution. My workaround
> > today is to force the port in the connection string of each client (quite
> > heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> > enable.
> > I've performed different test of connection (telnet 1433 work, PortQRY
> > return that 1433 and 1434 are working (but it didn't return all the instances
> > name), ping OK, tracert ok,...)
> >
> > Any help would be appreciated, thanks in advance
> > Sylvain
Connection issue with named instance
Hi all,
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instances
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
Sylvain
Can you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E110...85DFA439B.scuk
&
http://support.microsoft.com/default...b;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connection
> of these new machines ot My different SQL Servers. On this configuration we
> only speak of client/server connected on the same LAN without any antivirus
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse network
> they can't see named instance (only default instance is displayed (port 1433)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instances
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain
|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instance
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
[vbcol=seagreen]
> Can you please follow below links and let us know if it was helpful for you.
> http://sqljunkies.com/How%20To/2E110...85DFA439B.scuk
> &
> http://support.microsoft.com/default...b;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instances
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
Sylvain
Can you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E110...85DFA439B.scuk
&
http://support.microsoft.com/default...b;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connection
> of these new machines ot My different SQL Servers. On this configuration we
> only speak of client/server connected on the same LAN without any antivirus
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse network
> they can't see named instance (only default instance is displayed (port 1433)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instances
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain
|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instance
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
[vbcol=seagreen]
> Can you please follow below links and let us know if it was helpful for you.
> http://sqljunkies.com/How%20To/2E110...85DFA439B.scuk
> &
> http://support.microsoft.com/default...b;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
Connection issue with named instance
Hi all,
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433
)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instance
s
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
SylvainCan you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E11...485DFA439B.scuk
&
http://support.microsoft.com/defaul...kb;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connectio
n
> of these new machines ot My different SQL Servers. On this configuration w
e
> only speak of client/server connected on the same LAN without any antiviru
s
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse networ
k
> they can't see named instance (only default instance is displayed (port 14
33)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instan
ces
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instanc
e
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
[vbcol=seagreen]
> Can you please follow below links and let us know if it was helpful for yo
u.
> http://sqljunkies.com/How%20To/2E11...485DFA439B.scuk
> &
> http://support.microsoft.com/defaul...kb;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
>
Since the replacement of new client workstation I've trouble for connection
of these new machines ot My different SQL Servers. On this configuration we
only speak of client/server connected on the same LAN without any antivirus
enabled.
When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
to my server via for example ODBC and in this case when they browse network
they can't see named instance (only default instance is displayed (port 1433
)
!). Next to it if they force the name in the connection string they still
can't connect ot the server, because of the port resolution. My workaround
today is to force the port in the connection string of each client (quite
heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
enable.
I've performed different test of connection (telnet 1433 work, PortQRY
return that 1433 and 1434 are working (but it didn't return all the instance
s
name), ping OK, tracert ok,...)
Any help would be appreciated, thanks in advance
SylvainCan you please follow below links and let us know if it was helpful for you.
http://sqljunkies.com/How%20To/2E11...485DFA439B.scuk
&
http://support.microsoft.com/defaul...kb;en-us;287932
Regards
Surajit
"Sylvain" wrote:
> Hi all,
> Since the replacement of new client workstation I've trouble for connectio
n
> of these new machines ot My different SQL Servers. On this configuration w
e
> only speak of client/server connected on the same LAN without any antiviru
s
> enabled.
> When my users hae their new PC's (W2K - MDAC 2.6 SP1), they try to connect
> to my server via for example ODBC and in this case when they browse networ
k
> they can't see named instance (only default instance is displayed (port 14
33)
> !). Next to it if they force the name in the connection string they still
> can't connect ot the server, because of the port resolution. My workaround
> today is to force the port in the connection string of each client (quite
> heavy, 2500 workstations !!!) On my servers I have TCP/IP and Named Pipes
> enable.
> I've performed different test of connection (telnet 1433 work, PortQRY
> return that 1433 and 1434 are working (but it didn't return all the instan
ces
> name), ping OK, tracert ok,...)
> Any help would be appreciated, thanks in advance
> Sylvain|||Thanks for your reply.
Concerning the first link, after checking all cases the result is the same
than before, the only workaround is to create an alias (force port number).
All my clients even set on dynamically determine port, can't find an instanc
e
other than the default except if I set manually the expected port by the
server.
For the second link, after checking with my network team we have validate
that no firewall are placed between clients and servers.
Thanks for your help
Sylvain
"surajits" wrote:
[vbcol=seagreen]
> Can you please follow below links and let us know if it was helpful for yo
u.
> http://sqljunkies.com/How%20To/2E11...485DFA439B.scuk
> &
> http://support.microsoft.com/defaul...kb;en-us;287932
>
> Regards
> Surajit
>
>
> "Sylvain" wrote:
>
Connection issue across network
I have about 30 machines that I currently manage. I should also say, I just
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from my
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
Raymond Laubert
MCSE, MCDBA, MCT
So you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I just
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
> is the problem, I can not connect to this box from Enterprise Manager from my
> desktop. If I Remote Admin into the box everything works fine. If I try to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted my
> authenication as trusted. SQL is using the standard TCP port 1433.
> Any ideas?
> Thanks,
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can ping
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
> c.. On the client, is the firewall configured to permit access to the ports?
> d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from my
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
Raymond Laubert
MCSE, MCDBA, MCT
So you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I just
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
> is the problem, I can not connect to this box from Enterprise Manager from my
> desktop. If I Remote Admin into the box everything works fine. If I try to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted my
> authenication as trusted. SQL is using the standard TCP port 1433.
> Any ideas?
> Thanks,
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can ping
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and the server ports must be visible outside of the box. Here are a few things to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Config tool)
> c.. On the client, is the firewall configured to permit access to the ports?
> d.. Are you trying to connect to the ports or are you letting the DNS server resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see the ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Explorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and does it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4562BC@.microsoft.com...
|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
Connection issue across network
I have about 30 machines that I currently manage. I should also say, I just
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from m
y
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
--
Raymond Laubert
MCSE, MCDBA, MCTSo you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and t
he server ports must be visible outside of the box. Here are a few things to
check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config
tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server
resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the C
onnectionString)
f.. Does the server show up in the list of visible servers in Server Explore
r (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does i
t lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4
562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I jus
t
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in t
he
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Her
e
> is the problem, I can not connect to this box from Enterprise Manager from
my
> desktop. If I Remote Admin into the box everything works fine. If I try
to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log
in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted m
y
> authenication as trusted. SQL is using the standard TCP port 1433.
>
> Any ideas?
>
> Thanks,
>
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can pin
g
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
--
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and
the server ports must be visible outside of the box. Here are a few things
to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Con
fig tool)
> c.. On the client, is the firewall configured to permit access to the po
rts?
> d.. Are you trying to connect to the ports or are you letting the DNS se
rver resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see t
he ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Exp
lorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and do
es it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89
-488A-9AFB-B44A6B4562BC@.microsoft.com...|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
>
took over this position as Senior DBA. One machine is a Windows 2003 Quad
Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in the
SQL Admin group and SQL is set for both SQL and WIndows authenication. Here
is the problem, I can not connect to this box from Enterprise Manager from m
y
desktop. If I Remote Admin into the box everything works fine. If I try to
register the server with any authenication method it doesnt work. I have
tried my personal account, domain accounts, SA, other admin accounts and
they all come back with Server does not exist or access denied. If I log in
locally or via RA everything is fine. Other admins can access this box
remotely and we all have the same security settings. All of the other
servers register fine.
I reviewed the Windows event log and auditing show that SQL has accepted my
authenication as trusted. SQL is using the standard TCP port 1433.
Any ideas?
Thanks,
Raymond S Laubert
MCITP:Adminstration, MCDBA, MCSE, MCT
--
Raymond Laubert
MCSE, MCDBA, MCTSo you can connect on the server (via TA session) but not from a client.
Consider that the client needs to be permitted to see the server ports and t
he server ports must be visible outside of the box. Here are a few things to
check:
a.. Is the SQL Server Browser service running on the server?
b.. Are the external protocols enabled? (use SQL Server Surface Area Config
tool)
c.. On the client, is the firewall configured to permit access to the ports?
d.. Are you trying to connect to the ports or are you letting the DNS server
resolve the server instance?
e.. How are you trying to connect to the instance? In code? (Let's see the C
onnectionString)
f.. Does the server show up in the list of visible servers in Server Explore
r (Visual Studio)?
g.. Is the little yellow wire connected to the back of the server and does i
t lead (eventually) to the client? ;)
Check out Chapter 9 of my book... it's written for you (personally)... ;)
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89-488A-9AFB-B44A6B4
562BC@.microsoft.com...
>I have about 30 machines that I currently manage. I should also say, I jus
t
> took over this position as Senior DBA. One machine is a Windows 2003 Quad
> Processor 4GB ram box with SQL 2000 Standard Edition installed. I am in t
he
> SQL Admin group and SQL is set for both SQL and WIndows authenication. Her
e
> is the problem, I can not connect to this box from Enterprise Manager from
my
> desktop. If I Remote Admin into the box everything works fine. If I try
to
> register the server with any authenication method it doesnt work. I have
> tried my personal account, domain accounts, SA, other admin accounts and
> they all come back with Server does not exist or access denied. If I log
in
> locally or via RA everything is fine. Other admins can access this box
> remotely and we all have the same security settings. All of the other
> servers register fine.
> I reviewed the Windows event log and auditing show that SQL has accepted m
y
> authenication as trusted. SQL is using the standard TCP port 1433.
>
> Any ideas?
>
> Thanks,
>
> Raymond S Laubert
> MCITP:Adminstration, MCDBA, MCSE, MCT
> --
> Raymond Laubert
> MCSE, MCDBA, MCT|||Well, lets see...
I can connect to all the other servers via Enterprise Manager, so network
issues are taken care of.
I can connect to this server via Remote Admin and Terminal Server so
Security issues are taken care of.
Other DBAs and support personnel can connect to the server via Enterprise
Manager so configuration issues are taken care of.
Hmmm... I don't have a yellow wire... maybe that is the issue... oh
wait... mine is blue... yep it's connected as well.
Remember, I can connect to the other 29 servers via Enterprise Manager, this
is the only one I can not connect to. Other DBAs can connect to this server
as well as the other 29. We are all in the same security groups. I can pin
g
the server by address and name, so network is good.
I try not to put easy stuff on the board, but this one has me stumped.
Oh send me a copy of your book and I will proof read it for you, free of
charge of course. Maybe even promote it in the SQL Classes I teach.
--
Raymond Laubert
MCSE, MCDBA, MCT
"William (Bill) Vaughn" wrote:
[vbcol=seagreen]
> So you can connect on the server (via TA session) but not from a client.
> Consider that the client needs to be permitted to see the server ports and
the server ports must be visible outside of the box. Here are a few things
to check:
> a.. Is the SQL Server Browser service running on the server?
> b.. Are the external protocols enabled? (use SQL Server Surface Area Con
fig tool)
> c.. On the client, is the firewall configured to permit access to the po
rts?
> d.. Are you trying to connect to the ports or are you letting the DNS se
rver resolve the server instance?
> e.. How are you trying to connect to the instance? In code? (Let's see t
he ConnectionString)
> f.. Does the server show up in the list of visible servers in Server Exp
lorer (Visual Studio)?
> g.. Is the little yellow wire connected to the back of the server and do
es it lead (eventually) to the client? ;)
> Check out Chapter 9 of my book... it's written for you (personally)... ;)
>
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Ray Laubert" <ray@.rsl-webhosting.com> wrote in message news:70350431-1C89
-488A-9AFB-B44A6B4562BC@.microsoft.com...|||Send me your snail-mail address and I will...
Have you tried ODBC Ping?
Is the SqlBrowser service started?
Has the SQL Server been configured to expose the external protocols? It
sounds like it, but I would double-check. Are you addressing it via DNS
address or by IP? Again, seeing the connectstring would help.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Ray Laubert" <ray@.rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@.microsoft.com...[vbcol=seagreen]
> Well, lets see...
> I can connect to all the other servers via Enterprise Manager, so network
> issues are taken care of.
> I can connect to this server via Remote Admin and Terminal Server so
> Security issues are taken care of.
> Other DBAs and support personnel can connect to the server via Enterprise
> Manager so configuration issues are taken care of.
> Hmmm... I don't have a yellow wire... maybe that is the issue... oh
> wait... mine is blue... yep it's connected as well.
> Remember, I can connect to the other 29 servers via Enterprise Manager,
> this
> is the only one I can not connect to. Other DBAs can connect to this
> server
> as well as the other 29. We are all in the same security groups. I can
> ping
> the server by address and name, so network is good.
> I try not to put easy stuff on the board, but this one has me stumped.
> Oh send me a copy of your book and I will proof read it for you, free of
> charge of course. Maybe even promote it in the SQL Classes I teach.
> --
> Raymond Laubert
> MCSE, MCDBA, MCT
>
> "William (Bill) Vaughn" wrote:
>
Thursday, March 8, 2012
Connection Failed: SQl SErver Error 18456
I am runnig a program through Microsoft Access 2000 that uses SQL server and is run on 8 different machines. It has worked great for months but yesterday this message appeared:
Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login Failed for User 'SA'.
And when I try to use Outlook, this message is displayed:
The Microsoft Exchange Server Computer is not available. Either there are network problems or thhe Microsoft Exchange Server is down for mmaintenance.
Obvious problems with the SQL recognition but it seems to be up and running fine.
Any help appreciated.Make sure no change in SA's password and try connecting with other user with ADMIN privileges.
Connection Failed:
SQL State: '28000'
SQL Server Error: 18456
[Microsoft][ODBC SQL Server Driver][SQL Server]Login Failed for User 'SA'.
And when I try to use Outlook, this message is displayed:
The Microsoft Exchange Server Computer is not available. Either there are network problems or thhe Microsoft Exchange Server is down for mmaintenance.
Obvious problems with the SQL recognition but it seems to be up and running fine.
Any help appreciated.Make sure no change in SA's password and try connecting with other user with ADMIN privileges.
Subscribe to:
Posts (Atom)