"Ray Laubert" <ray@rsl-webhosting.com> wrote in message
news:46BC5BDF-6A4F-4817-88E1-29A8F83E4FB8@microsoft.com...
> 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:
>
>> 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