> Wireless network cards on the virtual machines? Do you mean they have
> NICs each, one linked to a wireless NIC and one to a loopback adapter?
>
> The whole setup seems a bit odd to me. Why do the servers have two
>
> I would just give them one NIC each and set them to local only. They
> then work like three machines plugged into a switch. AD works fine in that
> config.
>
> "Juhani" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> >I have three virtual machines. All are in the domain sps.local.
> >
> > The first is Win 2003 running AD
> > The second Win 2003 running SQL Server 2K
> > The third Win 2003 running SPS 2003.
> >
> > All three have two network cards (Wireless and Lookback Adapter)
> >
> > I have created three users on the AD machine - DomainAdmin; SQLAdmin and
> > SPSAdmin.
> >
> > As part of the SPS 2003 install I need to add SPSAdmin to the local (to
> > server3) Power Users group. It refuses because it can't find
> > (email address - cut out)l or sps.local\SPSAdmin
> >
> > I can ping the wireless adapter of the AD server from the SPS server and
> > can
> > also ping the SQL Server server. There are no other servers in the
> >
> > (I'm unsure if this is a VPC question or an AD one - I have never used
> > at
> > work because we haven't had it)
> >
> > Why isn't server3 finding SPSAdmin in the domain? Why doesn't anything
> > seem
> > to know about the domain controller even though I can ping it (and have
> > tried adding that same address as DNS address 2 for the SPS server. (How
> > can
> > I force the domain to act like one?)
> >
> > Grateful for any hints.
> >
> > Juhani
> >
> >
> >
> >
> >
> >
>
>

> I have three virtual machines. All are in the domain sps.local.
>
> The first is Win 2003 running AD
> The second Win 2003 running SQL Server 2K
> The third Win 2003 running SPS 2003.
>
> All three have two network cards (Wireless and Lookback Adapter)
>
> I have created three users on the AD machine - DomainAdmin; SQLAdmin and
> SPSAdmin.
>
> As part of the SPS 2003 install I need to add SPSAdmin to the local (to
> server3) Power Users group. It refuses because it can't find
> (email address - cut out)l or sps.local\SPSAdmin
>
> I can ping the wireless adapter of the AD server from the SPS server and
> also ping the SQL Server server. There are no other servers in the domain.
>
> (I'm unsure if this is a VPC question or an AD one - I have never used AD
> work because we haven't had it)
> Why isn't server3 finding SPSAdmin in the domain? Why doesn't anything
> to know about the domain controller even though I can ping it (and have
> tried adding that same address as DNS address 2 for the SPS server. (How
> I force the domain to act like one?)
>
> I have three virtual machines. All are in the domain sps.local.
>
> The first is Win 2003 running AD
> The second Win 2003 running SQL Server 2K
> The third Win 2003 running SPS 2003.
>
> All three have two network cards (Wireless and Lookback Adapter)
>
> I have created three users on the AD machine - DomainAdmin; SQLAdmin and
> SPSAdmin.
>
> As part of the SPS 2003 install I need to add SPSAdmin to the local (to
> server3) Power Users group. It refuses because it can't find
> (email address - cut out)l or sps.local\SPSAdmin
>
> I can ping the wireless adapter of the AD server from the SPS server and
> also ping the SQL Server server. There are no other servers in the domain.
>
> (I'm unsure if this is a VPC question or an AD one - I have never used AD
> work because we haven't had it)
>
> Why isn't server3 finding SPSAdmin in the domain? Why doesn't anything
> to know about the domain controller even though I can ping it (and have
> tried adding that same address as DNS address 2 for the SPS server. (How
> I force the domain to act like one?)
>
> Grateful for any hints.
>
> Juhani
>
>
>
>
>
>

>I have three virtual machines. All are in the domain sps.local.
>
> The first is Win 2003 running AD
> The second Win 2003 running SQL Server 2K
> The third Win 2003 running SPS 2003.
>
> All three have two network cards (Wireless and Lookback Adapter)
>
> I have created three users on the AD machine - DomainAdmin; SQLAdmin and
> SPSAdmin.
>
> As part of the SPS 2003 install I need to add SPSAdmin to the local (to
> server3) Power Users group. It refuses because it can't find
> (email address - cut out)l or sps.local\SPSAdmin
>
> I can ping the wireless adapter of the AD server from the SPS server and
> can
> also ping the SQL Server server. There are no other servers in the domain.
>
> (I'm unsure if this is a VPC question or an AD one - I have never used AD
> at
> work because we haven't had it)
>
> Why isn't server3 finding SPSAdmin in the domain? Why doesn't anything
> seem
> to know about the domain controller even though I can ping it (and have
> tried adding that same address as DNS address 2 for the SPS server. (How
> can
> I force the domain to act like one?)
>
> Grateful for any hints.
>
> Juhani
>
>
>
>
>
>

> Keep it simple with just one NIC in each server, basically as Herb
> described. If you want Internet access, configure one virtual machine
> (preferably not a DC) to act as a router between the local subnet and the
> physical LAN. If necessary, configure DNS forwarding on your local DNS
> server to resolve external URLs.
>
> "Herb Martin" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > "Juhani" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> >> I have three virtual machines. All are in the domain sps.local.
> >>
> >> The first is Win 2003 running AD
> >> The second Win 2003 running SQL Server 2K
> >> The third Win 2003 running SPS 2003.
> >>
> >> All three have two network cards (Wireless and Lookback Adapter)
> >>
> >> I have created three users on the AD machine - DomainAdmin; SQLAdmin
> >> SPSAdmin.
> >>
> >> As part of the SPS 2003 install I need to add SPSAdmin to the local (to
> >> server3) Power Users group. It refuses because it can't find
> >> (email address - cut out)l or sps.local\SPSAdmin
> >>
> >> I can ping the wireless adapter of the AD server from the SPS server
> > can
> >> also ping the SQL Server server. There are no other servers in the
> >> domain.
> >>
> >> (I'm unsure if this is a VPC question or an AD one - I have never used
> > at
> >> work because we haven't had it)
> >
> > I am not sure either; I am fairly new to VPC/VS
> > so it could be some virtual oddity but it SOUNDS
> > like one of the VERY COMMON problems in AD
> > where DNS is almost always the culprit.
> >
> > Almost all AD problems, of replication and authentication
> > and even of things like downloading GPOs or profiles which
> > are dependent on the authentication, are actually DNS issues.
> >
> > This presumes you have the basic network operating correctly.
> >
> > Note: You should not have MULTIPLE NICs from the same
> > machine on the same subnet (virtual or otherwise) in Windows
> > unless the two NICs are teamed (extra software drivers) or
> > bridged (built-in as of XP & 2003) this doesn't work correctly.
> >
> >
> > DNS for AD
> > 1) Dynamic for the zone supporting AD
> > 2) All internal DNS clients NIC\IP properties must specify SOLELY
> > that internal, dynamic DNS server (set.)
> > 3) DCs and even DNS servers are DNS clients too -- see #2
> > 4) If you have more than one Domain, every DNS server must
> > be able to resolve ALL domain (either directly or indirectly)
> >
> > netdiag /fix
> >
> > ...or maybe:
> >
> > dcdiag /fix
> >
> > (Win2003 can do this from Support tools):
> > nltest /dsregdns /server:DC-ServerNameGoesHere
> > http://support.microsoft.com/kb/q260371/
> >
> > Ensure that DNS zones/domains are fully replicated to all DNS
> > servers for that (internal) zone/domain.
> >
> > Also useful may be running DCDiag on each DC, sending the
> > output to a text file, and searching for FAIL, ERROR, WARN.
> >
> > Single Lable domain zone names are a problem Google:
> > [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
> >
> >> Why isn't server3 finding SPSAdmin in the domain? Why doesn't anything
> > seem
> >> to know about the domain controller even though I can ping it (and have
> >> tried adding that same address as DNS address 2 for the SPS server.
> > can
> >> I force the domain to act like one?)
> >>
> >
> >
> > --
> > Herb Martin
> >
> >
> > "Juhani" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> >> I have three virtual machines. All are in the domain sps.local.
> >>
> >> The first is Win 2003 running AD
> >> The second Win 2003 running SQL Server 2K
> >> The third Win 2003 running SPS 2003.
> >>
> >> All three have two network cards (Wireless and Lookback Adapter)
> >>
> >> I have created three users on the AD machine - DomainAdmin; SQLAdmin
> >> SPSAdmin.
> >>
> >> As part of the SPS 2003 install I need to add SPSAdmin to the local (to
> >> server3) Power Users group. It refuses because it can't find
> >> (email address - cut out)l or sps.local\SPSAdmin
> >>
> >> I can ping the wireless adapter of the AD server from the SPS server
> > can
> >> also ping the SQL Server server. There are no other servers in the
> >> domain.
> >>
> >> (I'm unsure if this is a VPC question or an AD one - I have never used
> > at
> >> work because we haven't had it)
> >>
> >> Why isn't server3 finding SPSAdmin in the domain? Why doesn't anything
> > seem
> >> to know about the domain controller even though I can ping it (and have
> >> tried adding that same address as DNS address 2 for the SPS server.
> > can
> >> I force the domain to act like one?)
> >>
> >> Grateful for any hints.
> >>
> >> Juhani
> >>
> >>
> >>
> >>
> >>
> >>
> >
> >
>
>

> Also:
>
> If an INTERNAL machine is used as the router
> (e.g., ISA or just ICS or Server NAT on a domain
> machine) then that box must NOT accept the DNS
> setting from the ISP through DHCP.
>
> Type in the INTERNAL DNS value on the external
> NIC as manual entries take precedence over the
> DHCP supplied OPTIONS.
>
> You still get the IP and Mask, but generally you
> override the name server values.
>
>
> --
> Herb Martin
>
>
> "Bill Grant" <not.available@online> wrote in message
> news:(email address - cut out)...
> > Keep it simple with just one NIC in each server, basically as Herb
> > described. If you want Internet access, configure one virtual machine
> > (preferably not a DC) to act as a router between the local subnet and
> > physical LAN. If necessary, configure DNS forwarding on your local DNS
> > server to resolve external URLs.
> >
> > "Herb Martin" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> > > "Juhani" <(email address - cut out)> wrote in message
> > > news:(email address - cut out)...
> > >> I have three virtual machines. All are in the domain sps.local.
> > >>
> > >> The first is Win 2003 running AD
> > >> The second Win 2003 running SQL Server 2K
> > >> The third Win 2003 running SPS 2003.
> > >>
> > >> All three have two network cards (Wireless and Lookback Adapter)
> > >>
> > >> I have created three users on the AD machine - DomainAdmin; SQLAdmin
> and
> > >> SPSAdmin.
> > >>
> > >> As part of the SPS 2003 install I need to add SPSAdmin to the local
> > >> server3) Power Users group. It refuses because it can't find
> > >> (email address - cut out)l or sps.local\SPSAdmin
> > >>
> > >> I can ping the wireless adapter of the AD server from the SPS server
> and
> > > can
> > >> also ping the SQL Server server. There are no other servers in the
> > >> domain.
> > >>
> > >> (I'm unsure if this is a VPC question or an AD one - I have never
> AD
> > > at
> > >> work because we haven't had it)
> > >
> > > I am not sure either; I am fairly new to VPC/VS
> > > so it could be some virtual oddity but it SOUNDS
> > > like one of the VERY COMMON problems in AD
> > > where DNS is almost always the culprit.
> > >
> > > Almost all AD problems, of replication and authentication
> > > and even of things like downloading GPOs or profiles which
> > > are dependent on the authentication, are actually DNS issues.
> > >
> > > This presumes you have the basic network operating correctly.
> > >
> > > Note: You should not have MULTIPLE NICs from the same
> > > machine on the same subnet (virtual or otherwise) in Windows
> > > unless the two NICs are teamed (extra software drivers) or
> > > bridged (built-in as of XP & 2003) this doesn't work correctly.
> > >
> > >
> > > DNS for AD
> > > 1) Dynamic for the zone supporting AD
> > > 2) All internal DNS clients NIC\IP properties must specify SOLELY
> > > that internal, dynamic DNS server (set.)
> > > 3) DCs and even DNS servers are DNS clients too -- see #2
> > > 4) If you have more than one Domain, every DNS server must
> > > be able to resolve ALL domain (either directly or
> > >
> > > netdiag /fix
> > >
> > > ...or maybe:
> > >
> > > dcdiag /fix
> > >
> > > (Win2003 can do this from Support tools):
> > > nltest /dsregdns /server:DC-ServerNameGoesHere
> > > http://support.microsoft.com/kb/q260371/
> > >
> > > Ensure that DNS zones/domains are fully replicated to all DNS
> > > servers for that (internal) zone/domain.
> > >
> > > Also useful may be running DCDiag on each DC, sending the
> > > output to a text file, and searching for FAIL, ERROR, WARN.
> > >
> > > Single Lable domain zone names are a problem Google:
> > > [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
> > >
> > >> Why isn't server3 finding SPSAdmin in the domain? Why doesn't
> > > seem
> > >> to know about the domain controller even though I can ping it (and
> > >> tried adding that same address as DNS address 2 for the SPS server.
> (How
> > > can
> > >> I force the domain to act like one?)
> > >>
> > >
> > >
> > > --
> > > Herb Martin
> > >
> > >
> > > "Juhani" <(email address - cut out)> wrote in message
> > > news:(email address - cut out)...
> > >> I have three virtual machines. All are in the domain sps.local.
> > >>
> > >> The first is Win 2003 running AD
> > >> The second Win 2003 running SQL Server 2K
> > >> The third Win 2003 running SPS 2003.
> > >>
> > >> All three have two network cards (Wireless and Lookback Adapter)
> > >>
> > >> I have created three users on the AD machine - DomainAdmin; SQLAdmin
> and
> > >> SPSAdmin.
> > >>
> > >> As part of the SPS 2003 install I need to add SPSAdmin to the local
> > >> server3) Power Users group. It refuses because it can't find
> > >> (email address - cut out)l or sps.local\SPSAdmin
> > >>
> > >> I can ping the wireless adapter of the AD server from the SPS server
> and
> > > can
> > >> also ping the SQL Server server. There are no other servers in the
> > >> domain.
> > >>
> > >> (I'm unsure if this is a VPC question or an AD one - I have never
> AD
> > > at
> > >> work because we haven't had it)
> > >>
> > >> Why isn't server3 finding SPSAdmin in the domain? Why doesn't
> > > seem
> > >> to know about the domain controller even though I can ping it (and
> > >> tried adding that same address as DNS address 2 for the SPS server.
> (How
> > > can
> > >> I force the domain to act like one?)
> > >>
> > >> Grateful for any hints.
> > >>
> > >> Juhani
> > >>
> > >>
> > >>
> > >>
> > >>
> > >>
> > >
> > >
> >
> >
>
>

> Thanks for both your help.
>
> I'm going to go away and try to work out what the last three messages
> (I'm loath to mess up my NICs as it took me ages to get them to work
> (non-AD) the way I wanted).
> But I'm getting a new work machine where I *will* need AD and where I can
> start setting up VPC from scratch so there's hope that I can use the
> there (once I understand it)
> Thanks for both your help.
>
> I'm going to go away and try to work out what the last three messages
> (I'm loath to mess up my NICs as it took me ages to get them to work
> (non-AD) the way I wanted).
>
> But I'm getting a new work machine where I *will* need AD and where I can
> start setting up VPC from scratch so there's hope that I can use the
> there (once I understand it)
>
> Juhani
>
> "Herb Martin" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Also:
> >
> > If an INTERNAL machine is used as the router
> > (e.g., ISA or just ICS or Server NAT on a domain
> > machine) then that box must NOT accept the DNS
> > setting from the ISP through DHCP.
> >
> > Type in the INTERNAL DNS value on the external
> > NIC as manual entries take precedence over the
> > DHCP supplied OPTIONS.
> >
> > You still get the IP and Mask, but generally you
> > override the name server values.
> >
> >
> > --
> > Herb Martin
> >
> >
> > "Bill Grant" <not.available@online> wrote in message
> > news:(email address - cut out)...
> > > Keep it simple with just one NIC in each server, basically as Herb
> > > described. If you want Internet access, configure one virtual machine
> > > (preferably not a DC) to act as a router between the local subnet and
> the
> > > physical LAN. If necessary, configure DNS forwarding on your local
> > > server to resolve external URLs.
> > >
> > > "Herb Martin" <(email address - cut out)> wrote in message
> > > news:(email address - cut out)...
> > > > "Juhani" <(email address - cut out)> wrote in message
> > > > news:(email address - cut out)...
> > > >> I have three virtual machines. All are in the domain sps.local.
> > > >>
> > > >> The first is Win 2003 running AD
> > > >> The second Win 2003 running SQL Server 2K
> > > >> The third Win 2003 running SPS 2003.
> > > >>
> > > >> All three have two network cards (Wireless and Lookback Adapter)
> > > >>
> > > >> I have created three users on the AD machine - DomainAdmin;
> > and
> > > >> SPSAdmin.
> > > >>
> > > >> As part of the SPS 2003 install I need to add SPSAdmin to the local
> (to
> > > >> server3) Power Users group. It refuses because it can't find
> > > >> (email address - cut out)l or sps.local\SPSAdmin
> > > >>
> > > >> I can ping the wireless adapter of the AD server from the SPS
> > and
> > > > can
> > > >> also ping the SQL Server server. There are no other servers in the
> > > >> domain.
> > > >>
> > > >> (I'm unsure if this is a VPC question or an AD one - I have never
> used
> > AD
> > > > at
> > > >> work because we haven't had it)
> > > >
> > > > I am not sure either; I am fairly new to VPC/VS
> > > > so it could be some virtual oddity but it SOUNDS
> > > > like one of the VERY COMMON problems in AD
> > > > where DNS is almost always the culprit.
> > > >
> > > > Almost all AD problems, of replication and authentication
> > > > and even of things like downloading GPOs or profiles which
> > > > are dependent on the authentication, are actually DNS issues.
> > > >
> > > > This presumes you have the basic network operating correctly.
> > > >
> > > > Note: You should not have MULTIPLE NICs from the same
> > > > machine on the same subnet (virtual or otherwise) in Windows
> > > > unless the two NICs are teamed (extra software drivers) or
> > > > bridged (built-in as of XP & 2003) this doesn't work correctly.
> > > >
> > > >
> > > > DNS for AD
> > > > 1) Dynamic for the zone supporting AD
> > > > 2) All internal DNS clients NIC\IP properties must specify SOLELY
> > > > that internal, dynamic DNS server (set.)
> > > > 3) DCs and even DNS servers are DNS clients too -- see #2
> > > > 4) If you have more than one Domain, every DNS server must
> > > > be able to resolve ALL domain (either directly or
> indirectly)
> > > >
> > > > netdiag /fix
> > > >
> > > > ...or maybe:
> > > >
> > > > dcdiag /fix
> > > >
> > > > (Win2003 can do this from Support tools):
> > > > nltest /dsregdns /server:DC-ServerNameGoesHere
> > > > http://support.microsoft.com/kb/q260371/
> > > >
> > > > Ensure that DNS zones/domains are fully replicated to all DNS
> > > > servers for that (internal) zone/domain.
> > > >
> > > > Also useful may be running DCDiag on each DC, sending the
> > > > output to a text file, and searching for FAIL, ERROR, WARN.
> > > >
> > > > Single Lable domain zone names are a problem Google:
> > > > [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
> > > >
> > > >> Why isn't server3 finding SPSAdmin in the domain? Why doesn't
> anything
> > > > seem
> > > >> to know about the domain controller even though I can ping it (and
> have
> > > >> tried adding that same address as DNS address 2 for the SPS server.
> > (How
> > > > can
> > > >> I force the domain to act like one?)
> > > >>
> > > >
> > > >
> > > > --
> > > > Herb Martin
> > > >
> > > >
> > > > "Juhani" <(email address - cut out)> wrote in message
> > > > news:(email address - cut out)...
> > > >> I have three virtual machines. All are in the domain sps.local.
> > > >>
> > > >> The first is Win 2003 running AD
> > > >> The second Win 2003 running SQL Server 2K
> > > >> The third Win 2003 running SPS 2003.
> > > >>
> > > >> All three have two network cards (Wireless and Lookback Adapter)
> > > >>
> > > >> I have created three users on the AD machine - DomainAdmin;
> > and
> > > >> SPSAdmin.
> > > >>
> > > >> As part of the SPS 2003 install I need to add SPSAdmin to the local
> (to
> > > >> server3) Power Users group. It refuses because it can't find
> > > >> (email address - cut out)l or sps.local\SPSAdmin
> > > >>
> > > >> I can ping the wireless adapter of the AD server from the SPS
> > and
> > > > can
> > > >> also ping the SQL Server server. There are no other servers in the
> > > >> domain.
> > > >>
> > > >> (I'm unsure if this is a VPC question or an AD one - I have never
> used
> > AD
> > > > at
> > > >> work because we haven't had it)
> > > >>
> > > >> Why isn't server3 finding SPSAdmin in the domain? Why doesn't
> anything
> > > > seem
> > > >> to know about the domain controller even though I can ping it (and
> have
> > > >> tried adding that same address as DNS address 2 for the SPS server.
> > (How
> > > > can
> > > >> I force the domain to act like one?)
> > > >>
> > > >> Grateful for any hints.
> > > >>
> > > >> Juhani
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > > >
> > >
> > >
> >
> >
>
>

> "Juhani" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> I have three virtual machines. All are in the domain sps.local.
>>
>> The first is Win 2003 running AD
>> The second Win 2003 running SQL Server 2K
>> The third Win 2003 running SPS 2003.
>>
>> All three have two network cards (Wireless and Lookback Adapter)
>>
>> I have created three users on the AD machine - DomainAdmin; SQLAdmin and
>> SPSAdmin.
>>
>> As part of the SPS 2003 install I need to add SPSAdmin to the local (to
>> server3) Power Users group. It refuses because it can't find
>> (email address - cut out)l or sps.local\SPSAdmin
>>
>> I can ping the wireless adapter of the AD server from the SPS server and
> can
>> also ping the SQL Server server. There are no other servers in the
>> domain.
>>
>> (I'm unsure if this is a VPC question or an AD one - I have never used AD
> at
>> work because we haven't had it)
>
> I am not sure either; I am fairly new to VPC/VS
> so it could be some virtual oddity but it SOUNDS
> like one of the VERY COMMON problems in AD
> where DNS is almost always the culprit.
>
> Almost all AD problems, of replication and authentication
> and even of things like downloading GPOs or profiles which
> are dependent on the authentication, are actually DNS issues.
>
> This presumes you have the basic network operating correctly.
>
> Note: You should not have MULTIPLE NICs from the same
> machine on the same subnet (virtual or otherwise) in Windows
> unless the two NICs are teamed (extra software drivers) or
> bridged (built-in as of XP & 2003) this doesn't work correctly.
>
>
> DNS for AD
> 1) Dynamic for the zone supporting AD
> 2) All internal DNS clients NIC\IP properties must specify SOLELY
> that internal, dynamic DNS server (set.)
> 3) DCs and even DNS servers are DNS clients too -- see #2
> 4) If you have more than one Domain, every DNS server must
> be able to resolve ALL domain (either directly or indirectly)
>
> netdiag /fix
>
> ...or maybe:
>
> dcdiag /fix
>
> (Win2003 can do this from Support tools):
> nltest /dsregdns /server:DC-ServerNameGoesHere
> http://support.microsoft.com/kb/q260371/
>
> Ensure that DNS zones/domains are fully replicated to all DNS
> servers for that (internal) zone/domain.
>
> Also useful may be running DCDiag on each DC, sending the
> output to a text file, and searching for FAIL, ERROR, WARN.
>
> Single Lable domain zone names are a problem Google:
> [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
>
>> Why isn't server3 finding SPSAdmin in the domain? Why doesn't anything
> seem
>> to know about the domain controller even though I can ping it (and have
>> tried adding that same address as DNS address 2 for the SPS server. (How
> can
>> I force the domain to act like one?)
>>
>
>
> --
> Herb Martin
>
>
> "Juhani" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
>> I have three virtual machines. All are in the domain sps.local.
>>
>> The first is Win 2003 running AD
>> The second Win 2003 running SQL Server 2K
>> The third Win 2003 running SPS 2003.
>>
>> All three have two network cards (Wireless and Lookback Adapter)
>>
>> I have created three users on the AD machine - DomainAdmin; SQLAdmin and
>> SPSAdmin.
>>
>> As part of the SPS 2003 install I need to add SPSAdmin to the local (to
>> server3) Power Users group. It refuses because it can't find
>> (email address - cut out)l or sps.local\SPSAdmin
>>
>> I can ping the wireless adapter of the AD server from the SPS server and
> can
>> also ping the SQL Server server. There are no other servers in the
>> domain.
>>
>> (I'm unsure if this is a VPC question or an AD one - I have never used AD
> at
>> work because we haven't had it)
>>
>> Why isn't server3 finding SPSAdmin in the domain? Why doesn't anything
> seem
>> to know about the domain controller even though I can ping it (and have
>> tried adding that same address as DNS address 2 for the SPS server. (How
> can
>> I force the domain to act like one?)
>>
>> Grateful for any hints.
>>
>> Juhani
>>
>>
>>
>>
>>
>>
>
>

>in general about how NICs are configured since once
>understood (in general) they can be set in 30-60 seconds.
> "Juhani" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Thanks for both your help.
> >
> > I'm going to go away and try to work out what the last three messages
> mean.
>
> Ask a question...
>
> My messages at least should be very clear or I need to
> modify it to add that clarity.
>
> Especially the first of the three where I keep much of
> that as a standard recommendation and just edit it
> enough to apply to a particular poster's request.
>
> > (I'm loath to mess up my NICs as it took me ages to get them to work
> > (non-AD) the way I wanted).
>
> The above reflects that you may have a misunderstanding
> in general about how NICs are configured since once
> understood (in general) they can be set in 30-60 seconds.
>
> Changing the DNS Server setting of a NIC is trivial and
> can put pack just as quickly.
>
> And if they are wrong (wrong DNS) you don't really
> work the way you want.
>
> > But I'm getting a new work machine where I *will* need AD and where I
> > start setting up VPC from scratch so there's hope that I can use the
> advice
> > there (once I understand it)
>
> You only have to ask -- or even call.
> My number is on my web site: LearnQuick.Com
>
> --
> Herb Martin
>
>
> "Juhani" <(email address - cut out)> wrote in message
> news:(email address - cut out)...
> > Thanks for both your help.
> >
> > I'm going to go away and try to work out what the last three messages
> mean.
> > (I'm loath to mess up my NICs as it took me ages to get them to work
> > (non-AD) the way I wanted).
> >
> > But I'm getting a new work machine where I *will* need AD and where I
> > start setting up VPC from scratch so there's hope that I can use the
> advice
> > there (once I understand it)
> >
> > Juhani
> >
> > "Herb Martin" <(email address - cut out)> wrote in message
> > news:(email address - cut out)...
> > > Also:
> > >
> > > If an INTERNAL machine is used as the router
> > > (e.g., ISA or just ICS or Server NAT on a domain
> > > machine) then that box must NOT accept the DNS
> > > setting from the ISP through DHCP.
> > >
> > > Type in the INTERNAL DNS value on the external
> > > NIC as manual entries take precedence over the
> > > DHCP supplied OPTIONS.
> > >
> > > You still get the IP and Mask, but generally you
> > > override the name server values.
> > >
> > >
> > > --
> > > Herb Martin
> > >
> > >
> > > "Bill Grant" <not.available@online> wrote in message
> > > news:(email address - cut out)...
> > > > Keep it simple with just one NIC in each server, basically as
> > > > described. If you want Internet access, configure one virtual
> > > > (preferably not a DC) to act as a router between the local subnet
> > the
> > > > physical LAN. If necessary, configure DNS forwarding on your local
> DNS
> > > > server to resolve external URLs.
> > > >
> > > > "Herb Martin" <(email address - cut out)> wrote in message
> > > > news:(email address - cut out)...
> > > > > "Juhani" <(email address - cut out)> wrote in message
> > > > > news:(email address - cut out)...
> > > > >> I have three virtual machines. All are in the domain sps.local.
> > > > >>
> > > > >> The first is Win 2003 running AD
> > > > >> The second Win 2003 running SQL Server 2K
> > > > >> The third Win 2003 running SPS 2003.
> > > > >>
> > > > >> All three have two network cards (Wireless and Lookback Adapter)
> > > > >>
> > > > >> I have created three users on the AD machine - DomainAdmin;
> SQLAdmin
> > > and
> > > > >> SPSAdmin.
> > > > >>
> > > > >> As part of the SPS 2003 install I need to add SPSAdmin to the
> > (to
> > > > >> server3) Power Users group. It refuses because it can't find
> > > > >> (email address - cut out)l or sps.local\SPSAdmin
> > > > >>
> > > > >> I can ping the wireless adapter of the AD server from the SPS
> server
> > > and
> > > > > can
> > > > >> also ping the SQL Server server. There are no other servers in
> > > > >> domain.
> > > > >>
> > > > >> (I'm unsure if this is a VPC question or an AD one - I have never
> > used
> > > AD
> > > > > at
> > > > >> work because we haven't had it)
> > > > >
> > > > > I am not sure either; I am fairly new to VPC/VS
> > > > > so it could be some virtual oddity but it SOUNDS
> > > > > like one of the VERY COMMON problems in AD
> > > > > where DNS is almost always the culprit.
> > > > >
> > > > > Almost all AD problems, of replication and authentication
> > > > > and even of things like downloading GPOs or profiles which
> > > > > are dependent on the authentication, are actually DNS issues.
> > > > >
> > > > > This presumes you have the basic network operating correctly.
> > > > >
> > > > > Note: You should not have MULTIPLE NICs from the same
> > > > > machine on the same subnet (virtual or otherwise) in Windows
> > > > > unless the two NICs are teamed (extra software drivers) or
> > > > > bridged (built-in as of XP & 2003) this doesn't work correctly.
> > > > >
> > > > >
> > > > > DNS for AD
> > > > > 1) Dynamic for the zone supporting AD
> > > > > 2) All internal DNS clients NIC\IP properties must specify
> > > > > that internal, dynamic DNS server (set.)
> > > > > 3) DCs and even DNS servers are DNS clients too -- see #2
> > > > > 4) If you have more than one Domain, every DNS server must
> > > > > be able to resolve ALL domain (either directly or
> > indirectly)
> > > > >
> > > > > netdiag /fix
> > > > >
> > > > > ...or maybe:
> > > > >
> > > > > dcdiag /fix
> > > > >
> > > > > (Win2003 can do this from Support tools):
> > > > > nltest /dsregdns /server:DC-ServerNameGoesHere
> > > > > http://support.microsoft.com/kb/q260371/
> > > > >
> > > > > Ensure that DNS zones/domains are fully replicated to all DNS
> > > > > servers for that (internal) zone/domain.
> > > > >
> > > > > Also useful may be running DCDiag on each DC, sending the
> > > > > output to a text file, and searching for FAIL, ERROR, WARN.
> > > > >
> > > > > Single Lable domain zone names are a problem Google:
> > > > > [ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
> > > > >
> > > > >> Why isn't server3 finding SPSAdmin in the domain? Why doesn't
> > anything
> > > > > seem
> > > > >> to know about the domain controller even though I can ping it
> > have
> > > > >> tried adding that same address as DNS address 2 for the SPS
> > > (How
> > > > > can
> > > > >> I force the domain to act like one?)
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > > Herb Martin
> > > > >
> > > > >
> > > > > "Juhani" <(email address - cut out)> wrote in message
> > > > > news:(email address - cut out)...
> > > > >> I have three virtual machines. All are in the domain sps.local.
> > > > >>
> > > > >> The first is Win 2003 running AD
> > > > >> The second Win 2003 running SQL Server 2K
> > > > >> The third Win 2003 running SPS 2003.
> > > > >>
> > > > >> All three have two network cards (Wireless and Lookback Adapter)
> > > > >>
> > > > >> I have created three users on the AD machine - DomainAdmin;
> SQLAdmin
> > > and
> > > > >> SPSAdmin.
> > > > >>
> > > > >> As part of the SPS 2003 install I need to add SPSAdmin to the
> > (to
> > > > >> server3) Power Users group. It refuses because it can't find
> > > > >> (email address - cut out)l or sps.local\SPSAdmin
> > > > >>
> > > > >> I can ping the wireless adapter of the AD server from the SPS
> server
> > > and
> > > > > can
> > > > >> also ping the SQL Server server. There are no other servers in
> > > > >> domain.
> > > > >>
> > > > >> (I'm unsure if this is a VPC question or an AD one - I have never
> > used
> > > AD
> > > > > at
> > > > >> work because we haven't had it)
> > > > >>
> > > > >> Why isn't server3 finding SPSAdmin in the domain? Why doesn't
> > anything
> > > > > seem
> > > > >> to know about the domain controller even though I can ping it
> > have
> > > > >> tried adding that same address as DNS address 2 for the SPS
> > > (How
> > > > > can
> > > > >> I force the domain to act like one?)
> > > > >>
> > > > >> Grateful for any hints.
> > > > >>
> > > > >> Juhani
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >>
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>