Two instances of SQL Server 2005 cannot "see" each other. One is Developer
edition and one is Standard edition. Standard editon is running under
Virtual PC. I would appreciate any suggestions on how make these two
instances visible to each other.
Thanks,
KeithThis should work pretty much like connecting any other two computers.
1) Can each computer ping the other successfully using TCP/IP? If not, it's
a virtual server problem.
2) Is the firewall on each computer configured to allow access through TCP
port 1433 (if you are using the default settings for a default instance)? If
not, change the firewall settings.
3) Is each SQL Server accepting TCP/IP connections? Check using the SQL
Server Surface Area Configuration tool.
4) If you are not using the default TCP port or if you installed a named
instance is the SQL Server Browser service running on each computer/virtual
machine to resolve the instance name to the port number? If not, start the
SQL Server Browser service.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"keith" <kbrickey@.dslextreme.com> wrote in message
news:%23QcBFI0SHHA.3428@.TK2MSFTNGP04.phx.gbl...
> Two instances of SQL Server 2005 cannot "see" each other. One is Developer
> edition and one is Standard edition. Standard editon is running under
> Virtual PC. I would appreciate any suggestions on how make these two
> instances visible to each other.
> Thanks,
> Keith
>|||Hi,
in addition you will have to make sure that you configured your firewall to
let the Virtual PC access your host PC. it sometimes saw this, that although
ICMP was working the host refused to establish connections to the VPC if
they used Shared networking and not NAT.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
--
"Rick Byham, (MSFT)" <rickbyh@.REDMOND.CORP.MICROSOFT.COM> wrote in message
news:F0034F02-B236-4402-9180-7817FA21CB9F@.microsoft.com...
> This should work pretty much like connecting any other two computers.
> 1) Can each computer ping the other successfully using TCP/IP? If not,
> it's a virtual server problem.
> 2) Is the firewall on each computer configured to allow access through TCP
> port 1433 (if you are using the default settings for a default instance)?
> If not, change the firewall settings.
> 3) Is each SQL Server accepting TCP/IP connections? Check using the SQL
> Server Surface Area Configuration tool.
> 4) If you are not using the default TCP port or if you installed a named
> instance is the SQL Server Browser service running on each
> computer/virtual machine to resolve the instance name to the port number?
> If not, start the SQL Server Browser service.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "keith" <kbrickey@.dslextreme.com> wrote in message
> news:%23QcBFI0SHHA.3428@.TK2MSFTNGP04.phx.gbl...
>
