• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Domain and Router through a 5port Switch?

C

chris101

Junior Member
Guys I have just setup a domain and want it to join the internet.
The Domain is in a seperate room to where the router is.

I have decided the best way would be to connect my domain to the switch and allow its clients to connect through the switch however with regards to the router, I am not sure how I can add this to the setup.

I would like to grant internet access to the network and was going to use a wireless homeplug to connect to the switch but im not sure if this is possible as the uplink port would be connected the server?

Any ideas how I could get this setup to work please?
 
chris101 said:
Sorry I meant windows server 2008. I want to use it as a ad controller and dhcp server.
Click to expand...

You would configure the router like normal. It has no effect on the Windows Domain. Disable the DHCP on it and have the domain controller do DNS and DHCP. Point the clients at the domain server for DNS. The domain controller will use the root servers unless you specify forwarders.

All the internal clients and servers should use domain DNS.

Do you have specific questions?
 
Thank you for your response.

My question is -

My router is located in another area which cannot connect to the server, hence no internet.

I want to be able to connect 3 client pc's and router to share internet to the server and clients.


From my understanding this would be done through a switch but as my router is located in a place that cannot reach the server or switch, I was planning on buying a wireless home plug where the receiver connected into the switch and transmitter connected to the router.

Would this be the best way?
 
chris101 said:
Thank you for your response.

My question is -

My router is located in another area which cannot connect to the server, hence no internet.

I want to be able to connect 3 client pc's and router to share internet to the server and clients.


From my understanding this would be done through a switch but as my router is located in a place that cannot reach the server or switch, I was planning on buying a wireless home plug where the receiver connected into the switch and transmitter connected to the router.

Would this be the best way?
Click to expand...

Something like that would work. Wireless / powerline / MOCA / Pull cat5. Those are all layer 1 / 2 techs that wouldn't have any effect on Windows Domains.
 
while waiting for my additional home plug and switch I decided to test out my server on the internet using the existing home plug I use for my TV.

I setup the reciever end of the homeplug through the ethernet port on the server and configured the router to relay the DHCP server to the win2k8 DHCP server and I set the IP address of the router to make sure its on the same ip format as the 2k8 server - 192.168.10.

Now on the 2k8 server I setup the gateway as the routers ip - 192.168.10.2 and the server is working fine on the internet however the clients are able to get an IP address from the 2k8 DHCP server but not connect to the internet.

Any ideas what the issues might be?

In case I have not been clear this is the basic setup -

Router (192.168.10.2) is setup with DHCP relay to the win2k8 server (192.168.10.201)

However any client that is setup to obtain IP Address automatically, get an ip address from the win2k8 server (e.g. 192.168.10.102) but still not able to get on the internet.
 
do:

ipconfig /all

post it here. Sounds like DNS on the 2k8 machine is not [potentially] setup correctly. The AD server should have DNS of itself and no other addresses* if you have multiple AD servers this changes but I am assuming one at the moment.
DNS the needs to be set to use the root servers or lesser preferred referrers. The client machines need to point at the 2k8 server for DNS.

Also DHCP relay? That normally means "dhcp-helper" which is handling DHCP requests across many subnets. What do you define it as? Normally the 2k8 machine will handle DHCP and the internet router will have that part disabled.
 
I think im making a stupid school boy error.

The clients are still trying to connect through the router as I do not have a switch yet.

There is an option on my router that says DHCP Relay, which is why I thought I can relay it to the win2k8 DHCP server and still access the internet.

Is this not the case then?
 
Server Ip Config -
Windows IP Configuration
Host Name . . . . . . . . . . . . : AA-DC1-2K8
Primary Dns Suffix . . . . . . . : home.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home.net
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82566DM Gigabit Network Connecti
on
Physical Address. . . . . . . . . : 00-1E-4F-DF-2F-AE
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.10.201(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.10.1
DNS Servers . . . . . . . . . . . : 192.168.10.201
NetBIOS over Tcpip. . . . . . . . : Enabled
 
Client IP -

Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : home.net
Description . . . . . . . . . . . : Intel(R) Wireless WiFi Link 4965AGN
Physical Address. . . . . . . . . : 00-22-5C-92-EB-45
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.10.108(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 04 May 2012 19:35:04
Lease Expires . . . . . . . . . . : 10 May 2012 19:35:04
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.10.201
DNS Servers . . . . . . . . . . . : 192.168.1.201
NetBIOS over Tcpip. . . . . . . . : Enabled
 
However when I change the settings to static and add the gateway ip to 192.168.10.1 and DNS server to 192.168.10.1, only then internet works.

I have tried leaving DNS blank or gateway blank, but both have to be on the routers IP for it to work.

Any ideas?
 
chris101 said:
I think im making a stupid school boy error.

The clients are still trying to connect through the router as I do not have a switch yet.

There is an option on my router that says DHCP Relay, which is why I thought I can relay it to the win2k8 DHCP server and still access the internet.

Is this not the case then?
Click to expand...

DHCP-relay would be used to relay DHCP requests from lan to wan. You should not use that there. Disable DHCP completely. Also yes the machines have to be on the same LAN as the DC. If they are simply not connected that would causes issues.
 
We are typing over each other...

Why does that one machine have a gateway of 192.168.1.1? that is not in the same subnet as 192.168.10.0/24. The DNS server is also 192.168.1.201. That would cause DNS to fail hard also.
 
Can you do a rough sketch of your network? You have 2 network ranges in there and I want to know if there is a reason for that. Maybe I misunderstood and you do have a real router in the mix someplace?

I was thinking
Code: 
Internet router
   |---- clients
   |---- server.
A switch would just give you more ports.
 
Apologies. I will try to be a little more clearer.

The 192.168.1.1 is auto appearing as ive setup the NIC to auto obtain IP.

Here is the sketch -

Win2k8 DHCP Server (192.168.10.201)
|
Wireless Router (192.168.10.1)
|
Clients (Obtain IP Address auto from DHCP through router, if possible?)
 
I have no idea as I didn't set it up. It must be one of the settings through the router or somewhere, as its set to obtain automatically?
 
chris101 said:
I have no idea as I didn't set it up. It must be one of the settings through the router or somewhere, as its set to obtain automatically?
Click to expand...

Ok, I think you might have this setup in a more complex way than needed. Is there a reason to isolate the domain from the other PC's? It should like there is a router for internet and another router someplace in the middle between the DC's and the DC machines. You only need a router when going between network segments, otherwise you just need a switch. Don't use the "WAN" port on the wireless router between the domain and clients.
 
Last edited:
The problem being I currently do not have a switch.

The server has only one NIC so the router is connected to it and the 2 clients are wirelessly connecting to the router which is relaying the DHCP to the domain.

I am able to ping between the client, server and router however just unable to get the internet up on the clients (Internet working on the server)?
 
chris101 said:
The problem being I currently do not have a switch.

The server has only one NIC so the router is connected to it and the 2 clients are wirelessly connecting to the router which is relaying the DHCP to the domain.

I am able to ping between the client, server and router however just unable to get the internet up on the clients (Internet working on the server)?
Click to expand...

I am trying to simplify this because I think you made a lot of progress, possibly in the wrong direction.

Ok I think I see how this is working. First don't plug anything in to the WAN port. The server should be on "LAN." This will let the DHCP requests go out over the wireless. The goal is to get all these devices on one "network" [ie subnetwork] while still getting Internet to all devices. From there it sounds like you are using a router as way to bridge to locations where you can't cable it.

Using only the LAN ports on the server "router" will still allow you to bridge but it will remove the router / nat that is going on between the 2 devices.

sounds like you have:
192.168.10.0/24:

Server ----- Wireless router --- [wifi] --- Wireless Internet router [192.168.1.1/24]---- clients .

Does this sum the physical topology?
 
Last edited:
The physical topology is as follows (apologies for being very basic, as all this is pretty new to me).

Clients ----> Wireless Internet Router (192.168.10.1) -----> Windows Server 2008 (192.168.10.201)

The clients connect through to the wireless internet router which has a dhcp relay to the windows server 2008 IP address.

The wan port has to be connected as thats where the Internet is being sourced from however, form your diagram and my basic understanding, it seems to me you understood I had two routers?
 
chris101 said:
The physical topology is as follows (apologies for being very basic, as all this is pretty new to me).

Clients ----> Wireless Internet Router (192.168.10.1) -----> Windows Server 2008 (192.168.10.201)

The clients connect through to the wireless internet router which has a dhcp relay to the windows server 2008 IP address.

The wan port has to be connected as thats where the Internet is being sourced from however, form your diagram and my basic understanding, it seems to me you understood I had two routers?
Click to expand...

Yeah ok that makes sense why you are having issues with the clients and the internet.

Basically you would need to set up the proper routing inside the network for them to connect. You do not want to relay but here is going to be the hard part. You need a cohesive DNS set up for AD to work. The clients off in the 192.168.1.0/24 area need to be told to get DNS from 192.168.10.201, however you wish to do it. Now typically you would set DHCP on that range to hand out address like this: scope 192.168.1.0/24 gateway 192.168.1.1 DNS: 192.168.10.201. From there the internet router (192.168.1.1) needs a route [typically a static route in a small net like yours) saying "192.168.10.0/24 [ip address of the other router]"

The issue for you is the devices in 192.168.1.0/24 will starting using your DC for DNS if configured that way. Your router that is connecting 192.168.10.0/24 and 192.168.1.0/24 should run in routed mode and not NAT. You then enter a static route for 0.0.0.0 -> 192.168.1.1.

Makes sense? Do you have control to make changes to 192.168.1.0/24 or is that some other network? The easy solution is to make sure the clients are inside the 192.168.10.0/24 network. If this is just your home network I would eliminate the 192.168.10.0/24 router entirely [the routed part at least, you can still use the bridge part]
 
Unfortuantely my router (Billion BiPAC 7800N), doesn't have a routing mode or birdge mode, not one obvious to find anway.

So I need to congifure the internet router to route to the DHCP sever on win2k8 via static IP?

This is all done in a test lab so I have control over the whole setup.
 
Just found a old wireless usb dongle which I have connected to the server and enabled it on the internet.

So now thats effectively acting as the 2nd NIC for internet.

Would this be the best way of setting it up now?

Server 2008
|--------|
NIC1----NIC2
|---------|
Switch--Internet (Wireless Router)
|
Clients


Until I get my switch, is there any way I could test my setup?

Maybe connecting my trasnmitter homeplug into the server 2k8 and reciever homeplug into one of the clients?
 
Last edited:
You must log in or register to reply here.

TRENDING THREADS

Back
Top