W2K box + W2kServerbox + router for cable modem w/ DHCP question

[milagro]

So I have what the title says...my question relates to connectivity. Currently both boxes can connect to the internet and the router is set up as a DHCP server. The two systems can also talk to each other, but I can't get the client to join the server's domain. The client is currently in its own workgroup but not a member of a domain. I've also set up DHCP on the server and defined a scope...and I'm fairly certain I could get the client to join the domain if I used remote access service and set up a vpn....but is this neccessary?

I guess I'm wondering what the normal/efficient method is for setting up a client/server lan that involves a router for sharing my cable connection....

 

[Saltin]

If you've got a Domain set-up, the DC should have a static IP, for starters.
Secondly, you have not mentioned what you are using for name resolution? If you are using 2k Server, I assume you must be using 2000 DNS. Is this the case?

9 times out of 10, when a client cant join a domain, its because it cant find the domain. When clients cant find the domain, its a name and service resolution problem.

Please post your resolution set-up (and if it is DNS, let me know what zones you have created).

 

[Hoober]

Do you have the internal IP address of the server specified in the DNS settings on the client computer? Or do you have the internal IP range that the router is handing out specified in the reverse lookup zones on the server? Either one of these should solve the problem.

 

[Saltin]

<< Do you have the internal IP address of the server specified in the DNS settings on the client computer? Or do you have the internal IP range that the router is handing out specified in the reverse lookup zones on the server? Either one of these should solve the problem. >>



Possibly, but I am guessing his DC's have not automatically registered thier LDAP and Kerberos records in DNS to begin with. Generally, first timer's make mistakes in DNS setup and design that prevent the normal automatic registration of these records from happening.

We can hope it's as simple as the client's DNS setting, but I don't think it is.
And who's in charge of DHCP here? The router or the 2k Server? One or the other please, not both!
Finally, has the 2k server DHCP been authorized in AD?

 

[milagro]

damn..i new I shouldn't try dealing w/ this at work..hehe...away from my setup but I'll do the best to answer...




<< If you've got a Domain set-up, the DC should have a static IP, for starters.
Secondly, you have not mentioned what you are using for name resolution? If you are using 2k Server, I assume you must be using 2000 DNS. Is this the case?
>>



Yeah, this is an issue...I've got a domain set-up, but i've got a cable isp using DHCP to my router...and my router is assigning ips dynamically to the systems on my lan, although, I've never seen them change. I guess I need to figure out how to have the router assign static ip's? I have an smc barricade...

yes, I am using 2000 DNS



<< Do you have the internal IP address of the server specified in the DNS settings on the client computer? Or do you have the internal IP range that the router is handing out specified in the reverse lookup zones on the server? Either one of these should solve the problem. >>



no to the first question...in my dns settings the server is identified and left out of the scope....forward lookup zones are identified, but I currently do not have anything listed in the reverse lookup zones...advise here is appreciated...



<< And who's in charge of DHCP here? The router or the 2k Server? One or the other please, not both!
Finally, has the 2k server DHCP been authorized in AD? >>



yeah...think I got too many dhcp chefs...like I said, I'll see if I can get that router to assign a static ip for the server..

yes, the dhcp server has been authorized in AD...

thx in advance for the help

 

[ivwshane]

First you need to stop your router from doing DHCP (most SOHO routers can be configured through an internal web page). Next set your router to a static LAN ip. Make sure both your servers have static ip's and that the scope is defined correctly. Next specify the server to use itself as the DNS (which I assume you have installed since DHCP on win2k server requires it) and I use a default gateway that points to the router, on the client machine set everthing to automatic. After all that is setup to join the domain open up system properties-->network identification-->properties, in the properties dialogue box check the "Domain" and hit ok. If all goes correctly then you should get a dialogue box asking for a user name and password and domain. The user/pass must be of someone with the appropriate rights on the server box.

 

[milagro]

<< First you need to stop your router from doing DHCP (most SOHO routers can be configured through an internal web page). Next set your router to a static LAN ip. Make sure both your servers have static ip's and that the scope is defined correctly. >>



So I was planning on having the router assign a static ip to the server e.g. router = 192.168.2.1; assign 192.168.2.2 to server....then have the server assign ip's to the other boxes (currently only one) dynamically...does that make sense..or should I also assign static ips to the clients (192.168.2.3,4,5 etc...)-is there an advantage one way or the other?

 

[ivwshane]

YOur server needs to be static. Either have your server box do the DHCP work or have the router do it not both. Assign static ip's to things that won't change or that are needed on a frequent basis. So the router would geta static ip and so would your server, then any client would get a dynamic. However if you want them to be staic that's fine too but then what would you need the DHCP server for?

 

[milagro]

i'll just let the router take care of the dhcp-I mean deal w/ the dhcp coming from my isp via cable modem-and then have the router assign a static ip to the server...kinda like this

ISP ===>dynamic ip(###.###.###.###)<router>(192.168.2.1)=====>static ip (192.168.2.2)<server>===>dynamic ip's for clients

does that not make sense?

If there's a reason I shouldn't do that, maybe it will become apparent to me when I get home and attempt to configure things that way...before I confuse anyone more, i'll report back after I get home and make some changes...

 

[Saltin]

Yeah, honestly, if you only have a few clients, just nix the DHCP. You don't need it unless you want to mess/learn with it. I would only use DHCP (personally) for more than 20 clients. That's just me.

Fix your IP address issues, just go static all round.

Your real issue is DNS here. It's just waiting for you to get to it

 

[milagro]

yeah...basically trying to learn more "hands-on" about configuring DHCP within w2kserver..

well, I ended up just enabling the router as a DHCP server with a range of about 5 ip adresses...then I just selected an IP from that range on the server and the client....I've got connectivity no prob and everything is accessible...I've got various curiousities I've yet to answer/understand-but I guess I'll save those for other threads...thx for the help-you're helping me learn....