After installing router I can no longer log into the domain

[jtpr]

I have run into an odd situation that I can't seem to figure out. I have a
very simple network. One 2000 advanced server DC and (2) 2000 pro clients.
Now, for a couple of years this has been running just fine. I have a domain
called XYZ. Both users log into this domain and each have a personal and
common area on the server. The server is running DHCP/DNS. IP range is
10.1.1.x. Each client had their own dialup line out to the world, due to
the lack of anything else at the time, and all they really use it for is
minimal email.

OK, they move to another location. Everything is still OK for a couple of
months, so the move went fine. Then they hear they can get DSL. They get a
package consisting of a DSL modem and a LinkSys router. I hook everything
up, letting the new router be the DHCP server, disabling the scope at the
server, and giving the server a DHCP address. I'm using the same 10.1.1.x
numbering scheme. All hell breaks loose.

Neither user can log into the domain because they can no longer find the
server. If they log into their machines as local users, they can't even see
the server. They can ping it by number, so the hardware is OK. I have
tried adding the server to the local hosts files and giving it a static IP,
no luck.

I guess the bottom line is I don't know how to set this up. How do I set up
a DC and it's clients when I'm using a "foreign" DHCP/DNS server, such as
this router? Should I disable DHCP on the router and just stick with the
server? Actually, I would be just as happy to just screw the entire domain
thing and just have 2 clients and a file server. They only use it to back
files up to anyway. I am running Microsoft client and TCP/IP on the
clients, do I need another protocol?


-Jim
©¿©¬

If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam

 

[Steven L Umbach]

Windows 2000 relies heavily on dns as a resource locator in addition to host name
resolution. I would disable the dhcp on the Linksys and use dhcp from your server, or
at the very least manually configure your Windows 2000 computers to have only the
tcp/ip address of the domain controller [which should be static] as their dns server.
The domain controller also needs to be configured to use the Linksys as it's default
gateway which will enable it to use it's dns server to resolve internet names via
root hints or forwarding. See KB link below.--- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

 

[jtpr]

OK. But let's suppose I want to get rid of the domain altogether and just
use the server to store backups. That is, have the users log into their
machines locally, but map a couple of drives to the server. Is it too late
for that now that I have AD running on the server? If it is, and I
understand you correctly, I should point the DNS' of the clients at the DC,
and have the DC DNS address' point to itself, with the gateway being the
router?

--
-Jim
©¿©¬

If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam

Windows 2000 relies heavily on dns as a resource locator in addition to host name
resolution. I would disable the dhcp on the Linksys and use dhcp from your server, or
at the very least manually configure your Windows 2000 computers to have only the
tcp/ip address of the domain controller [which should be static] as their dns server.
The domain controller also needs to be configured to use the Linksys as it's default
gateway which will enable it to use it's dns server to resolve internet names via
root hints or forwarding. See KB link below.--- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

I have run into an odd situation that I can't seem to figure out. I have a
very simple network. One 2000 advanced server DC and (2) 2000 pro clients.
Now, for a couple of years this has been running just fine. I have a domain
called XYZ. Both users log into this domain and each have a personal and
common area on the server. The server is running DHCP/DNS. IP range is
10.1.1.x. Each client had their own dialup line out to the world, due to
the lack of anything else at the time, and all they really use it for is
minimal email.

OK, they move to another location. Everything is still OK for a couple of
months, so the move went fine. Then they hear they can get DSL. They get a
package consisting of a DSL modem and a LinkSys router. I hook everything
up, letting the new router be the DHCP server, disabling the scope at the
server, and giving the server a DHCP address. I'm using the same 10.1.1.x
numbering scheme. All hell breaks loose.

Neither user can log into the domain because they can no longer find the
server. If they log into their machines as local users, they can't even see
the server. They can ping it by number, so the hardware is OK. I have
tried adding the server to the local hosts files and giving it a static IP,
no luck.

I guess the bottom line is I don't know how to set this up. How do I set up
a DC and it's clients when I'm using a "foreign" DHCP/DNS server, such as
this router? Should I disable DHCP on the router and just stick with the
server? Actually, I would be just as happy to just screw the entire domain
thing and just have 2 clients and a file server. They only use it to back
files up to anyway. I am running Microsoft client and TCP/IP on the
clients, do I need another protocol?


-Jim
©¿©¬

If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam

 

[Steven L Umbach]

The dc needs to point to itself by it's assigned tcp/ip address in its
tci/ip configuration for preferred dns sever and to have to lan side of the
Linksys as it's default gateway. Personally I think the Active Directory
domain controller setup will be more effecient but as small as your network
is you certainly could just make it a regular server by running dcpromo on
it. --- Steve

OK. But let's suppose I want to get rid of the domain altogether and just
use the server to store backups. That is, have the users log into their
machines locally, but map a couple of drives to the server. Is it too late
for that now that I have AD running on the server? If it is, and I
understand you correctly, I should point the DNS' of the clients at the DC,
and have the DC DNS address' point to itself, with the gateway being the
router?

--
-Jim
©¿©¬

If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam

Windows 2000 relies heavily on dns as a resource locator in addition to host name
resolution. I would disable the dhcp on the Linksys and use dhcp from

your
server, or

at the very least manually configure your Windows 2000 computers to have only the
tcp/ip address of the domain controller [which should be static] as

their
dns server.

The domain controller also needs to be configured to use the Linksys as it's default
gateway which will enable it to use it's dns server to resolve internet names via
root hints or forwarding. See KB link below.--- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

couple

of

even

see

static

IP,

 

[jtpr]

Yeah, I'll probably leave it as a DC for now, only to learn how to do this
properly. So, I point the server at itself for its DNS, and make the router
the gateway. Does it matter if it is static or dynamic?

As for the clients, can I just let them get their info from the router?
Because what is happening here is they have the ISP DNS servers for their
DNS address' and the router as the gateway. If I override this by pointing
their DNS' at the DC, they can no longer find web address'. There does not
seem to be a way to have the ISP and the DC as their DNS servers, it seems
to be one way or the other.

Or would I be better off setting up the router as a DHCP client, and letting
the DC be the DHCP server, but pointing to the router for the gateway? If I
do that then how are the clients going to get the address' of the external
DNS servers to resolve web address'?

Thanks for all your time on this.

--
-Jim
©¿©¬

If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam

The dc needs to point to itself by it's assigned tcp/ip address in its
tci/ip configuration for preferred dns sever and to have to lan side of the
Linksys as it's default gateway. Personally I think the Active Directory
domain controller setup will be more effecient but as small as your network
is you certainly could just make it a regular server by running dcpromo on
it. --- Steve

OK. But let's suppose I want to get rid of the domain altogether and just
use the server to store backups. That is, have the users log into their
machines locally, but map a couple of drives to the server. Is it too late
for that now that I have AD running on the server? If it is, and I
understand you correctly, I should point the DNS' of the clients at the DC,
and have the DC DNS address' point to itself, with the gateway being the
router?

--
-Jim
©¿©¬

If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam

Windows 2000 relies heavily on dns as a resource locator in addition

to
host name

resolution. I would disable the dhcp on the Linksys and use dhcp from

your
server, or

at the very least manually configure your Windows 2000 computers to

have
only the

tcp/ip address of the domain controller [which should be static] as

their
dns server.

The domain controller also needs to be configured to use the Linksys

as
it's default

gateway which will enable it to use it's dns server to resolve

internet
names via

root hints or forwarding. See KB link below.--- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

I have run into an odd situation that I can't seem to figure out. I have a
very simple network. One 2000 advanced server DC and (2) 2000 pro clients.
Now, for a couple of years this has been running just fine. I have

a
domain

called XYZ. Both users log into this domain and each have a

personal
and

common area on the server. The server is running DHCP/DNS. IP

range

is due
to

for

is couple They
get a at
the even static I
set up such
as with
the to
back

 

[Marina Roos]

It's much easier if you let the DC do all the serving for DHCP, DNS and WINS
(if you have W9x, ME or NT4 clients).
You are using 2 nics in the server, right?
Make sure DNS on both nics are pointing to your server-IP. Put the
ISP-DNS-numbers in the tab Forwarders of your DNS-server.
Let the clients obtain an IP automatically from the DHCP-server, which will
also push DNS and WINS.

Marina

Yeah, I'll probably leave it as a DC for now, only to learn how to do this
properly. So, I point the server at itself for its DNS, and make the router
the gateway. Does it matter if it is static or dynamic?

As for the clients, can I just let them get their info from the router?
Because what is happening here is they have the ISP DNS servers for their
DNS address' and the router as the gateway. If I override this by pointing
their DNS' at the DC, they can no longer find web address'. There does not
seem to be a way to have the ISP and the DC as their DNS servers, it seems
to be one way or the other.

Or would I be better off setting up the router as a DHCP client, and letting
the DC be the DHCP server, but pointing to the router for the gateway? If I
do that then how are the clients going to get the address' of the external
DNS servers to resolve web address'?

Thanks for all your time on this.

--
-Jim
©¿©¬

If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam

The dc needs to point to itself by it's assigned tcp/ip address in its
tci/ip configuration for preferred dns sever and to have to lan side of the
Linksys as it's default gateway. Personally I think the Active Directory
domain controller setup will be more effecient but as small as your network
is you certainly could just make it a regular server by running dcpromo on
it. --- Steve

OK. But let's suppose I want to get rid of the domain altogether and just
use the server to store backups. That is, have the users log into their
machines locally, but map a couple of drives to the server. Is it too late
for that now that I have AD running on the server? If it is, and I
understand you correctly, I should point the DNS' of the clients at

the
DC,

and have the DC DNS address' point to itself, with the gateway being the
router?

--
-Jim
©¿©¬

If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam
Windows 2000 relies heavily on dns as a resource locator in addition to
host name
resolution. I would disable the dhcp on the Linksys and use dhcp

from
your

server, or
at the very least manually configure your Windows 2000 computers to have
only the
tcp/ip address of the domain controller [which should be static] as their
dns server.
The domain controller also needs to be configured to use the Linksys as
it's default
gateway which will enable it to use it's dns server to resolve internet
names via
root hints or forwarding. See KB link below.--- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

I have run into an odd situation that I can't seem to figure out. I
have a
very simple network. One 2000 advanced server DC and (2) 2000 pro
clients.
Now, for a couple of years this has been running just fine. I

have

a range for find
the can't
even

do

I

 

[jtpr]

No, only one NIC. Remember, I have a Linksys router as my gateway. I could
let the DC do all the serving as you suggest, I was just wondering, as a
point of interest, how I could set things up with the router doing the
DHCP/DNS, but still be able to log into the domain. It may not be possible.

--
-Jim
©¿©¬

If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam

It's much easier if you let the DC do all the serving for DHCP, DNS and WINS
(if you have W9x, ME or NT4 clients).
You are using 2 nics in the server, right?
Make sure DNS on both nics are pointing to your server-IP. Put the
ISP-DNS-numbers in the tab Forwarders of your DNS-server.
Let the clients obtain an IP automatically from the DHCP-server, which will
also push DNS and WINS.

Marina

Yeah, I'll probably leave it as a DC for now, only to learn how to do this
properly. So, I point the server at itself for its DNS, and make the router
the gateway. Does it matter if it is static or dynamic?

As for the clients, can I just let them get their info from the router?
Because what is happening here is they have the ISP DNS servers for their
DNS address' and the router as the gateway. If I override this by pointing
their DNS' at the DC, they can no longer find web address'. There does not
seem to be a way to have the ISP and the DC as their DNS servers, it seems
to be one way or the other.

Or would I be better off setting up the router as a DHCP client, and letting
the DC be the DHCP server, but pointing to the router for the gateway?

If

I
do that then how are the clients going to get the address' of the external
DNS servers to resolve web address'?

Thanks for all your time on this.

--
-Jim
©¿©¬

If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam
of
the

dcpromo

on

it. --- Steve

OK. But let's suppose I want to get rid of the domain altogether

and
just

use the server to store backups. That is, have the users log into their
machines locally, but map a couple of drives to the server. Is it too
late
for that now that I have AD running on the server? If it is, and I
understand you correctly, I should point the DNS' of the clients at the
DC,
and have the DC DNS address' point to itself, with the gateway being the
router?

--
-Jim
©¿©¬

If you want to reply by email its --> ryan at jimryan dot com
Please use BCC and lets all avoid spam
Windows 2000 relies heavily on dns as a resource locator in

addition
to

host name
resolution. I would disable the dhcp on the Linksys and use dhcp from
your
server, or
at the very least manually configure your Windows 2000 computers

to
have

only the
tcp/ip address of the domain controller [which should be static] as
their
dns server.
The domain controller also needs to be configured to use the

Linksys
as

it's default
gateway which will enable it to use it's dns server to resolve internet
names via
root hints or forwarding. See KB link below.--- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;291382

I have run into an odd situation that I can't seem to figure

out.

I have world,
due it
for scope
at do server,
such it
to

 

[SteveC]

No, only one NIC. Remember, I have a Linksys router as my gateway. I could
let the DC do all the serving as you suggest, I was just wondering, as a
point of interest, how I could set things up with the router doing the
DHCP/DNS, but still be able to log into the domain. It may not be possible.

Hello,

It is possible, but it sure would be a PITA to configure. Even then,
you will not be able to have the full functionality of using W2K
serving DNS and DHCP.

To make it work, for one thing, you would need your ISP to allow you
to register dynamic records with their DNS servers. Mucho luck with
this request.

The Linksys DHCP service is very limited compared to W2k, so a lot of
manual configuration like DNS domain would still be required. You
would be better off using static IP addresses in this case.

As Steven and Marina pointed out, it's a lot easier using w2k instead
of your router.

regards,

SteveC
======
If at first you don't succeed, forget skydiving