ASP Developer Network - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com

ASPDeveloper

ASPDeveloper.Net / VirtualServerFAQ.COM

Make sure you go to our home page for:

* Virtual Server 2005 FAQ
* ASP.Net 2.0 Information
* ASP.Net 2.0 Streaming Tutorials
* ASP.Net 2.0 HTML based Tutorials

Made possible by Business Internet Technology Shop (BitShop)

Virtual PC

Recent Virtual PC posts

* hardware virtualization
* Virutal PC on Vista64 with 16 bit installer apps??
* 07 MS Virtual PC-Installing on a mapped drive for multiple PC acce
* problem in connecting two virtual machines for local network only
* Vista Home Premium .. Can"t install Virtual Server.. so how do I automatically start a Virtual PC without a login?
* Change location of "My Virtual Machines"
* Differencing disks and disk space
* Cannot configure VPC instance to use/share Internet connection
* Virtual PC to SP1
* Firewall blocking internet access by guest
* VGA/Display/Resolution problems in Linux Debian 4.04 under vpc 2007
* [OT] kind of: fix frozen pointer in Knoppix 5.1 under VPC
* backing up before xp3
* Setting up internet in Windows 98
* Using swap file or not for VM
* winpe-2005 ISO
* Windows XP sp 3 crash on Dell D830 Vista x64 host system, IntelCor
* Mini newsgroup FAQ for the week of 10/12/2008
* how to create a guest virtual computer
* Problem : Reboot of Physical PC

Add Solution

Accessing SQL Server

Source: microsoft.public.virtualpc
Sent: 10/18/2008
From: Sergio Torres
Message:

I am having problems accessing SQL Server 2005 Develper in my virtual PC from
the Host.

I run a Windows Vista Ultimate 64 bits as host and created a Virtual PC with
Windows XP Pro.

I have SQL Server 2005 Developer in the virtual PC and SQL Server Express
2008 in the Host.

When I try to access SQL 2005 from the host or SQL 2008 from the VPC I get
an error message saying maybe the server is configured not to accept remote
connections.

I checked and both SQL servers are set up to accept connections from the
local area network.

Both Windows Firewalls are set to let pass SQL connections to the default
port.

I can connect from both PCs to external (WAN) SQL servers. I can transfer
files between the two computers without problem.

The VPC is using the adapter on the physical computer as networking
configuration.

Any ideas?

Thanks,

--
Sergio Torres C.
(505) 897 2041
___________________
http://www.stcsys.com
___________________

Post Reply | This is Spam! | Mark as Spam

Related Messages

Re: Accessing SQL Server

Sent: 10/19/2008
From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
Message:

Many possible problems here. First, you must check that you can ping the
guest from the host (and vice versa) to be sure that your network is OK.
Transferring files between computers is not sufficient because this job is
done by Virtual PC whitout passing by the TCP/IP network.

Second, if I remember correctly, TCP/IP addresses of type 192.168.0.1 are
*not* considered as local address by the SQL-Server. To him, this is a
remote connection so you should enable Local and remote connections from the
SQL-Server 2005 Surface Area Configuration tool | Surface Area Configuration
for Services and Connections | Database Engine | Remote Connection.

From the Server Server Configuration Manager (this is not the same tool as
the other one); you must also check that either the TCP/IP and/or the Named
Pipes protocols are enabled for both the SQL Server 2005 Network
Configuration (this is for the server side) and the SQL Native Client
Configuration (this is for the client side is you are using the native
protocol as a client).

If you are not using an alias, try addding the prefix tcp: or np: to
distinguish between the tcp/ip and the named pipes protocol. Add the name
of the library for either TCP or NP if you are using ODBC or OLEDB. In the
case of TCP/IP, you can also try adding the port ,1433 (this is the default
port, change it if necessary) after the name/address of the server.

Using an Alias can alleviate some of these problems; particularly the
distinction between tcp: and np: or the use of a dynamically allocated port.

Finally, unless you are using a domain to manage your account or that you
can authenticate yourself before trying to make a connection to the
SQL-Server, you must use a SQL-Server login account and not a Windows
account to connect to the server. Don't forget to put the Server into the
Mixed Mode (SQL-Server and Wndows Authentification mode under the Security
tab of the SSMS); otherwise, it will refuse your SQL login account. Of
course, your sql account must also be granted the right to access the
database.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)

"Sergio Torres" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

>I am having problems accessing SQL Server 2005 Develper in my virtual PC
>from
> the Host.
>
> I run a Windows Vista Ultimate 64 bits as host and created a Virtual PC
> with
> Windows XP Pro.
>
> I have SQL Server 2005 Developer in the virtual PC and SQL Server Express
> 2008 in the Host.
>
> When I try to access SQL 2005 from the host or SQL 2008 from the VPC I get
> an error message saying maybe the server is configured not to accept
> remote
> connections.
>
> I checked and both SQL servers are set up to accept connections from the
> local area network.
>
> Both Windows Firewalls are set to let pass SQL connections to the default
> port.
>
> I can connect from both PCs to external (WAN) SQL servers. I can transfer
> files between the two computers without problem.
>
> The VPC is using the adapter on the physical computer as networking
> configuration.
>
> Any ideas?
>
> Thanks,
>
> --
> Sergio Torres C.
> (505) 897 2041
> ___________________
> http://www.stcsys.com
> ___________________
>

Re: Accessing SQL Server

Sent: 10/19/2008
From: Sergio Torres
Message:

Dear Sylvain,

Thank you for your help.

Now I am able to connect adding the prefix np: to the server name in the
"Connect to Server" dialog box of SQL Server Manager Studio.

Just a note: If I select "Network Protocol" as "Named Pipes" in the
Connection Properties" tab of the "Connect to Server" Dialog box it does not
work. Isn't it the same as adding the np: prefix to the server name?

If I use the tcp: prefix the connection still does not work.

I checked and the VP was pingable.

I had to change the Remote Connection listening scope to "local and remote
connections, Using both TCP/IP and named pipes" for the server in the VPC. I
used the "Surface Area Configuration for Services and Connections" console to
to this.

Thank you again!

--
Sergio Torres C.
(505) 897 2041
___________________
http://www.stcsys.com
___________________

"Sylvain Lafontaine" wrote:

Show quoted text

> Many possible problems here. First, you must check that you can ping the
> guest from the host (and vice versa) to be sure that your network is OK.
> Transferring files between computers is not sufficient because this job is
> done by Virtual PC whitout passing by the TCP/IP network.
>
> Second, if I remember correctly, TCP/IP addresses of type 192.168.0.1 are
> *not* considered as local address by the SQL-Server. To him, this is a
> remote connection so you should enable Local and remote connections from the
> SQL-Server 2005 Surface Area Configuration tool | Surface Area Configuration
> for Services and Connections | Database Engine | Remote Connection.
>
> From the Server Server Configuration Manager (this is not the same tool as
> the other one); you must also check that either the TCP/IP and/or the Named
> Pipes protocols are enabled for both the SQL Server 2005 Network
> Configuration (this is for the server side) and the SQL Native Client
> Configuration (this is for the client side is you are using the native
> protocol as a client).
>
> If you are not using an alias, try addding the prefix tcp: or np: to
> distinguish between the tcp/ip and the named pipes protocol. Add the name
> of the library for either TCP or NP if you are using ODBC or OLEDB. In the
> case of TCP/IP, you can also try adding the port ,1433 (this is the default
> port, change it if necessary) after the name/address of the server.
>
> Using an Alias can alleviate some of these problems; particularly the
> distinction between tcp: and np: or the use of a dynamically allocated port.
>
> Finally, unless you are using a domain to manage your account or that you
> can authenticate yourself before trying to make a connection to the
> SQL-Server, you must use a SQL-Server login account and not a Windows
> account to connect to the server. Don't forget to put the Server into the
> Mixed Mode (SQL-Server and Wndows Authentification mode under the Security
> tab of the SSMS); otherwise, it will refuse your SQL login account. Of
> course, your sql account must also be granted the right to access the
> database.
>
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
>
>
> "Sergio Torres" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> >I am having problems accessing SQL Server 2005 Develper in my virtual PC
> >from
> > the Host.
> >
> > I run a Windows Vista Ultimate 64 bits as host and created a Virtual PC
> > with
> > Windows XP Pro.
> >
> > I have SQL Server 2005 Developer in the virtual PC and SQL Server Express
> > 2008 in the Host.
> >
> > When I try to access SQL 2005 from the host or SQL 2008 from the VPC I get
> > an error message saying maybe the server is configured not to accept
> > remote
> > connections.
> >
> > I checked and both SQL servers are set up to accept connections from the
> > local area network.
> >
> > Both Windows Firewalls are set to let pass SQL connections to the default
> > port.
> >
> > I can connect from both PCs to external (WAN) SQL servers. I can transfer
> > files between the two computers without problem.
> >
> > The VPC is using the adapter on the physical computer as networking
> > configuration.
> >
> > Any ideas?
> >
> > Thanks,
> >
> > --
> > Sergio Torres C.
> > (505) 897 2041
> > ___________________
> > http://www.stcsys.com
> > ___________________
> >
>
>
>

Re: Accessing SQL Server

Sent: 10/19/2008
From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
Message:

For the named protocol, I would have been under the same impression as you.
What is the exact name of the server that you are trying to use? Are you
using a Netbeui name or a tcp/ip address or something else? Is this a named
instance (with a name) or the default instance? In the case of a named
instance, you should add its name after the server address.

Also, for the TCP/IP protocol for the SQL Server machine (the server, not
the client), it's not sufficient that the TCP/IP protocol is activated, you
must also check under the IP Adress tab that the server is listening on the
tcp/ip address of the machine. If it's not the default instance, you must
also allocate a dynamic TCP Ports and/or a static port. The port 1433 will
be automatically used only in the case that this is the default instance
(ie, it's not a named instance) of the machine. This must be done on an
adress per address basis or by using the IPAll option.

For tcp/ip, try adding the port ,1433 after the address/name of the server
or try with an alias. For dynamically allocated port, make sure that the
port 1434 is allowed through the firewalls and that the SQL-Server Browser
Service is running on the server machine (important). Of course, this also
requires that some other ports are permitted on the firewall.

BTW, are you sure that you don't have any other firewall working around?

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)

"Sergio Torres" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Dear Sylvain,
>
> Thank you for your help.
>
> Now I am able to connect adding the prefix np: to the server name in the
> "Connect to Server" dialog box of SQL Server Manager Studio.
>
> Just a note: If I select "Network Protocol" as "Named Pipes" in the
> Connection Properties" tab of the "Connect to Server" Dialog box it does
> not
> work. Isn't it the same as adding the np: prefix to the server name?
>
> If I use the tcp: prefix the connection still does not work.
>
> I checked and the VP was pingable.
>
> I had to change the Remote Connection listening scope to "local and remote
> connections, Using both TCP/IP and named pipes" for the server in the VPC.
> I
> used the "Surface Area Configuration for Services and Connections" console
> to
> to this.
>
> Thank you again!
>
> --
> Sergio Torres C.
> (505) 897 2041
> ___________________
> http://www.stcsys.com
> ___________________
>
>
>
> "Sylvain Lafontaine" wrote:
>
>> Many possible problems here. First, you must check that you can ping the
>> guest from the host (and vice versa) to be sure that your network is OK.
>> Transferring files between computers is not sufficient because this job
>> is
>> done by Virtual PC whitout passing by the TCP/IP network.
>>
>> Second, if I remember correctly, TCP/IP addresses of type 192.168.0.1 are
>> *not* considered as local address by the SQL-Server. To him, this is a
>> remote connection so you should enable Local and remote connections from
>> the
>> SQL-Server 2005 Surface Area Configuration tool | Surface Area
>> Configuration
>> for Services and Connections | Database Engine | Remote Connection.
>>
>> From the Server Server Configuration Manager (this is not the same tool
>> as
>> the other one); you must also check that either the TCP/IP and/or the
>> Named
>> Pipes protocols are enabled for both the SQL Server 2005 Network
>> Configuration (this is for the server side) and the SQL Native Client
>> Configuration (this is for the client side is you are using the native
>> protocol as a client).
>>
>> If you are not using an alias, try addding the prefix tcp: or np: to
>> distinguish between the tcp/ip and the named pipes protocol. Add the
>> name
>> of the library for either TCP or NP if you are using ODBC or OLEDB. In
>> the
>> case of TCP/IP, you can also try adding the port ,1433 (this is the
>> default
>> port, change it if necessary) after the name/address of the server.
>>
>> Using an Alias can alleviate some of these problems; particularly the
>> distinction between tcp: and np: or the use of a dynamically allocated
>> port.
>>
>> Finally, unless you are using a domain to manage your account or that you
>> can authenticate yourself before trying to make a connection to the
>> SQL-Server, you must use a SQL-Server login account and not a Windows
>> account to connect to the server. Don't forget to put the Server into the
>> Mixed Mode (SQL-Server and Wndows Authentification mode under the
>> Security
>> tab of the SSMS); otherwise, it will refuse your SQL login account. Of
>> course, your sql account must also be granted the right to access the
>> database.
>>
>> --
>> Sylvain Lafontaine, ing.
>> MVP - Technologies Virtual-PC
>> E-mail: sylvain aei ca (fill the blanks, no spam please)
>>
>>
>> "Sergio Torres" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> >I am having problems accessing SQL Server 2005 Develper in my virtual PC
>> >from
>> > the Host.
>> >
>> > I run a Windows Vista Ultimate 64 bits as host and created a Virtual PC
>> > with
>> > Windows XP Pro.
>> >
>> > I have SQL Server 2005 Developer in the virtual PC and SQL Server
>> > Express
>> > 2008 in the Host.
>> >
>> > When I try to access SQL 2005 from the host or SQL 2008 from the VPC I
>> > get
>> > an error message saying maybe the server is configured not to accept
>> > remote
>> > connections.
>> >
>> > I checked and both SQL servers are set up to accept connections from
>> > the
>> > local area network.
>> >
>> > Both Windows Firewalls are set to let pass SQL connections to the
>> > default
>> > port.
>> >
>> > I can connect from both PCs to external (WAN) SQL servers. I can
>> > transfer
>> > files between the two computers without problem.
>> >
>> > The VPC is using the adapter on the physical computer as networking
>> > configuration.
>> >
>> > Any ideas?
>> >
>> > Thanks,
>> >
>> > --
>> > Sergio Torres C.
>> > (505) 897 2041
>> > ___________________
>> > http://www.stcsys.com
>> > ___________________
>> >
>>
>>
>>

Re: Accessing SQL Server

Sent: 10/29/2008
From: Sergio Torres
Message:

Sylvain,

Thank you for your help. Sorry it took me so long to answer (your email was
filtered by my mail server, I just found it).

Please see my notes:

The server name is VIRTUAL-TGM.
I use the Netbeui name but I also have tried with the ip address.
It's the default instance.
Under the IP Address tab, in the server protocols, IP1, says it is listening
on 192.168.1.61
I have dynamic ports disabled (blank)
I do have a linksys router, but I understand LAN connections are not
filtered in anyway. Just in case I enabled port range forward for
192.168.1.61, 1433, but got the same error message:

TITLE: Connect to Server
------------------------------

Cannot connect to VIRTUAL-TGM,1433.

------------------------------
ADDITIONAL INFORMATION:

A network-related or instance-specific error occurred while establishing a
connection to SQL Server. The server was not found or was not accessible.
Verify that the instance name is correct and that SQL Server is configured to
allow remote connections. (provider: TCP Provider, error: 0 - A connection
attempt failed because the connected party did not properly respond after a
period of time, or established connection failed because connected host has
failed to respond.) (Microsoft SQL Server, Error: 10060)

For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476

------------------------------
BUTTONS:

OK
------------------------------

Thank you again,

--
Sergio Torres C.
(505) 897 2041
___________________
http://www.stcsys.com
___________________

"Sylvain Lafontaine" wrote:

Show quoted text

> For the named protocol, I would have been under the same impression as you.
> What is the exact name of the server that you are trying to use? Are you
> using a Netbeui name or a tcp/ip address or something else? Is this a named
> instance (with a name) or the default instance? In the case of a named
> instance, you should add its name after the server address.
>
> Also, for the TCP/IP protocol for the SQL Server machine (the server, not
> the client), it's not sufficient that the TCP/IP protocol is activated, you
> must also check under the IP Adress tab that the server is listening on the
> tcp/ip address of the machine. If it's not the default instance, you must
> also allocate a dynamic TCP Ports and/or a static port. The port 1433 will
> be automatically used only in the case that this is the default instance
> (ie, it's not a named instance) of the machine. This must be done on an
> adress per address basis or by using the IPAll option.
>
> For tcp/ip, try adding the port ,1433 after the address/name of the server
> or try with an alias. For dynamically allocated port, make sure that the
> port 1434 is allowed through the firewalls and that the SQL-Server Browser
> Service is running on the server machine (important). Of course, this also
> requires that some other ports are permitted on the firewall.
>
> BTW, are you sure that you don't have any other firewall working around?
>
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
>
>
> "Sergio Torres" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Dear Sylvain,
> >
> > Thank you for your help.
> >
> > Now I am able to connect adding the prefix np: to the server name in the
> > "Connect to Server" dialog box of SQL Server Manager Studio.
> >
> > Just a note: If I select "Network Protocol" as "Named Pipes" in the
> > Connection Properties" tab of the "Connect to Server" Dialog box it does
> > not
> > work. Isn't it the same as adding the np: prefix to the server name?
> >
> > If I use the tcp: prefix the connection still does not work.
> >
> > I checked and the VP was pingable.
> >
> > I had to change the Remote Connection listening scope to "local and remote
> > connections, Using both TCP/IP and named pipes" for the server in the VPC.
> > I
> > used the "Surface Area Configuration for Services and Connections" console
> > to
> > to this.
> >
> > Thank you again!
> >
> > --
> > Sergio Torres C.
> > (505) 897 2041
> > ___________________
> > http://www.stcsys.com
> > ___________________
> >
> >
> >
> > "Sylvain Lafontaine" wrote:
> >
> >> Many possible problems here. First, you must check that you can ping the
> >> guest from the host (and vice versa) to be sure that your network is OK.
> >> Transferring files between computers is not sufficient because this job
> >> is
> >> done by Virtual PC whitout passing by the TCP/IP network.
> >>
> >> Second, if I remember correctly, TCP/IP addresses of type 192.168.0.1 are
> >> *not* considered as local address by the SQL-Server. To him, this is a
> >> remote connection so you should enable Local and remote connections from
> >> the
> >> SQL-Server 2005 Surface Area Configuration tool | Surface Area
> >> Configuration
> >> for Services and Connections | Database Engine | Remote Connection.
> >>
> >> From the Server Server Configuration Manager (this is not the same tool
> >> as
> >> the other one); you must also check that either the TCP/IP and/or the
> >> Named
> >> Pipes protocols are enabled for both the SQL Server 2005 Network
> >> Configuration (this is for the server side) and the SQL Native Client
> >> Configuration (this is for the client side is you are using the native
> >> protocol as a client).
> >>
> >> If you are not using an alias, try addding the prefix tcp: or np: to
> >> distinguish between the tcp/ip and the named pipes protocol. Add the
> >> name
> >> of the library for either TCP or NP if you are using ODBC or OLEDB. In
> >> the
> >> case of TCP/IP, you can also try adding the port ,1433 (this is the
> >> default
> >> port, change it if necessary) after the name/address of the server.
> >>
> >> Using an Alias can alleviate some of these problems; particularly the
> >> distinction between tcp: and np: or the use of a dynamically allocated
> >> port.
> >>
> >> Finally, unless you are using a domain to manage your account or that you
> >> can authenticate yourself before trying to make a connection to the
> >> SQL-Server, you must use a SQL-Server login account and not a Windows
> >> account to connect to the server. Don't forget to put the Server into the
> >> Mixed Mode (SQL-Server and Wndows Authentification mode under the
> >> Security
> >> tab of the SSMS); otherwise, it will refuse your SQL login account. Of
> >> course, your sql account must also be granted the right to access the
> >> database.
> >>
> >> --
> >> Sylvain Lafontaine, ing.
> >> MVP - Technologies Virtual-PC
> >> E-mail: sylvain aei ca (fill the blanks, no spam please)
> >>
> >>
> >> "Sergio Torres" <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> >I am having problems accessing SQL Server 2005 Develper in my virtual PC
> >> >from
> >> > the Host.
> >> >
> >> > I run a Windows Vista Ultimate 64 bits as host and created a Virtual PC
> >> > with
> >> > Windows XP Pro.
> >> >
> >> > I have SQL Server 2005 Developer in the virtual PC and SQL Server
> >> > Express
> >> > 2008 in the Host.
> >> >
> >> > When I try to access SQL 2005 from the host or SQL 2008 from the VPC I
> >> > get
> >> > an error message saying maybe the server is configured not to accept
> >> > remote
> >> > connections.
> >> >
> >> > I checked and both SQL servers are set up to accept connections from
> >> > the
> >> > local area network.
> >> >
> >> > Both Windows Firewalls are set to let pass SQL connections to the
> >> > default
> >> > port.
> >> >
> >> > I can connect from both PCs to external (WAN) SQL servers. I can
> >> > transfer
> >> > files between the two computers without problem.
> >> >
> >> > The VPC is using the adapter on the physical computer as networking
> >> > configuration.
> >> >
> >> > Any ideas?
> >> >
> >> > Thanks,
> >> >
> >> > --
> >> > Sergio Torres C.
> >> > (505) 897 2041
> >> > ___________________
> >> > http://www.stcsys.com
> >> > ___________________
> >> >
> >>
> >>
> >>
>
>
>

Re: Accessing SQL Server

Sent: 10/30/2008
From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
Message:

if you have disabled the dynamic ports, make sure that SQL-Server is
listening to the port 1433.In your case, if it works with np: then keep it
this way.

Also, I don't understand why you simply don't install the SQL-Server 2005
Developer Edition directly onto your host machine instead of using a virtual
machine.

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)

"Sergio Torres" <(email address - cut out)> wrote in message
news:(email address - cut out)...

Show quoted text

> Sylvain,
>
> Thank you for your help. Sorry it took me so long to answer (your email
> was
> filtered by my mail server, I just found it).
>
> Please see my notes:
>
> The server name is VIRTUAL-TGM.
> I use the Netbeui name but I also have tried with the ip address.
> It's the default instance.
> Under the IP Address tab, in the server protocols, IP1, says it is
> listening
> on 192.168.1.61
> I have dynamic ports disabled (blank)
> I do have a linksys router, but I understand LAN connections are not
> filtered in anyway. Just in case I enabled port range forward for
> 192.168.1.61, 1433, but got the same error message:
>
> TITLE: Connect to Server
> ------------------------------
>
> Cannot connect to VIRTUAL-TGM,1433.
>
> ------------------------------
> ADDITIONAL INFORMATION:
>
> A network-related or instance-specific error occurred while establishing a
> connection to SQL Server. The server was not found or was not accessible.
> Verify that the instance name is correct and that SQL Server is configured
> to
> allow remote connections. (provider: TCP Provider, error: 0 - A connection
> attempt failed because the connected party did not properly respond after
> a
> period of time, or established connection failed because connected host
> has
> failed to respond.) (Microsoft SQL Server, Error: 10060)
>
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
>
> ------------------------------
> BUTTONS:
>
> OK
> ------------------------------
>
> Thank you again,
>
> --
> Sergio Torres C.
> (505) 897 2041
> ___________________
> http://www.stcsys.com
> ___________________
>
>
>
> "Sylvain Lafontaine" wrote:
>
>> For the named protocol, I would have been under the same impression as
>> you.
>> What is the exact name of the server that you are trying to use? Are you
>> using a Netbeui name or a tcp/ip address or something else? Is this a
>> named
>> instance (with a name) or the default instance? In the case of a named
>> instance, you should add its name after the server address.
>>
>> Also, for the TCP/IP protocol for the SQL Server machine (the server, not
>> the client), it's not sufficient that the TCP/IP protocol is activated,
>> you
>> must also check under the IP Adress tab that the server is listening on
>> the
>> tcp/ip address of the machine. If it's not the default instance, you
>> must
>> also allocate a dynamic TCP Ports and/or a static port. The port 1433
>> will
>> be automatically used only in the case that this is the default instance
>> (ie, it's not a named instance) of the machine. This must be done on an
>> adress per address basis or by using the IPAll option.
>>
>> For tcp/ip, try adding the port ,1433 after the address/name of the
>> server
>> or try with an alias. For dynamically allocated port, make sure that the
>> port 1434 is allowed through the firewalls and that the SQL-Server
>> Browser
>> Service is running on the server machine (important). Of course, this
>> also
>> requires that some other ports are permitted on the firewall.
>>
>> BTW, are you sure that you don't have any other firewall working around?
>>
>> --
>> Sylvain Lafontaine, ing.
>> MVP - Technologies Virtual-PC
>> E-mail: sylvain aei ca (fill the blanks, no spam please)
>>
>>
>> "Sergio Torres" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > Dear Sylvain,
>> >
>> > Thank you for your help.
>> >
>> > Now I am able to connect adding the prefix np: to the server name in
>> > the
>> > "Connect to Server" dialog box of SQL Server Manager Studio.
>> >
>> > Just a note: If I select "Network Protocol" as "Named Pipes" in the
>> > Connection Properties" tab of the "Connect to Server" Dialog box it
>> > does
>> > not
>> > work. Isn't it the same as adding the np: prefix to the server name?
>> >
>> > If I use the tcp: prefix the connection still does not work.
>> >
>> > I checked and the VP was pingable.
>> >
>> > I had to change the Remote Connection listening scope to "local and
>> > remote
>> > connections, Using both TCP/IP and named pipes" for the server in the
>> > VPC.
>> > I
>> > used the "Surface Area Configuration for Services and Connections"
>> > console
>> > to
>> > to this.
>> >
>> > Thank you again!
>> >
>> > --
>> > Sergio Torres C.
>> > (505) 897 2041
>> > ___________________
>> > http://www.stcsys.com
>> > ___________________
>> >
>> >
>> >
>> > "Sylvain Lafontaine" wrote:
>> >
>> >> Many possible problems here. First, you must check that you can ping
>> >> the
>> >> guest from the host (and vice versa) to be sure that your network is
>> >> OK.
>> >> Transferring files between computers is not sufficient because this
>> >> job
>> >> is
>> >> done by Virtual PC whitout passing by the TCP/IP network.
>> >>
>> >> Second, if I remember correctly, TCP/IP addresses of type 192.168.0.1
>> >> are
>> >> *not* considered as local address by the SQL-Server. To him, this is
>> >> a
>> >> remote connection so you should enable Local and remote connections
>> >> from
>> >> the
>> >> SQL-Server 2005 Surface Area Configuration tool | Surface Area
>> >> Configuration
>> >> for Services and Connections | Database Engine | Remote Connection.
>> >>
>> >> From the Server Server Configuration Manager (this is not the same
>> >> tool
>> >> as
>> >> the other one); you must also check that either the TCP/IP and/or the
>> >> Named
>> >> Pipes protocols are enabled for both the SQL Server 2005 Network
>> >> Configuration (this is for the server side) and the SQL Native Client
>> >> Configuration (this is for the client side is you are using the native
>> >> protocol as a client).
>> >>
>> >> If you are not using an alias, try addding the prefix tcp: or np: to
>> >> distinguish between the tcp/ip and the named pipes protocol. Add the
>> >> name
>> >> of the library for either TCP or NP if you are using ODBC or OLEDB.
>> >> In
>> >> the
>> >> case of TCP/IP, you can also try adding the port ,1433 (this is the
>> >> default
>> >> port, change it if necessary) after the name/address of the server.
>> >>
>> >> Using an Alias can alleviate some of these problems; particularly the
>> >> distinction between tcp: and np: or the use of a dynamically allocated
>> >> port.
>> >>
>> >> Finally, unless you are using a domain to manage your account or that
>> >> you
>> >> can authenticate yourself before trying to make a connection to the
>> >> SQL-Server, you must use a SQL-Server login account and not a Windows
>> >> account to connect to the server. Don't forget to put the Server into
>> >> the
>> >> Mixed Mode (SQL-Server and Wndows Authentification mode under the
>> >> Security
>> >> tab of the SSMS); otherwise, it will refuse your SQL login account.
>> >> Of
>> >> course, your sql account must also be granted the right to access the
>> >> database.
>> >>
>> >> --
>> >> Sylvain Lafontaine, ing.
>> >> MVP - Technologies Virtual-PC
>> >> E-mail: sylvain aei ca (fill the blanks, no spam please)
>> >>
>> >>
>> >> "Sergio Torres" <(email address - cut out)> wrote in
>> >> message
>> >> news:(email address - cut out)...
>> >> >I am having problems accessing SQL Server 2005 Develper in my virtual
>> >> >PC
>> >> >from
>> >> > the Host.
>> >> >
>> >> > I run a Windows Vista Ultimate 64 bits as host and created a Virtual
>> >> > PC
>> >> > with
>> >> > Windows XP Pro.
>> >> >
>> >> > I have SQL Server 2005 Developer in the virtual PC and SQL Server
>> >> > Express
>> >> > 2008 in the Host.
>> >> >
>> >> > When I try to access SQL 2005 from the host or SQL 2008 from the VPC
>> >> > I
>> >> > get
>> >> > an error message saying maybe the server is configured not to accept
>> >> > remote
>> >> > connections.
>> >> >
>> >> > I checked and both SQL servers are set up to accept connections from
>> >> > the
>> >> > local area network.
>> >> >
>> >> > Both Windows Firewalls are set to let pass SQL connections to the
>> >> > default
>> >> > port.
>> >> >
>> >> > I can connect from both PCs to external (WAN) SQL servers. I can
>> >> > transfer
>> >> > files between the two computers without problem.
>> >> >
>> >> > The VPC is using the adapter on the physical computer as networking
>> >> > configuration.
>> >> >
>> >> > Any ideas?
>> >> >
>> >> > Thanks,
>> >> >
>> >> > --
>> >> > Sergio Torres C.
>> >> > (505) 897 2041
>> >> > ___________________
>> >> > http://www.stcsys.com
>> >> > ___________________
>> >> >
>> >>
>> >>
>> >>
>>
>>
>>

Re: Accessing SQL Server

Sent: 10/30/2008
From: "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
Message:

Also, are you sure that this is the default instance and not a named
instance? For some more information, you can also take a look at the
following article:

http://msdn.microsoft.com/en-us/library/ms181087.aspx

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)

"Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
wrote in message news:(email address - cut out)...

Show quoted text

> if you have disabled the dynamic ports, make sure that SQL-Server is
> listening to the port 1433.In your case, if it works with np: then keep it
> this way.
>
> Also, I don't understand why you simply don't install the SQL-Server 2005
> Developer Edition directly onto your host machine instead of using a
> virtual machine.
>
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
>
>
> "Sergio Torres" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> Sylvain,
>>
>> Thank you for your help. Sorry it took me so long to answer (your email
>> was
>> filtered by my mail server, I just found it).
>>
>> Please see my notes:
>>
>> The server name is VIRTUAL-TGM.
>> I use the Netbeui name but I also have tried with the ip address.
>> It's the default instance.
>> Under the IP Address tab, in the server protocols, IP1, says it is
>> listening
>> on 192.168.1.61
>> I have dynamic ports disabled (blank)
>> I do have a linksys router, but I understand LAN connections are not
>> filtered in anyway. Just in case I enabled port range forward for
>> 192.168.1.61, 1433, but got the same error message:
>>
>> TITLE: Connect to Server
>> ------------------------------
>>
>> Cannot connect to VIRTUAL-TGM,1433.
>>
>> ------------------------------
>> ADDITIONAL INFORMATION:
>>
>> A network-related or instance-specific error occurred while establishing
>> a
>> connection to SQL Server. The server was not found or was not accessible.
>> Verify that the instance name is correct and that SQL Server is
>> configured to
>> allow remote connections. (provider: TCP Provider, error: 0 - A
>> connection
>> attempt failed because the connected party did not properly respond after
>> a
>> period of time, or established connection failed because connected host
>> has
>> failed to respond.) (Microsoft SQL Server, Error: 10060)
>>
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
>>
>> ------------------------------
>> BUTTONS:
>>
>> OK
>> ------------------------------
>>
>> Thank you again,
>>
>> --
>> Sergio Torres C.
>> (505) 897 2041
>> ___________________
>> http://www.stcsys.com
>> ___________________
>>
>>
>>
>> "Sylvain Lafontaine" wrote:
>>
>>> For the named protocol, I would have been under the same impression as
>>> you.
>>> What is the exact name of the server that you are trying to use? Are
>>> you
>>> using a Netbeui name or a tcp/ip address or something else? Is this a
>>> named
>>> instance (with a name) or the default instance? In the case of a named
>>> instance, you should add its name after the server address.
>>>
>>> Also, for the TCP/IP protocol for the SQL Server machine (the server,
>>> not
>>> the client), it's not sufficient that the TCP/IP protocol is activated,
>>> you
>>> must also check under the IP Adress tab that the server is listening on
>>> the
>>> tcp/ip address of the machine. If it's not the default instance, you
>>> must
>>> also allocate a dynamic TCP Ports and/or a static port. The port 1433
>>> will
>>> be automatically used only in the case that this is the default instance
>>> (ie, it's not a named instance) of the machine. This must be done on an
>>> adress per address basis or by using the IPAll option.
>>>
>>> For tcp/ip, try adding the port ,1433 after the address/name of the
>>> server
>>> or try with an alias. For dynamically allocated port, make sure that
>>> the
>>> port 1434 is allowed through the firewalls and that the SQL-Server
>>> Browser
>>> Service is running on the server machine (important). Of course, this
>>> also
>>> requires that some other ports are permitted on the firewall.
>>>
>>> BTW, are you sure that you don't have any other firewall working around?
>>>
>>> --
>>> Sylvain Lafontaine, ing.
>>> MVP - Technologies Virtual-PC
>>> E-mail: sylvain aei ca (fill the blanks, no spam please)
>>>
>>>
>>> "Sergio Torres" <(email address - cut out)> wrote in
>>> message
>>> news:(email address - cut out)...
>>> > Dear Sylvain,
>>> >
>>> > Thank you for your help.
>>> >
>>> > Now I am able to connect adding the prefix np: to the server name in
>>> > the
>>> > "Connect to Server" dialog box of SQL Server Manager Studio.
>>> >
>>> > Just a note: If I select "Network Protocol" as "Named Pipes" in the
>>> > Connection Properties" tab of the "Connect to Server" Dialog box it
>>> > does
>>> > not
>>> > work. Isn't it the same as adding the np: prefix to the server name?
>>> >
>>> > If I use the tcp: prefix the connection still does not work.
>>> >
>>> > I checked and the VP was pingable.
>>> >
>>> > I had to change the Remote Connection listening scope to "local and
>>> > remote
>>> > connections, Using both TCP/IP and named pipes" for the server in the
>>> > VPC.
>>> > I
>>> > used the "Surface Area Configuration for Services and Connections"
>>> > console
>>> > to
>>> > to this.
>>> >
>>> > Thank you again!
>>> >
>>> > --
>>> > Sergio Torres C.
>>> > (505) 897 2041
>>> > ___________________
>>> > http://www.stcsys.com
>>> > ___________________
>>> >
>>> >
>>> >
>>> > "Sylvain Lafontaine" wrote:
>>> >
>>> >> Many possible problems here. First, you must check that you can ping
>>> >> the
>>> >> guest from the host (and vice versa) to be sure that your network is
>>> >> OK.
>>> >> Transferring files between computers is not sufficient because this
>>> >> job
>>> >> is
>>> >> done by Virtual PC whitout passing by the TCP/IP network.
>>> >>
>>> >> Second, if I remember correctly, TCP/IP addresses of type 192.168.0.1
>>> >> are
>>> >> *not* considered as local address by the SQL-Server. To him, this is
>>> >> a
>>> >> remote connection so you should enable Local and remote connections
>>> >> from
>>> >> the
>>> >> SQL-Server 2005 Surface Area Configuration tool | Surface Area
>>> >> Configuration
>>> >> for Services and Connections | Database Engine | Remote Connection.
>>> >>
>>> >> From the Server Server Configuration Manager (this is not the same
>>> >> tool
>>> >> as
>>> >> the other one); you must also check that either the TCP/IP and/or the
>>> >> Named
>>> >> Pipes protocols are enabled for both the SQL Server 2005 Network
>>> >> Configuration (this is for the server side) and the SQL Native Client
>>> >> Configuration (this is for the client side is you are using the
>>> >> native
>>> >> protocol as a client).
>>> >>
>>> >> If you are not using an alias, try addding the prefix tcp: or np: to
>>> >> distinguish between the tcp/ip and the named pipes protocol. Add the
>>> >> name
>>> >> of the library for either TCP or NP if you are using ODBC or OLEDB.
>>> >> In
>>> >> the
>>> >> case of TCP/IP, you can also try adding the port ,1433 (this is the
>>> >> default
>>> >> port, change it if necessary) after the name/address of the server.
>>> >>
>>> >> Using an Alias can alleviate some of these problems; particularly the
>>> >> distinction between tcp: and np: or the use of a dynamically
>>> >> allocated
>>> >> port.
>>> >>
>>> >> Finally, unless you are using a domain to manage your account or that
>>> >> you
>>> >> can authenticate yourself before trying to make a connection to the
>>> >> SQL-Server, you must use a SQL-Server login account and not a Windows
>>> >> account to connect to the server. Don't forget to put the Server into
>>> >> the
>>> >> Mixed Mode (SQL-Server and Wndows Authentification mode under the
>>> >> Security
>>> >> tab of the SSMS); otherwise, it will refuse your SQL login account.
>>> >> Of
>>> >> course, your sql account must also be granted the right to access the
>>> >> database.
>>> >>
>>> >> --
>>> >> Sylvain Lafontaine, ing.
>>> >> MVP - Technologies Virtual-PC
>>> >> E-mail: sylvain aei ca (fill the blanks, no spam please)
>>> >>
>>> >>
>>> >> "Sergio Torres" <(email address - cut out)> wrote in
>>> >> message
>>> >> news:(email address - cut out)...
>>> >> >I am having problems accessing SQL Server 2005 Develper in my
>>> >> >virtual PC
>>> >> >from
>>> >> > the Host.
>>> >> >
>>> >> > I run a Windows Vista Ultimate 64 bits as host and created a
>>> >> > Virtual PC
>>> >> > with
>>> >> > Windows XP Pro.
>>> >> >
>>> >> > I have SQL Server 2005 Developer in the virtual PC and SQL Server
>>> >> > Express
>>> >> > 2008 in the Host.
>>> >> >
>>> >> > When I try to access SQL 2005 from the host or SQL 2008 from the
>>> >> > VPC I
>>> >> > get
>>> >> > an error message saying maybe the server is configured not to
>>> >> > accept
>>> >> > remote
>>> >> > connections.
>>> >> >
>>> >> > I checked and both SQL servers are set up to accept connections
>>> >> > from
>>> >> > the
>>> >> > local area network.
>>> >> >
>>> >> > Both Windows Firewalls are set to let pass SQL connections to the
>>> >> > default
>>> >> > port.
>>> >> >
>>> >> > I can connect from both PCs to external (WAN) SQL servers. I can
>>> >> > transfer
>>> >> > files between the two computers without problem.
>>> >> >
>>> >> > The VPC is using the adapter on the physical computer as networking
>>> >> > configuration.
>>> >> >
>>> >> > Any ideas?
>>> >> >
>>> >> > Thanks,
>>> >> >
>>> >> > --
>>> >> > Sergio Torres C.
>>> >> > (505) 897 2041
>>> >> > ___________________
>>> >> > http://www.stcsys.com
>>> >> > ___________________
>>> >> >
>>> >>
>>> >>
>>> >>
>>>
>>>
>>>
>
>

Re: Accessing SQL Server

Sent: 10/30/2008
From: Sergio Torres
Message:

Sylvain,

Thank you for your help. I'll check the link you provided me.

--
Sergio Torres C.
(505) 897 2041
___________________
http://www.stcsys.com
___________________

"Sylvain Lafontaine" wrote:

Show quoted text

> Also, are you sure that this is the default instance and not a named
> instance? For some more information, you can also take a look at the
> following article:
>
> http://msdn.microsoft.com/en-us/library/ms181087.aspx
>
> --
> Sylvain Lafontaine, ing.
> MVP - Technologies Virtual-PC
> E-mail: sylvain aei ca (fill the blanks, no spam please)
>
>
> "Sylvain Lafontaine" <sylvain aei ca (fill the blanks, no spam please)>
> wrote in message news:(email address - cut out)...
> > if you have disabled the dynamic ports, make sure that SQL-Server is
> > listening to the port 1433.In your case, if it works with np: then keep it
> > this way.
> >
> > Also, I don't understand why you simply don't install the SQL-Server 2005
> > Developer Edition directly onto your host machine instead of using a
> > virtual machine.
> >
> > --
> > Sylvain Lafontaine, ing.
> > MVP - Technologies Virtual-PC
> > E-mail: sylvain aei ca (fill the blanks, no spam please)
> >
> >
> > "Sergio Torres" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> >> Sylvain,
> >>
> >> Thank you for your help. Sorry it took me so long to answer (your email
> >> was
> >> filtered by my mail server, I just found it).
> >>
> >> Please see my notes:
> >>
> >> The server name is VIRTUAL-TGM.
> >> I use the Netbeui name but I also have tried with the ip address.
> >> It's the default instance.
> >> Under the IP Address tab, in the server protocols, IP1, says it is
> >> listening
> >> on 192.168.1.61
> >> I have dynamic ports disabled (blank)
> >> I do have a linksys router, but I understand LAN connections are not
> >> filtered in anyway. Just in case I enabled port range forward for
> >> 192.168.1.61, 1433, but got the same error message:
> >>
> >> TITLE: Connect to Server
> >> ------------------------------
> >>
> >> Cannot connect to VIRTUAL-TGM,1433.
> >>
> >> ------------------------------
> >> ADDITIONAL INFORMATION:
> >>
> >> A network-related or instance-specific error occurred while establishing
> >> a
> >> connection to SQL Server. The server was not found or was not accessible.
> >> Verify that the instance name is correct and that SQL Server is
> >> configured to
> >> allow remote connections. (provider: TCP Provider, error: 0 - A
> >> connection
> >> attempt failed because the connected party did not properly respond after
> >> a
> >> period of time, or established connection failed because connected host
> >> has
> >> failed to respond.) (Microsoft SQL Server, Error: 10060)
> >>
> >> For help, click:
> >> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
> >>
> >> ------------------------------
> >> BUTTONS:
> >>
> >> OK
> >> ------------------------------
> >>
> >> Thank you again,
> >>
> >> --
> >> Sergio Torres C.
> >> (505) 897 2041
> >> ___________________
> >> http://www.stcsys.com
> >> ___________________
> >>
> >>
> >>
> >> "Sylvain Lafontaine" wrote:
> >>
> >>> For the named protocol, I would have been under the same impression as
> >>> you.
> >>> What is the exact name of the server that you are trying to use? Are
> >>> you
> >>> using a Netbeui name or a tcp/ip address or something else? Is this a
> >>> named
> >>> instance (with a name) or the default instance? In the case of a named
> >>> instance, you should add its name after the server address.
> >>>
> >>> Also, for the TCP/IP protocol for the SQL Server machine (the server,
> >>> not
> >>> the client), it's not sufficient that the TCP/IP protocol is activated,
> >>> you
> >>> must also check under the IP Adress tab that the server is listening on
> >>> the
> >>> tcp/ip address of the machine. If it's not the default instance, you
> >>> must
> >>> also allocate a dynamic TCP Ports and/or a static port. The port 1433
> >>> will
> >>> be automatically used only in the case that this is the default instance
> >>> (ie, it's not a named instance) of the machine. This must be done on an
> >>> adress per address basis or by using the IPAll option.
> >>>
> >>> For tcp/ip, try adding the port ,1433 after the address/name of the
> >>> server
> >>> or try with an alias. For dynamically allocated port, make sure that
> >>> the
> >>> port 1434 is allowed through the firewalls and that the SQL-Server
> >>> Browser
> >>> Service is running on the server machine (important). Of course, this
> >>> also
> >>> requires that some other ports are permitted on the firewall.
> >>>
> >>> BTW, are you sure that you don't have any other firewall working around?
> >>>
> >>> --
> >>> Sylvain Lafontaine, ing.
> >>> MVP - Technologies Virtual-PC
> >>> E-mail: sylvain aei ca (fill the blanks, no spam please)
> >>>
> >>>
> >>> "Sergio Torres" <(email address - cut out)> wrote in
> >>> message
> >>> news:(email address - cut out)...
> >>> > Dear Sylvain,
> >>> >
> >>> > Thank you for your help.
> >>> >
> >>> > Now I am able to connect adding the prefix np: to the server name in
> >>> > the
> >>> > "Connect to Server" dialog box of SQL Server Manager Studio.
> >>> >
> >>> > Just a note: If I select "Network Protocol" as "Named Pipes" in the
> >>> > Connection Properties" tab of the "Connect to Server" Dialog box it
> >>> > does
> >>> > not
> >>> > work. Isn't it the same as adding the np: prefix to the server name?
> >>> >
> >>> > If I use the tcp: prefix the connection still does not work.
> >>> >
> >>> > I checked and the VP was pingable.
> >>> >
> >>> > I had to change the Remote Connection listening scope to "local and
> >>> > remote
> >>> > connections, Using both TCP/IP and named pipes" for the server in the
> >>> > VPC.
> >>> > I
> >>> > used the "Surface Area Configuration for Services and Connections"
> >>> > console
> >>> > to
> >>> > to this.
> >>> >
> >>> > Thank you again!
> >>> >
> >>> > --
> >>> > Sergio Torres C.
> >>> > (505) 897 2041
> >>> > ___________________
> >>> > http://www.stcsys.com
> >>> > ___________________
> >>> >
> >>> >
> >>> >
> >>> > "Sylvain Lafontaine" wrote:
> >>> >
> >>> >> Many possible problems here. First, you must check that you can ping
> >>> >> the
> >>> >> guest from the host (and vice versa) to be sure that your network is
> >>> >> OK.
> >>> >> Transferring files between computers is not sufficient because this
> >>> >> job
> >>> >> is
> >>> >> done by Virtual PC whitout passing by the TCP/IP network.
> >>> >>
> >>> >> Second, if I remember correctly, TCP/IP addresses of type 192.168.0.1
> >>> >> are
> >>> >> *not* considered as local address by the SQL-Server. To him, this is
> >>> >> a
> >>> >> remote connection so you should enable Local and remote connections
> >>> >> from
> >>> >> the
> >>> >> SQL-Server 2005 Surface Area Configuration tool | Surface Area
> >>> >> Configuration
> >>> >> for Services and Connections | Database Engine | Remote Connection.
> >>> >>
> >>> >> From the Server Server Configuration Manager (this is not the same
> >>> >> tool
> >>> >> as
> >>> >> the other one); you must also check that either the TCP/IP and/or the
> >>> >> Named
> >>> >> Pipes protocols are enabled for both the SQL Server 2005 Network
> >>> >> Configuration (this is for the server side) and the SQL Native Client
> >>> >> Configuration (this is for the client side is you are using the
> >>> >> native
> >>> >> protocol as a client).
> >>> >>
> >>> >> If you are not using an alias, try addding the prefix tcp: or np: to
> >>> >> distinguish between the tcp/ip and the named pipes protocol. Add the
> >>> >> name
> >>> >> of the library for either TCP or NP if you are using ODBC or OLEDB.
> >>> >> In
> >>> >> the
> >>> >> case of TCP/IP, you can also try adding the port ,1433 (this is the
> >>> >> default
> >>> >> port, change it if necessary) after the name/address of the server.
> >>> >>
> >>> >> Using an Alias can alleviate some of these problems; particularly the
> >>> >> distinction between tcp: and np: or the use of a dynamically
> >>> >> allocated
> >>> >> port.
> >>> >>
> >>> >> Finally, unless you are using a domain to manage your account or that
> >>> >> you
> >>> >> can authenticate yourself before trying to make a connection to the
> >>> >> SQL-Server, you must use a SQL-Server login account and not a Windows
> >>> >> account to connect to the server. Don't forget to put the Server into
> >>> >> the
> >>> >> Mixed Mode (SQL-Server and Wndows Authentification mode under the
> >>> >> Security
> >>> >> tab of the SSMS); otherwise, it will refuse your SQL login account.
> >>> >> Of
> >>> >> course, your sql account must also be granted the right to access the
> >>> >> database.
> >>> >>
> >>> >> --
> >>> >> Sylvain Lafontaine, ing.
> >>> >> MVP - Technologies Virtual-PC
> >>> >> E-mail: sylvain aei ca (fill the blanks, no spam please)
> >>> >>
> >>> >>
> >>> >> "Sergio Torres" <(email address - cut out)> wrote in
> >>> >> message
> >>> >> news:(email address - cut out)...
> >>> >> >I am having problems accessing SQL Server 2005 Develper in my
> >>> >> >virtual PC
> >>> >> >from
> >>> >> > the Host.
> >>> >> >
> >>> >> > I run a Windows Vista Ultimate 64 bits as host and created a
> >>> >> > Virtual PC
> >>> >> > with
> >>> >> > Windows XP Pro.
> >>> >> >
> >>> >> > I have SQL Server 2005 Developer in the virtual PC and SQL Server
> >>> >> > Express
> >>> >> > 2008 in the Host.
> >>> >> >
> >>> >> > When I try to access SQL 2005 from the host or SQL 2008 from the
> >>> >> > VPC I
> >>> >> > get
> >>> >> > an error message saying maybe the server is configured not to
> >>> >> > accept
> >>> >> > remote
> >>> >> > connections.
> >>> >> >
> >>> >> > I checked and both SQL servers are set up to accept connections
> >>> >> > from
> >>> >> > the
> >>> >> > local area network.
> >>> >> >
> >>> >> > Both Windows Firewalls are set to let pass SQL connections to the
> >>> >> > default
> >>> >> > port.
> >>> >> >
> >>> >> > I can connect from both PCs to external (WAN) SQL servers. I can
> >>> >> > transfer
> >>> >> > files between the two computers without problem.
> >>> >> >
> >>> >> > The VPC is using the adapter on the physical computer as networking
> >>> >> > configuration.
> >>> >> >
> >>> >> > Any ideas?
> >>> >> >
> >>> >> > Thanks,
> >>> >> >
> >>> >> > --
> >>> >> > Sergio Torres C.
> >>> >> > (505) 897 2041
> >>> >> > ___________________
> >>> >> > http://www.stcsys.com
> >>> >> > ___________________
> >>> >> >
> >>> >>
> >>> >>
> >>> >>
> >>>
> >>>
> >>>

Post Reply | This is Spam! | Mark as Spam

Other groups

Virtual PC (Mac)(3592)	Virtual PC(12844)	Virtual PC (French)(496)
Virtual Server 2005(6245)

Our Sponsors

Virtual Server 2005 Info Here!
http://www.aspdeveloper.net

Wiki

Blogs

Articles

Image galleries

File galleries

Forums

Maps

Directories

ASP Developer Network (since 1996) - Brought to you by Steve Radich and BitShop, Inc. - http://www.bitshop.com
Copyright © 1997-2005 by BitShop, Inc. All Rights Reserved.
No content may be reproduced in any form without written permission from BitShop, Inc.
We will be honored to assist with reproduction rights on our material if you contact us.
We also can provide print articles for your magazine, private training seminars at your site, and conference presentations.
Thank you for visiting. Please bookmark our site if you found it useful!
If you wish to make a donation it will help further the development of these free resources: