I have a RED 50 at a remote site which is not giving out IP DHCP addresses to clients on remote VLAN.
When I view the LIVE LOG for DHCP on the UTM 9 I can see requests coming in from the clients and IP addresses being offered but they are not getting to the clients.
I have 5 other sites that are working fine with the same set-up. Let me qualify that, I have one other site with a RED 50 that is working fine and 4 others with RED 15's that are working fine. IP's are being requested, offered, and received.
I am relatively new at this position but I am told that this was working for quite some time and then quit working without explanation.
This is my livelog from the site not receiving IP's.
2018:10:24-07:23:56 publicfw dhcpd: DHCPOFFER on 172.22.81.190 to 3c:2e:f9:80:f7:d4 (iPhone) via reds1
2018:10:24-07:24:04 publicfw dhcpd: DHCPDISCOVER from 3c:2e:f9:80:f7:d4 (iPhone) via reds1
2018:10:24-07:24:04 publicfw dhcpd: DHCPOFFER on 172.22.81.190 to 3c:2e:f9:80:f7:d4 (iPhone) via reds1
2018:10:24-07:24:12 publicfw dhcpd: DHCPDISCOVER from 3c:2e:f9:80:f7:d4 (iPhone) via reds1
2018:10:24-07:24:12 publicfw dhcpd: DHCPOFFER on 172.22.81.190 to 3c:2e:f9:80:f7:d4 (iPhone) via reds1
2018:10:24-07:24:16 publicfw dhcpd: DHCPDISCOVER from 40:9c:28:76:b8:9c (iPhone) via reds1
2018:10:24-07:24:16 publicfw dhcpd: DHCPOFFER on 172.22.81.234 to 40:9c:28:76:b8:9c (iPhone) via reds1
2018:10:24-07:24:17 publicfw dhcpd: DHCPDISCOVER from b4:8b:19:73:2f:cd (iPhone) via reds1
2018:10:24-07:24:18 publicfw dhcpd: DHCPOFFER on 172.22.81.213 to b4:8b:19:73:2f:cd (iPhone) via reds1
2018:10:24-07:24:19 publicfw dhcpd: DHCPDISCOVER from b4:8b:19:73:2f:cd (iPhone) via reds1
2018:10:24-07:24:19 publicfw dhcpd: DHCPOFFER on 172.22.81.213 to b4:8b:19:73:2f:cd (iPhone) via reds1
2018:10:24-07:24:21 publicfw dhcpd: DHCPDISCOVER from 3c:2e:f9:80:f7:d4 (iPhone) via reds1
This is the livelog from the other site I have with a red 50 that is working just fine.
2018:10:24-07:26:46 publicfw dhcpd: DHCPDISCOVER from bc:a9:20:f2:81:fb (iPhone-2) via reds2
2018:10:24-07:26:47 publicfw dhcpd: DHCPOFFER on 10.237.89.210 to bc:a9:20:f2:81:fb (iPhone-2) via reds2
2018:10:24-07:26:49 publicfw dhcpd: DHCPREQUEST for 10.237.89.210 (10.237.88.1) from bc:a9:20:f2:81:fb (iPhone-2) via reds2
2018:10:24-07:26:49 publicfw dhcpd: DHCPACK on 10.237.89.210 to bc:a9:20:f2:81:fb (iPhone-2) via reds2
2018:10:24-07:27:27 publicfw dhcpd: DHCPREQUEST for 10.237.88.133 from 88:66:a5:52:cc:2b (iPhone) via reds2
2018:10:24-07:27:27 publicfw dhcpd: DHCPACK on 10.237.88.133 to 88:66:a5:52:cc:2b (iPhone) via reds2
2018:10:24-07:27:42 publicfw dhcpd: DHCPDISCOVER from 00:34:da:01:7a:95 (android-c0c8dfa223031c31) via reds2
2018:10:24-07:27:43 publicfw dhcpd: DHCPOFFER on 10.237.88.138 to 00:34:da:01:7a:95 (android-c0c8dfa223031c31) via reds2
2018:10:24-07:27:46 publicfw dhcpd: DHCPDISCOVER from 00:34:da:01:7a:95 (android-c0c8dfa223031c31) via reds2
2018:10:24-07:27:47 publicfw dhcpd: DHCPOFFER on 10.237.88.138 to 00:34:da:01:7a:95 (android-c0c8dfa223031c31) via reds2
2018:10:24-07:27:47 publicfw dhcpd: DHCPREQUEST for 10.237.88.138 (10.237.88.1) from 00:34:da:01:7a:95 (android-c0c8dfa223031c31) via reds2
2018:10:24-07:27:47 publicfw dhcpd: DHCPACK on 10.237.88.138 to 00:34:da:01:7a:95 (android-c0c8dfa223031c31) via reds2
2018:10:24-07:27:58 publicfw dhcpd: DHCPREQUEST for 10.237.88.67 from 00:b3:62:86:36:9f (JadaAnnsiPhone) via reds2
2018:10:24-07:27:58 publicfw dhcpd: DHCPACK on 10.237.88.67 to 00:b3:62:86:36:9f (JadaAnnsiPhone) via reds2
2018:10:24-07:27:58 publicfw dhcpd: DHCPREQUEST for 10.237.88.67 from 00:b3:62:86:36:9f (JadaAnnsiPhone) via reds2
2018:10:24-07:27:58 publicfw dhcpd: DHCPACK on 10.237.88.67 to 00:b3:62:86:36:9f (JadaAnnsiPhone) via reds2
2018:10:24-07:28:11 publicfw dhcpd: DHCPDISCOVER from 04:d6:aa:5c:4d:1d via reds2
2018:10:24-07:28:12 publicfw dhcpd: DHCPOFFER on 10.237.90.47 to 04:d6:aa:5c:4d:1d (SAMSUNG-SM-G930V) via reds2
2018:10:24-07:28:12 publicfw dhcpd: DHCPDISCOVER from 04:d6:aa:5c:4d:1d (SAMSUNG-SM-G930V) via reds2
2018:10:24-07:28:12 publicfw dhcpd: DHCPOFFER on 10.237.90.47 to 04:d6:aa:5c:4d:1d (SAMSUNG-SM-G930V) via reds2
2018:10:24-07:28:18 publicfw dhcpd: DHCPDISCOVER from 04:d6:aa:5c:4d:1d (SAMSUNG-SM-G930V) via reds2
2018:10:24-07:28:18 publicfw dhcpd: DHCPOFFER on 10.237.90.47 to 04:d6:aa:5c:4d:1d (SAMSUNG-SM-G930V) via reds2
2018:10:24-07:28:19 publicfw dhcpd: DHCPDISCOVER from 28:a0:2b:10:56:c8 via reds2
2018:10:24-07:28:20 publicfw dhcpd: DHCPOFFER on 10.237.89.20 to 28:a0:2b:10:56:c8 (awes2iP1103GRY5) via reds2
2018:10:24-07:28:21 publicfw dhcpd: DHCPREQUEST for 10.237.89.20 (10.237.88.1) from 28:a0:2b:10:56:c8 (awes2iP1103GRY5) via reds2
2018:10:24-07:28:21 publicfw dhcpd: DHCPACK on 10.237.89.20 to 28:a0:2b:10:56:c8 (awes2iP1103GRY5) via reds2
2018:10:24-07:28:25 publicfw dhcpd: DHCPDISCOVER from 04:d6:aa:5c:4d:1d (SAMSUNG-SM-G930V) via reds2
2018:10:24-07:28:25 publicfw dhcpd: DHCPOFFER on 10.237.90.47 to 04:d6:aa:5c:4d:1d (SAMSUNG-SM-G930V) via reds2
I don't know where to look to find out why the discover and offer are going through the UTM but not getting back to the client.
Any assistance would be greatly appreciated.
Thank you.
This thread was automatically locked due to age.
