> Host workgroup interfering with LAN
>
> Hello,
>
> I have a lab environment with 2 VMachines. A Win2003 R2 Domain Server and a
> Fedora C6 Member Server. Everything works grate but workgroup setup.
>
> Since I´ve used SHARED NETWORKING to connect the Win Server to the internet,
> this machine has now 2 workgroups: LAB (from the lab.local domain) and COMP1
> from the VPC host computer (Windows Vista Home Premium).
>
> I need to “delete” the COMP1 workgroup (within Win2003 DC virtual machine)
> in order to get an application running appropriately from Fedora.
>
> Can anyone help?
>
> Thanks in advance,
> mauricio

> How have you created these workgroups? Also - you should be aware that
> the virtual machines will be unable to communicate with each other if
> you are using shared networking. Your better option is to use ICS with
> a loopback adapter (per this post:
> http://blogs.msdn.com/virtual_pc_guy/archive/2005/10/04/477195.aspx)
>
> Cheers,
> Benjamin Armstrong
> ============================
> Windows Virtualization Program Manager
> Blog: http://blogs.msdn.com/Virtual_PC_Guy
> Book: http://tinyurl.com/ysxcbm
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights. You assume all risk for your use.
>
> mwann wrote:
> > Host workgroup interfering with LAN
> >
> > Hello,
> >
> > I have a lab environment with 2 VMachines. A Win2003 R2 Domain Server and a
> > Fedora C6 Member Server. Everything works grate but workgroup setup.
> >
> > Since I´ve used SHARED NETWORKING to connect the Win Server to the internet,
> > this machine has now 2 workgroups: LAB (from the lab.local domain) and COMP1
> > from the VPC host computer (Windows Vista Home Premium).
> >
> > I need to “delete” the COMP1 workgroup (within Win2003 DC virtual machine)
> > in order to get an application running appropriately from Fedora.
> >
> > Can anyone help?
> >
> > Thanks in advance,
> > mauricio
>

> The LAB workgroup is the previous name of the WinServer (before AD and
> lab.local domain). The COMP1 workgroup is the name of the host machine
> (Win
> Vista).
>
> WinServer DC virtual machine has two network adapters: Shared Networking
> AND
> Loopback Adaptor. Loopback is provisioning the LAN network to connect with
> Fedora Member server VM.
>
> When I use a Fedora command to review which workgroups it can see, cames
> up
> LAB (the actual workgroup) and COMP1 (workgroup named after the host
> computer). I would like to get rid of COMP1 in the lab.local (LAB)
> environment.
>
> Many thanks,
> mauricio
>
> "Benjamin Armstrong [MSFT]" wrote:
>
>> How have you created these workgroups? Also - you should be aware that
>> the virtual machines will be unable to communicate with each other if
>> you are using shared networking. Your better option is to use ICS with
>> a loopback adapter (per this post:
>> http://blogs.msdn.com/virtual_pc_guy/archive/2005/10/04/477195.aspx)
>>
>> Cheers,
>> Benjamin Armstrong
>> ============================
>> Windows Virtualization Program Manager
>> Blog: http://blogs.msdn.com/Virtual_PC_Guy
>> Book: http://tinyurl.com/ysxcbm
>>
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights. You assume all risk for your use.
>>
>> mwann wrote:
>> > Host workgroup interfering with LAN
>> >
>> > Hello,
>> >
>> > I have a lab environment with 2 VMachines. A Win2003 R2 Domain Server
>> > and a
>> > Fedora C6 Member Server. Everything works grate but workgroup setup.
>> >
>> > Since I´ve used SHARED NETWORKING to connect the Win Server to the
>> > internet,
>> > this machine has now 2 workgroups: LAB (from the lab.local domain) and
>> > COMP1
>> > from the VPC host computer (Windows Vista Home Premium).
>> >
>> > I need to “delete” the COMP1 workgroup (within Win2003 DC virtual
>> > machine)
>> > in order to get an application running appropriately from Fedora.
>> >
>> > Can anyone help?
>> >
>> > Thanks in advance,
>> > mauricio
>>

> That really has nothing to do with virtual machines. That is normal when
> you move from a workgroup to a domain. The old workgroup name will still be
> visible in the browser list for a while.
>
> Your real problem is probably the multihomed DC. This has been a problem
> since NT4 days. If you must use a multihomed DC, disable Netbios over TCP/IP
> on the "public" NIC of the DC so that it does not interfere with browsing on
> the "private" LAN.
>
> I am a bit surprised that you decided to make this machine a DC. What
> is the point if the client is running Linux? Active Directory is not really
> compatible with this sort of setup. You need to modify the way DNS works to
> use AD with NAT. And as Ben pointed out, shared networking is not
> appropriate either.
>
>
> "mwann" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > The LAB workgroup is the previous name of the WinServer (before AD and
> > lab.local domain). The COMP1 workgroup is the name of the host machine
> > (Win
> > Vista).
> >
> > WinServer DC virtual machine has two network adapters: Shared Networking
> > AND
> > Loopback Adaptor. Loopback is provisioning the LAN network to connect with
> > Fedora Member server VM.
> >
> > When I use a Fedora command to review which workgroups it can see, cames
> > up
> > LAB (the actual workgroup) and COMP1 (workgroup named after the host
> > computer). I would like to get rid of COMP1 in the lab.local (LAB)
> > environment.
> >
> > Many thanks,
> > mauricio
> >
> > "Benjamin Armstrong [MSFT]" wrote:
> >
> >> How have you created these workgroups? Also - you should be aware that
> >> the virtual machines will be unable to communicate with each other if
> >> you are using shared networking. Your better option is to use ICS with
> >> a loopback adapter (per this post:
> >> http://blogs.msdn.com/virtual_pc_guy/archive/2005/10/04/477195.aspx)
> >>
> >> Cheers,
> >> Benjamin Armstrong
> >> ============================
> >> Windows Virtualization Program Manager
> >> Blog: http://blogs.msdn.com/Virtual_PC_Guy
> >> Book: http://tinyurl.com/ysxcbm
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights. You assume all risk for your use.
> >>
> >> mwann wrote:
> >> > Host workgroup interfering with LAN
> >> >
> >> > Hello,
> >> >
> >> > I have a lab environment with 2 VMachines. A Win2003 R2 Domain Server
> >> > and a
> >> > Fedora C6 Member Server. Everything works grate but workgroup setup.
> >> >
> >> > Since I´ve used SHARED NETWORKING to connect the Win Server to the
> >> > internet,
> >> > this machine has now 2 workgroups: LAB (from the lab.local domain) and
> >> > COMP1
> >> > from the VPC host computer (Windows Vista Home Premium).
> >> >
> >> > I need to “delete” the COMP1 workgroup (within Win2003 DC virtual
> >> > machine)
> >> > in order to get an application running appropriately from Fedora.
> >> >
> >> > Can anyone help?
> >> >
> >> > Thanks in advance,
> >> > mauricio
> >>
>
>

> Here is the deal,
>
> I have an application server that runs only on Linux. In order to use this
> application in an AD environment, I need to make the Fedora machine member
> of
> Windows DC.
>
> Since I have this laboratory environment with 2 VPC machines, I need to
> "look" at the DC machine with only the former NT name as workgroup.
> Unfortunately, I also need Internet access in the Fedora machine. To
> simulate
> a working environment, I would like the DC machine (since I have only 2
> VPC
> machines) to provide Internet. While doing so, the Internet access through
> SHARED NETWORK on ethernet 0 is providing the host (windows vista)
> workgroup
> to the ethernet 1 connection, which is connecting the 2 VPC machines
> (LAN).
>
> If I use the host actual Internet card to provide access to the DC
> machine,
> I am unable to get connected.
>
> I am stalled.
>
> Thanks anyway.
> Mauricio
>
> "Bill Grant" wrote:
>
>> That really has nothing to do with virtual machines. That is normal
>> when
>> you move from a workgroup to a domain. The old workgroup name will still
>> be
>> visible in the browser list for a while.
>>
>> Your real problem is probably the multihomed DC. This has been a
>> problem
>> since NT4 days. If you must use a multihomed DC, disable Netbios over
>> TCP/IP
>> on the "public" NIC of the DC so that it does not interfere with browsing
>> on
>> the "private" LAN.
>>
>> I am a bit surprised that you decided to make this machine a DC.
>> What
>> is the point if the client is running Linux? Active Directory is not
>> really
>> compatible with this sort of setup. You need to modify the way DNS works
>> to
>> use AD with NAT. And as Ben pointed out, shared networking is not
>> appropriate either.
>>
>>
>> "mwann" <(email address - cut out)> wrote in message
>> news:(email address - cut out)...
>> > The LAB workgroup is the previous name of the WinServer (before AD and
>> > lab.local domain). The COMP1 workgroup is the name of the host machine
>> > (Win
>> > Vista).
>> >
>> > WinServer DC virtual machine has two network adapters: Shared
>> > Networking
>> > AND
>> > Loopback Adaptor. Loopback is provisioning the LAN network to connect
>> > with
>> > Fedora Member server VM.
>> >
>> > When I use a Fedora command to review which workgroups it can see,
>> > cames
>> > up
>> > LAB (the actual workgroup) and COMP1 (workgroup named after the host
>> > computer). I would like to get rid of COMP1 in the lab.local (LAB)
>> > environment.
>> >
>> > Many thanks,
>> > mauricio
>> >
>> > "Benjamin Armstrong [MSFT]" wrote:
>> >
>> >> How have you created these workgroups? Also - you should be aware
>> >> that
>> >> the virtual machines will be unable to communicate with each other if
>> >> you are using shared networking. Your better option is to use ICS
>> >> with
>> >> a loopback adapter (per this post:
>> >> http://blogs.msdn.com/virtual_pc_guy/archive/2005/10/04/477195.aspx)
>> >>
>> >> Cheers,
>> >> Benjamin Armstrong
>> >> ============================
>> >> Windows Virtualization Program Manager
>> >> Blog: http://blogs.msdn.com/Virtual_PC_Guy
>> >> Book: http://tinyurl.com/ysxcbm
>> >>
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights. You assume all risk for your use.
>> >>
>> >> mwann wrote:
>> >> > Host workgroup interfering with LAN
>> >> >
>> >> > Hello,
>> >> >
>> >> > I have a lab environment with 2 VMachines. A Win2003 R2 Domain
>> >> > Server
>> >> > and a
>> >> > Fedora C6 Member Server. Everything works grate but workgroup setup.
>> >> >
>> >> > Since I´ve used SHARED NETWORKING to connect the Win Server to the
>> >> > internet,
>> >> > this machine has now 2 workgroups: LAB (from the lab.local domain)
>> >> > and
>> >> > COMP1
>> >> > from the VPC host computer (Windows Vista Home Premium).
>> >> >
>> >> > I need to “delete” the COMP1 workgroup (within Win2003 DC virtual
>> >> > machine)
>> >> > in order to get an application running appropriately from Fedora.
>> >> >
>> >> > Can anyone help?
>> >> >
>> >> > Thanks in advance,
>> >> > mauricio
>> >>
>>
>>

> As I said earlier, this really has nothing to do with virtual machines
> or virtual networking. Having a multihomed DC hs been a major problem since
> NT days and still is. Because the name of the DC is associated with two
> different IP addresses , there are problems with the operation of the
> computer browser service.
>
> You may be able to solve this by disabling Netbios over TCP/IP on the
> "public" IP of the DC. But you still may see the workgroup name of the
> "public" network. A DC, as the domain master browser, is progammed to merge
> browse lists on a routed network.
>
> You still have the problem that the Shared Networking (NAT) option in VPC
> is not suitable for this sort of thing. In a real-world scenario you would
> use a separate router (unless you use SBS server, which is designed to run
> as both a DC and a router). This router would run as a NAT router to give
> the private network access to the Internet. The DC would act as the DNS
> server and would be configured to forward to a public DNS service.
>
> I am still not sure why this machine has to be a DC when the application
> server is running on Linux. How do you make the app server a member of the
> domain?
>
> "mwann" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Here is the deal,
> >
> > I have an application server that runs only on Linux. In order to use this
> > application in an AD environment, I need to make the Fedora machine member
> > of
> > Windows DC.
> >
> > Since I have this laboratory environment with 2 VPC machines, I need to
> > "look" at the DC machine with only the former NT name as workgroup.
> > Unfortunately, I also need Internet access in the Fedora machine. To
> > simulate
> > a working environment, I would like the DC machine (since I have only 2
> > VPC
> > machines) to provide Internet. While doing so, the Internet access through
> > SHARED NETWORK on ethernet 0 is providing the host (windows vista)
> > workgroup
> > to the ethernet 1 connection, which is connecting the 2 VPC machines
> > (LAN).
> >
> > If I use the host actual Internet card to provide access to the DC
> > machine,
> > I am unable to get connected.
> >
> > I am stalled.
> >
> > Thanks anyway.
> > Mauricio
> >
> > "Bill Grant" wrote:
> >
> >> That really has nothing to do with virtual machines. That is normal
> >> when
> >> you move from a workgroup to a domain. The old workgroup name will still
> >> be
> >> visible in the browser list for a while.
> >>
> >> Your real problem is probably the multihomed DC. This has been a
> >> problem
> >> since NT4 days. If you must use a multihomed DC, disable Netbios over
> >> TCP/IP
> >> on the "public" NIC of the DC so that it does not interfere with browsing
> >> on
> >> the "private" LAN.
> >>
> >> I am a bit surprised that you decided to make this machine a DC.
> >> What
> >> is the point if the client is running Linux? Active Directory is not
> >> really
> >> compatible with this sort of setup. You need to modify the way DNS works
> >> to
> >> use AD with NAT. And as Ben pointed out, shared networking is not
> >> appropriate either.
> >>
> >>
> >> "mwann" <(email address - cut out)> wrote in message
> >> news:(email address - cut out)...
> >> > The LAB workgroup is the previous name of the WinServer (before AD and
> >> > lab.local domain). The COMP1 workgroup is the name of the host machine
> >> > (Win
> >> > Vista).
> >> >
> >> > WinServer DC virtual machine has two network adapters: Shared
> >> > Networking
> >> > AND
> >> > Loopback Adaptor. Loopback is provisioning the LAN network to connect
> >> > with
> >> > Fedora Member server VM.
> >> >
> >> > When I use a Fedora command to review which workgroups it can see,
> >> > cames
> >> > up
> >> > LAB (the actual workgroup) and COMP1 (workgroup named after the host
> >> > computer). I would like to get rid of COMP1 in the lab.local (LAB)
> >> > environment.
> >> >
> >> > Many thanks,
> >> > mauricio
> >> >
> >> > "Benjamin Armstrong [MSFT]" wrote:
> >> >
> >> >> How have you created these workgroups? Also - you should be aware
> >> >> that
> >> >> the virtual machines will be unable to communicate with each other if
> >> >> you are using shared networking. Your better option is to use ICS
> >> >> with
> >> >> a loopback adapter (per this post:
> >> >> http://blogs.msdn.com/virtual_pc_guy/archive/2005/10/04/477195.aspx)
> >> >>
> >> >> Cheers,
> >> >> Benjamin Armstrong
> >> >> ============================
> >> >> Windows Virtualization Program Manager
> >> >> Blog: http://blogs.msdn.com/Virtual_PC_Guy
> >> >> Book: http://tinyurl.com/ysxcbm
> >> >>
> >> >> This posting is provided "AS IS" with no warranties, and confers no
> >> >> rights. You assume all risk for your use.
> >> >>
> >> >> mwann wrote:
> >> >> > Host workgroup interfering with LAN
> >> >> >
> >> >> > Hello,
> >> >> >
> >> >> > I have a lab environment with 2 VMachines. A Win2003 R2 Domain
> >> >> > Server
> >> >> > and a
> >> >> > Fedora C6 Member Server. Everything works grate but workgroup setup.
> >> >> >
> >> >> > Since I´ve used SHARED NETWORKING to connect the Win Server to the
> >> >> > internet,
> >> >> > this machine has now 2 workgroups: LAB (from the lab.local domain)
> >> >> > and
> >> >> > COMP1
> >> >> > from the VPC host computer (Windows Vista Home Premium).
> >> >> >
> >> >> > I need to “delete” the COMP1 workgroup (within Win2003 DC virtual
> >> >> > machine)
> >> >> > in order to get an application running appropriately from Fedora.
> >> >> >
> >> >> > Can anyone help?
> >> >> >
> >> >> > Thanks in advance,
> >> >> > mauricio
> >> >>
> >>
> >>
>
>