Windows 2000 Domain and cable modem network

How would one go aboutting up a Windows 2000 domain network with a cablemodem and router? here's the topology:


CABLE MODEM
|
ROUTER
/ | \
SERVER C1* C2*


C1/C2 = Client 1/2

Router is in gateway mode. Server is running Win 2K Server, C1/2 Windows XP Pro.


Justin

So are you having some problem? Your diagram should work fine.

WEll not anymore, what was happening was the DNS/Domain server was arguing with Comast's DNS server for control, i setup my DNS server as a non-root server and added Comcast's DNS servers to the forwarding list, then setup the client machines to use the DNS address of my server.


JUstin

Did you ever get a solution to the DNS issue and setup config in order to get your network to function properly?
I'll let you in on my issue when I did that too...

After I setup our network like that over 4-5 month ago for a small business we unfortunately had a server hardware failure and after replacing the hardware the 7 users on the network (all win2000 pro desktop, win2000 server w/ DNS, WINS, ICS and Active Dir.) began to notice thier web was very slow and that pages timed out on them etc. After trying solution after solution to fix this, I noticed the activity lights on the cable modem in extremely heavy use, even if the cable modem was disconnected from any connection past itself (example from the wall to the coax to the cable modem, thats it!) So why was activity so extreme when there was no traffic that could travel past the modem?? So I ran a CommView program to sniff all incoming/outgoing traffic and noticed *heavy* port 137 traffic (and a few others). Have my DNS records been updated and propogated somehow to share comcast's dynamically somehow because I put their forwarding DNS entries? Was the traffic looking for a certain MAC address I owned? Although I've been in the IT industry for many many years, I've never seen this before. And well I can't exactly call Comcast and complain that thier traffic is screwing up my DNS server, so after calling and complaining to tech support about heavy traffic and slow connections they sighed in disgust that I would attempt to bother them over such trivial problems, as if I had a right to ask them to do ANY work?!! After 2 calls in and one lady unexpectedly putting me on hold until I hung up (so her call center would see that SHE hung ME up in her support log) I'm going to try and select "Disable NetBIOS over TCP/IP" and see if that works tomorrow.

Did/has anyone have this same problem?? Im still wondering what is wrong...if this doesn't work then I'm going to a more private and less public internet line like DSL.

Thanks,
Justin L

justintd: In your second post, you indicated that you where able to solve the problem by modifying your DNS structure. Can you be more specific as to what you did? I seem to be havving the same problem and, while I'm no DNS expert, I don't want to really mess things up. Currently have the same topology that you described. I have my router configured as a DHCP server. My server currently has Windows 2003 AD and I have created it's own domain that I want to use for my home: "network.home" The problem is that my clients cannot resolve network.home. I'm sure there is some issue with configuring the router to somehow point to the server as a DNS and then have the server go back to the router, but I'm not sure how to do that... any help would be greatly appreciated.