Yes, manually configure all TCP/IP settings:
IP = 192.168.0.2
Subnet Mask = 255.255.255.0
Default gateway = 192.168.0.1 (router's IP)
Primary DNS = 90.0.0.2
If doing this enables you to join the domain, you may be able to switch back
to DHCP thereafter.
Doug Sherman
MCSE, MCSA, MCP+I, MVP
"Bud Belles" <(E-Mail Removed)> wrote in message
news:u$(E-Mail Removed)...
> I am having the router assign IP addresses. The first laptop got
> 192.168.0.2. Are you suggesting that I turn off the DHCP function and
then
> manually assign the laptop 192.168.0.2?
>
> Thanks,
> Bud
> "Doug Sherman [MVP]" <(E-Mail Removed)> wrote in
message
> news:(E-Mail Removed)...
> > Possible:
> >
> > If you are using the Linksys' DHCP function to configure wireless
clients,
> > try manually configuring them instead. On many low end routers if you
use
> > the DHCP function to configure clients with an IP of 90.0.0.2 for DNS,
> > they
> > would actually get 192.168.0.1. Queries go to the router and then the
> > router forwards them to 90.0.0.2. Generally this works OK, but one of
the
> > times it is most prone to failure is the domain join process.
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "Bud Belles" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> >> We just aquired a few laptops. I've configured our Linksys wireless
> > access
> >> point as a separate subnet (192.168.0.x) and connected it to our LAN
as
> >> 90.0.0.9. My domain controller is at 90.0.0.2. I can access the
> >> internet
> >> from a wireless laptop (its running Windows/XP Pro SP 2). I can ping
the
> > DC
> >> using its IP address, pinging a public web site also works. My problem
> >> shows up in that I can't get the laptop to join our domain. When I
> >> change
> >> its name and attempt to join the domain, the domain controller can't be
> >> found. I'm stuck and any suggestions would be greatly appreciated.
> >>
> >> Thanks,
> >> Bud
> >>
> >>
> >
> >
>
>
|
Similar Threads
