I have a domain, and I have a domain computer running WinSrv2008R2 being
used as a dev workstation. On it, I set up a Hyper-V virtual machine
that is NOT on the domain, but in a WORKGROUP. Everything works fine,
internet access etc. If I click on a domain server via the Network icon
it prompts for my domain user/password to connect.

But when I click on the network icon, I see all the non-XP domain
computers on the network - no domain XP computers show up.

1. Is this working correctly given it's a workgroup and not part of the
domain?

2. Computer Browser service is not running on the VM, is that why I
can't see the XP machines?

3. If I start Computer Browser service on the VM, is that advised?
Currently only DCs have the Computer Browser service running, and all
domain computers are visible on all domain computers.

Thanks!

Hi
Mixing Domain and Workgroup is Not a good idea.
Jack (MS, MVP-Networking).

"Dominick" wrote in message
...
I have a domain, and I have a domain computer running WinSrv2008R2 being
used as a dev workstation. On it, I set up a Hyper-V virtual machine that
is NOT on the domain, but in a WORKGROUP. Everything works fine, internet
access etc. If I click on a domain server via the Network icon it prompts
for my domain user/password to connect.

But when I click on the network icon, I see all the non-XP domain
computers on the network - no domain XP computers show up.

1. Is this working correctly given it's a workgroup and not part of the
domain?

2. Computer Browser service is not running on the VM, is that why I can't
see the XP machines?

3. If I start Computer Browser service on the VM, is that advised?
Currently only DCs have the Computer Browser service running, and all
domain computers are visible on all domain computers.

Thanks!

Hi
Mixing Domain and Workgroup is Not a good idea.
Jack (MS, MVP-Networking).

"Dominick" wrote in message
...
I have a domain, and I have a domain computer running WinSrv2008R2 being
used as a dev workstation. On it, I set up a Hyper-V virtual machine that
is NOT on the domain, but in a WORKGROUP. Everything works fine, internet
access etc. If I click on a domain server via the Network icon it prompts
for my domain user/password to connect.

But when I click on the network icon, I see all the non-XP domain
computers on the network - no domain XP computers show up.

1. Is this working correctly given it's a workgroup and not part of the
domain?

2. Computer Browser service is not running on the VM, is that why I can't
see the XP machines?

3. If I start Computer Browser service on the VM, is that advised?
Currently only DCs have the Computer Browser service running, and all
domain computers are visible on all domain computers.

Thanks!

I tried to find some documentation on this but couldn't - do you have
anything you can point to that I can read about the pitfalls of this? I
know about some things like "if the app will be running in a domain you
should be testing it in a domain", but for my purposes no domain
services are needed. In lieu of any reading, why do you say it's not a
good idea?

Jack [MVP-Networking] wrote:
Hi
Mixing Domain and Workgroup is Not a good idea.
Jack (MS, MVP-Networking).

"Dominick" wrote in message
...
I have a domain, and I have a domain computer running WinSrv2008R2
being used as a dev workstation. On it, I set up a Hyper-V virtual
machine that is NOT on the domain, but in a WORKGROUP. Everything
works fine, internet access etc. If I click on a domain server via
the Network icon it prompts for my domain user/password to connect.

But when I click on the network icon, I see all the non-XP domain
computers on the network - no domain XP computers show up.

1. Is this working correctly given it's a workgroup and not part of
the domain?

2. Computer Browser service is not running on the VM, is that why I
can't see the XP machines?

3. If I start Computer Browser service on the VM, is that advised?
Currently only DCs have the Computer Browser service running, and all
domain computers are visible on all domain computers.

Thanks!

I tried to find some documentation on this but couldn't - do you have
anything you can point to that I can read about the pitfalls of this? I
know about some things like "if the app will be running in a domain you
should be testing it in a domain", but for my purposes no domain
services are needed. In lieu of any reading, why do you say it's not a
good idea?

Jack [MVP-Networking] wrote:
Hi
Mixing Domain and Workgroup is Not a good idea.
Jack (MS, MVP-Networking).

"Dominick" wrote in message
...
I have a domain, and I have a domain computer running WinSrv2008R2
being used as a dev workstation. On it, I set up a Hyper-V virtual
machine that is NOT on the domain, but in a WORKGROUP. Everything
works fine, internet access etc. If I click on a domain server via
the Network icon it prompts for my domain user/password to connect.

But when I click on the network icon, I see all the non-XP domain
computers on the network - no domain XP computers show up.

1. Is this working correctly given it's a workgroup and not part of
the domain?

2. Computer Browser service is not running on the VM, is that why I
can't see the XP machines?

3. If I start Computer Browser service on the VM, is that advised?
Currently only DCs have the Computer Browser service running, and all
domain computers are visible on all domain computers.

Thanks!