techies123
asked on
DHCP Issue Server not on address pool
Fo reasons only known to BT I have had to give a domain controller server 2003. A public IP address and route to it using a BT "Business" Hub. As they dont support NAT. After that my DHCP has stopped working? range being 191.168.100.10 to .254. The server is now out of this range. Do i need a superscope. All other non BT ADSL networks i work on have the server within the scope
ASKER
It was because the client had a range of 5 ip's i had to set up the public IP against the MAC address of the server. The only way it could be done apparently!
too advoid cabling
how do i do
You could add two IPs on the same network interface
?
too advoid cabling
how do i do
You could add two IPs on the same network interface
?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Just need DHCP to work on Single NIC with the server with a public IP and clients internal IP?
how are you connecting the clients to the server if all the server has is a public IP?
Within the configuration of the network interface on the server, add a second IP that is on the same segment as the LAN
This way you will have an IP in each.
localarea connection
pulbicIP Public_netmask Public_ip_default_gateway
192.168.100.1 255.255.255.0
In the DHCP scope, presumably you will be pushing the default gateway as the IP on the DHCP server.
Within the configuration of the network interface on the server, add a second IP that is on the same segment as the LAN
This way you will have an IP in each.
localarea connection
pulbicIP Public_netmask Public_ip_default_gateway
192.168.100.1 255.255.255.0
In the DHCP scope, presumably you will be pushing the default gateway as the IP on the DHCP server.
ASKER
Have added the 192.168.100.1 to the network card of the server. Will have to test tomorrow if it will work.
I am pushing the DG as the router address which is the router IP
Thanks
I am pushing the DG as the router address which is the router IP
Thanks
The internal IPs have no path to the router IP as the default gateway.
All they know is 192.168.100.x
Since the router does not do NAT, it has no idea where 192.168.100.x is or how to get to it.
It would be similar to me telling you go to 100 main street
Without the town information, the above reference is meaningless.
All they know is 192.168.100.x
Since the router does not do NAT, it has no idea where 192.168.100.x is or how to get to it.
It would be similar to me telling you go to 100 main street
Without the town information, the above reference is meaningless.
Not sure what the issue is that lead them to tell you to make such adjustments.
The issue with superscopes, you would need to have a relay agent that would mark the segment on which the IP is to be allocated.
You could add two IPs on the same network interface.
It is rather peculiar that you now have your DC exposed to the net.