Domain Login Through Router?

[qfkeon]

I would like to set up 3 machines on my network so that they are not visible to other users. I am trying to figure out how to enable these machines to authenticate login information and map to network shares through a Linksys 4-port DSL router.

My current setup that does not seem to work has the router getting its 192.168.1.x WAN IP address through DHCP from the Windows 2000 Server. The router's IP as viewed by the 3 machines is 192.168.2.1 and it is providing DHCP to those machines. The entire network also passes through a Linksys Router to access the Internet.

I can access the Internet with my current setup and I can ping my 2000 server, but I cannot seem to login to my server.

I will greatly appreciate any help.

Q

 

[YokyDoky]

You can only have one DHCP server on a segment, so you're going to have to decide which one to axe. I've ran it both ways; using the Linksys as the DHCP server seems to be less maintenance. My question is, why bother with DHCP on a LAN with only a few clients? Hardcode all IPs including the router and forget about DHCP altogether. Here's my scheme: router is 192.168.1.1 (default). Server is x.x.x.2, workstations go up from there, including one wireless client. The server authenticates logons (Domain controller), is the DNS server, no WINS used. I wouldn't use DHCP unless you have more than 20 or so clients. If you have portables that come and go, you can use DHCP to hand them addresses and start the DHCP range above the addresses you have hardcoded for your stationary clients. I know this much: the router MUST have a static IP for the private LAN.

Y. Doky - "Manager" of Systems

"A .22 caliber intellect in a .357 Magnum world."

 

[qfkeon]

Thank you for the response. This network has 40+ machines on it. I want to separate 3 of the machines so that their shares are not visible to the rest of the network. I also want to allow these machines to logon to the same server as the rest of the network. I thought I could use a router to hide the machines and still be able to access the rest of the network.

Q

 

[efcusa88]

If the boxes you want to separate are windows 2000 or XP you can set up the filters so that no other machines can access them.

 

[qfkeon]

Thank you for the response. That is what I ended up doing. I set up a workgroup for the 3 machines and set like names and passwords on each. I then disabled the option to allow anonymous enumeration. This seems to work okay. I also have matching user name and password information on the domain controller that these machines need to connect to so that when they try to access a shared resource, their credentials are authenticated.

 

[chupie]

Hello, i have somewhat of the same problem.. I have recently set up a linksys wireless router in a computer lab, i have sucessfully got the internet to work through it, but am not able to login to the local domain. the main network uses static ips, and so does the router, is it even possible to login to the domain through the router?

 

[bcastner]

The fact that the connection to a Domain is wireless should be completely unimportant.

What exactly are the error messages you receive in Event Viewer?

Start with the issues raised if faq779-4017
From the sounds of it, you are using the Linksys router to provide internet service on a private LAN IP different than the Domain.

Be carefull here as well: unless you intend to isolate the wireless from the wired, and offer a second DHCP server, things can get messy.

If you wireless router is offering IPs that are in a different subnet from your lan, you need to take additional steps in a Domain setting to have these IPs registered.