>I've been developing an application, and part of this application involves a
>service running on another machine. In my current testing environment, I
>intend to run this service on Windows Server 2008, but running it on Virtual
>PC. The other parts of the application will run on my host and call the
>service over a network. However, I cannot get my host PC to notice the
>Virtual Server, despite the VPC noticing both my host and the internet.
>
>I tried also running a winXP VPC to fulfill this task, and it didn't
>recognize the server either.
>
>
>I tried running the program anyway, providing the IP of the server according
>to its own IPconfig, though obviously this didn't work.
>
>For the server VPC, its network settings were initially just one network
>adaptor; 1 for the nForce networking controller which is plugged into my
>router. When I ran into this problem I tried expanding it to 3, which added
>the 'Shared networking (NAT)' option, as well as the other nForce networking
>controller which is plugged into nothing (don't ask, I just wanted it to
>notice all my network adaptors in the off chance it would help).
>
>
>Thanks for the help. I wasn't sure which forum to post this in, but this
>appeared to be the best match. Sorry if its a mismatch.

> On Thu, 12 Feb 2009 22:15:00 -0800, slotkowski
> <(email address - cut out)> wrote:
>
> >I've been developing an application, and part of this application involves a
> >service running on another machine. In my current testing environment, I
> >intend to run this service on Windows Server 2008, but running it on Virtual
> >PC. The other parts of the application will run on my host and call the
> >service over a network. However, I cannot get my host PC to notice the
> >Virtual Server, despite the VPC noticing both my host and the internet.
> >
> >I tried also running a winXP VPC to fulfill this task, and it didn't
> >recognize the server either.
> >
> >
> >I tried running the program anyway, providing the IP of the server according
> >to its own IPconfig, though obviously this didn't work.
> >
> >For the server VPC, its network settings were initially just one network
> >adaptor; 1 for the nForce networking controller which is plugged into my
> >router. When I ran into this problem I tried expanding it to 3, which added
> >the 'Shared networking (NAT)' option, as well as the other nForce networking
> >controller which is plugged into nothing (don't ask, I just wanted it to
> >notice all my network adaptors in the off chance it would help).
> >
> >
> >Thanks for the help. I wasn't sure which forum to post this in, but this
> >appeared to be the best match. Sorry if its a mismatch.
>
> In a situation like this it is almost 100% sure it is the Windows
> Firewall on one or both of your PC:s that is blocking the service. You
> have to open up the port you are using through the firewall.
>
> --
>
> Bo Berglund (Sweden)
>

>
>
>"Bo Berglund" wrote:
>
>> On Thu, 12 Feb 2009 22:15:00 -0800, slotkowski
>> <(email address - cut out)> wrote:
>>
>> >I've been developing an application, and part of this application involves a
>> >service running on another machine. In my current testing environment, I
>> >intend to run this service on Windows Server 2008, but running it on Virtual
>> >PC. The other parts of the application will run on my host and call the
>> >service over a network. However, I cannot get my host PC to notice the
>> >Virtual Server, despite the VPC noticing both my host and the internet.
>> >
>> >I tried also running a winXP VPC to fulfill this task, and it didn't
>> >recognize the server either.
>> >
>> >
>> >I tried running the program anyway, providing the IP of the server according
>> >to its own IPconfig, though obviously this didn't work.
>> >
>> >For the server VPC, its network settings were initially just one network
>> >adaptor; 1 for the nForce networking controller which is plugged into my
>> >router. When I ran into this problem I tried expanding it to 3, which added
>> >the 'Shared networking (NAT)' option, as well as the other nForce networking
>> >controller which is plugged into nothing (don't ask, I just wanted it to
>> >notice all my network adaptors in the off chance it would help).
>> >
>> >
>> >Thanks for the help. I wasn't sure which forum to post this in, but this
>> >appeared to be the best match. Sorry if its a mismatch.
>>
>> In a situation like this it is almost 100% sure it is the Windows
>> Firewall on one or both of your PC:s that is blocking the service. You
>> have to open up the port you are using through the firewall.
>>
>> --
>>
>> Bo Berglund (Sweden)
>>
>
>I tried disabling my firewall outright on both ends for a moment, and that
>didn't work. The host and guest still failed to recognize each other.