Re: Surface area configuration connection issue

Tech-Archive recommends: Speed Up your PC by fixing your registry

Yes, you would. IIRC there is an ODBC-based connection diagnostic that might
help, but given what we've seen I would suspect that the ports/protocols are
still not properly configured/exposed. See the surface area config tool.

--
____________________________________
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)
-----------------------------------------------------------------------------------------------------------------------

"Sun" <Sun@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4E4B2AFE-0757-4500-B88A-E1B27333E159@xxxxxxxxxxxxxxxx
If that was the case, wouldn't I get an error connecting to the database
engine itself. That works fine. Also I am able to ping the server from my
command prompt.

Sun.

"William (Bill) Vaughn" wrote:

I'm not an expert DBA/system admin either--I need help from time-to-time
as
well. As I understand it, there situations where the Directory Name
Service
is incorrectly configured or not running. This service takes the server
name
"MyDomain\MyComputer" and determines "where" it is. It returns a TCP/IP
address like 192.168.248.22. If this is not working correctly, the
connection mechanism within ADO can't find the server or the port that
it's
listening on. The SQL Browser service broadcasts the address of all SQL
Server instances running on the server so when asked the client can be
given
the right location and port.

hth

--
____________________________________
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)
-----------------------------------------------------------------------------------------------------------------------

"Sun" <Sun@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0C25AA32-6201-4971-A1B7-3A04D495C65C@xxxxxxxxxxxxxxxx
I am sorry Bill, I did not understand. I am neither a DBA nor a network
person :-( could you please explain me further.

Thanks,
Sunanda.

"William (Bill) Vaughn" wrote:

Perhaps a DNS issue. If the NetServeEnum is not returning names, they
might
not be visible.

--
____________________________________
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)
-----------------------------------------------------------------------------------------------------------------------

"William (Bill) Vaughn" <billvaRemoveThis@xxxxxxxxx> wrote in message
news:uz9YYI%23aHHA.4000@xxxxxxxxxxxxxxxxxxxxxxx
Try disabling the firewall on the client and server. It could be
that
access to the ports is blocked.

--
____________________________________
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)
-----------------------------------------------------------------------------------------------------------------------

"Sun" <Sun@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8D9C9674-90EC-44CD-8C7F-ABB26B798A29@xxxxxxxxxxxxxxxx
Yes it is. I have tried restarting all the services, but no good.

"William (Bill) Vaughn" wrote:

Is the SQL Browser service running?

--
____________________________________
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)
-----------------------------------------------------------------------------------------------------------------------

"Sun" <Sun@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9AEA4089-FD94-4A30-B205-E65698D9BEE3@xxxxxxxxxxxxxxxx
Hi,

I have Sql Server 2005 Std edition installed on a Windows 2003
server
and
the client components installed on my machine with Win XP.

The Surface area configuration was configured on the server to
allow
TCP/IP
and named pipes.

My network login has been added to a group that has been given
the
necessary
permissions to MSTDServer through WMI.

There is no firewall running on the server.

When I launch the surface area configuration manager on my
machine
and
try
to change the computer to the server, I get the following error
message.

TITLE: Select Computer
------------------------------

Computer <...>does not exist on the network, or the computer
cannot
be
configured remotely. Verify that the remote computer has the
required
Windows
Management Instrumentation components and then try again.


How do I resolve this?

Issue 2:
This could be connected to the previous issue. I am not able to
connect to
Integration Services/Reporting Services through the Sql Server
Management
studio. I am able to connect to the Database Engine and the
Analysis
Services.

Please help me resolve these issues.

Thanks,
Sunanda.
















.

Relevant Pages