I have successfully setup a DHCP server with radius authenciation but i need help for route it
I want to setup a network like this
windows 2008 server IP 172.16.0.111
|
Mikrotik WAN IP 172.16.0.5
DHCP SERVER LAN IP 172.16.0.1
|
cisco switch
__________|________
| |
DHCP client DHCP client
172.16.0.2 172.16.0.3
In this design clients have successfully connected to DHCP server but can anyone help me to connect them to windows server 172.16.0.111
I have not done any kind of route yet please tell me if necessary
This will not work because your wan and lan interfaces on the mikrotik are in the same contiguous IP Network. You either bridge the wan and lan and place their common IP on the bridge interface or use different IP subnets for the wan and lan.
A little reading on TCP/IP will also do some good.
Thanks skillfull for reply. i have understood that same subnet will not work on both interfaces.
but if i bridge then all users (manully ip configured) will get connected to 2008 server & i want only dhcp connected users can only get connected.
I am lil confused about it so can you help me further…
I am ready to change any ips & subnet but please help me so my dhcp users can get connected to 2008 server.
is there any need to do static route in 2008 server???
Configure DNS on mikrotik and set primary dns to 172.16.0.111. Also, allow remote request.
/ip dns
set allow-remote-requests=yes cache-max-ttl=1w cache-size=2048KiB max-udp-packet-size=512 primary-dns=172.16.0.111 secondary-dns=208.67.222.222
Configure DHCP server for lan interface and set add-arp=yes
now my users are connected to some other DHCP servers running on my networks. so, can you help me to configure multiple relay on 1 dhcp servers i have more then 3000 users on my LAN so this design will be safe???
still m not getting ping reply from 172.16.1.111 & 172.16.1.1
please comment & any help will be appreciateable
Thanks skillful i tried but nothing happen coz i want /16 for my dhcp network
You cannot have 172.16.0.0/16 on your lan interface if you have 172.16.1.0/24 on your wan.
Follow the instructions in my earlier post but change your wan address range to 192.168.1.0/24 if you must retain 172.16.0.0/16 on your lan. For instance, replace all 172.16.1.1/24 with 192.168.1.1/24 and 172.16.1.111/24 with 192.168.1.111/24. Furthermore, all your 172.16.x.x IP addresses must have a /16 subnet. The DHCP Server should not lease out /16 range while the lan interface is /24.
All you need to do is contained in my earlier post, just replace the IP address with the appropriate one.
From your post, it is obvious that your knowledge of IP Networking is very poor. Do yourself some good by reading up IP Networking and sub-netting.
[admin@AXiS] interface> print
Flags: X - disabled, D - dynamic, R - running
# NAME TYPE RX-RATE TX-RATE MTU
0 R LAN ether 0 0 1500
1 R WAN ether 0 0 1500
[admin@AXiS] ip address> print detail
Flags: X - disabled, I - invalid, D - dynamic
0 address=172.16.0.1/16 network=172.16.0.0 broadcast=172.16.255.255 interface=LAN actual-interface=LAN
1 address=192.168.202.111/24 network=192.168.202.0 broadcast=192.168.202.255 interface=WAN actual-interface=WAN
What IP address do you have on the windows server? Can you ping 192.168.222.1 from the Router? Make sure there is no firewall blocking ICMP on the windows 2008 system.
[admin@AXiS] ip route> print detail
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf
0 ADC dst-address=172.16.0.0/16 pref-src=172.16.0.1 interface=LAN scope=10 target-scope=0
1 ADC dst-address=192.168.202.0/24 pref-src=192.168.202.111 interface=WAN scope=10 target-scope=0
[admin@AXiS] ip arp> print detail
Flags: X - disabled, I - invalid, H - DHCP, D - dynamic
0 H address=172.16.0.68 mac-address=XX:00:XX:18:XX:75 interface=LAN
1 H address=172.16.0.67 mac-address=00:XX:2E:0B:XX:B3 interface=LAN
2 H address=172.16.0.64 mac-address=00:02:XX:8C:XX:CD interface=LAN
3 H address=172.16.0.62 mac-address=00:15:XX:E0:XX:13 interface=LAN
4 H address=172.16.0.63 mac-address=00:01:XX:12:22:XX interface=LAN
5 H address=172.16.0.65 mac-address=XX:15:XX:28:XX:09 interface=LAN
6 H address=172.16.0.69 mac-address=00:19:XX:9D:B6:XX interface=LAN
7 H address=172.16.0.60 mac-address=00:1C:XX:31:01:XX interface=LAN
8 H address=172.16.0.59 mac-address=00:1D:XX:45:XX:A3 interface=LAN
9 H address=172.16.0.58 mac-address=00:01:XX:13:XX:76 interface=LAN
10 D address=192.168.202.1 mac-address=00:XX:20:XX:15:XX interface=WAN
ospf debug Hello sent to 224.0.0.5 via [eth1:192.168.202.111]
ospf debug Hello sent to 224.0.0.5 via [eth1:192.168.202.111]
ospf debug Hello sent to 224.0.0.5 via [eth0:172.16.0.1]
ospf debug Hello sent to 224.0.0.5 via [eth0:172.16.0.1]
[admin@AXiS] ip route> print detail
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf
0 ADC dst-address=172.16.0.0/16 pref-src=172.16.0.1 interface=LAN scope=10 target-scope=0
1 Do dst-address=172.16.0.0/16 scope=20 target-scope=10
2 ADC dst-address=192.168.202.0/24 pref-src=192.168.202.111 interface=WAN scope=10 target-scope=0
3 Do dst-address=192.168.202.0/24 scope=20 target-scope=10
4 A S ;;; Default Route
dst-address=0.0.0.0/0 gateway=192.168.202.1 interface=WAN gateway-state=reachable distance=1 scope=30
target-scope=1
