As Mathieu said, you cannot ping from one IP subnet to another without
an IP router.
You actually have more problems here than you have yet discovered.
Setting up a domain is not a trivial thing an it can cause unexpected things
to happen.
I would recommend that you put your domain controller on the internal
virtual network which virtual server has. You will not be able to connect to
the physical network from there, and that is a good thing! To test that your
domain works properly, set up another virtual machine with a client OS and
link it to the internal network as well.
The safest way to give you virtual network access to the physical
network is to run a virtual machine as a NAT router between the virtual and
physical networks.
"Mathieu CHATEAU" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> hello,
>
> they have to be on the same subnet.
> but your virtual server in 192.X.X.X too
>
> This is routing/network related, not domain/workgroup related
>
> --
> Cordialement,
> Mathieu CHATEAU
> http://lordoftheping.blogspot.com
>
>
> "ianwr" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) oups.com...
>> Hi,
>>
>> Sorry if this is a very easy question, i'm not too hot on networking
>> and have been playing around with Virtual Server. The problem i have
>> is that i have a home network on a 192.x.x.x workgroup and this is
>> where my router is attached.
>>
>> I have setup a virtual server domain unfer the IP address range
>> 10.10.10.x.
>>
>> I can't ping the virtual server DC from my home workgroup and vice-
>> versa. Is there a way to somehow allow them to see each other on the
>> network?
>>
>> Thanks for all your help in advance
>>
>> Ian.
>>
>