Hi Michael,
I tried the "local" suggestion and unfortunately it
doesn't work. In Visual Studio 03 I tried invoking the
dataadapter wizard and setting up a connection and I got
this error message:
"[DBNETLIB][ConnectionOpen(connect().]
SqlServer does not exist or access denied""
I reset SQL Server and tried it with and without a
password. I also tried integrated security with no
avail.
When I am in VS 03 and open the server explorer I get the
following Server Explorer Error dialog box:
"Server Explorer is unable to perform this operation. See
below for details"
The message is :
"The requested name is valid but no data of the requested
type was found"
I don't think it's a DNS problem because I can type an
address in my browser using localhost and it finds it
"http://Localhost/test.html" - That works, so it does
resolve localhost.
I have local aspx applications that use localhost SQL
Server data access and they all fail.
When I open Enterprise Mangager I can access my localhost
just fine (inside Enterprise Manager).
This was not a problem prior to upating from 2000 Server
and VS Studio 1.0
Thank you again, I really appreciate your research and
efforts, Mike
[quoted text, click to view] >-----Original Message-----
>Hi Michael,
>
>Thanks for your post. As I understand, when you unplug
the laptop from the
>network you get a connection error message and a big red
X under the server
>node in the Server Explorer when you try to open it. In
addition, you
>cannot access your localhost. If I have misunderstood,
please feel free to
>let me know.
>
>Based on my research, when you unplug the laptop form
the network, the
>network connection is broken. Of course, you cannot
connect to the other
>servers. As the connection problem with the local
machine, it is most
>probable that the server name used in the connection of
server node cannot
>be translated to an IP address by the DNS server
(because the network
>connection is broken) and then the local machine cannot
be found. As a
>workaround, I would like you to try to create a Data
Connection with
>"(local)" as the server name to connect to the local
server.
>
>Does it solve your problem? If not, I would like you to
provide me with the
>detailed message so that I can narrow down the cause of
this issue.
>
>Thanks for using MSDN newsgroup.
>
>Regards,
>
>Michael Shao
>Microsoft Online Partner Support
>Get Secure! -
www.microsoft.com/security >This posting is provided "as is" with no warranties and
confers no rights.
>
>.
