Menu
What's new
By:
Filters Better Search

DHCP problems with Ethernet

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

I've had similar issues with DHCP today after upgrading to 380.68.2. I had a problem with manual assigned IPs which didn't take affect. A quick google led me to disable IPv6 and WPS features. Then all my devices had problems with DHCP. Clients were dropping off and failing to get new leases and then after a short while successfully getting a lease and then dropping off etc... When I enabled IPv6 firewall and WPS features the DHCP issues did not occur.
 
Just figuring out the chronology of events:
1. Receiving of IP address on router is tagged by time 18:17. IP is received and I can connect to machine via RDP on WiFi.

O1ofFrL.png


2. Throwing the error at Windows log is tagged by 18:19

sOXEUXD.png


So the error is seems to thrown after the IP receiving? How that could be? The clocks on router and on Win machine are fully synchronized.

Do the above router log records are regarded as normal or there should be smth more?
 
And yes, it's not just the annoying message. I observe some non-functional OS features, such as built-in OneDrive or login via MS account:

8YDFXWz.png


I guess, that this could be related to DHCP.
 
Last edited:
Marko Polo said:
Do the above router log records are regarded as normal or there should be smth more?
Click to expand...
It's difficult to say for sure without seeing the unfiltered event log, but the errors shown suggest that there is a problem with the network adapter. Whether that is caused by the driver, any "utility" software also installed, or a physical problem (i.e. cables) is hard to know. Searching the internet for similar messages (there are lots) shows that some people have had success by installing different drivers (i.e. the default Microsoft drivers rather than the manufacturers).
 
The mac address posting the error is not registered (00-FF-2F), so it's probably a virtual adapter. Try a google search on error 0x79 and virtual adapter.
 
Also, there are problems with some of the VPN-connections. I see in OpenVPN client log:

Tue Sep 26 21:32:21 2017 SYSTEM ADAPTER LIST
Tue Sep 26 21:32:21 2017 TAP-Windows Adapter V9 #2
Tue Sep 26 21:32:21 2017 Index = 17
Tue Sep 26 21:32:21 2017 GUID = {2FE86F70-1989-4D59-8D1A-BFCE161C77F3}
Tue Sep 26 21:32:21 2017 IP = 169.254.128.144/255.255.0.0
Tue Sep 26 21:32:21 2017 MAC = 00:ff:2f:e8:6f:70
Tue Sep 26 21:32:21 2017 GATEWAY = 0.0.0.0/255.255.255.255
Tue Sep 26 21:32:21 2017 DHCP SERV = 0.0.0.0/255.255.255.255
Tue Sep 26 21:32:21 2017 DHCP LEASE OBTAINED = Tue Sep 26 21:32:21 2017
Tue Sep 26 21:32:21 2017 DHCP LEASE EXPIRES = Tue Sep 26 21:32:21 2017
Tue Sep 26 21:32:21 2017 DNS SERV =
Tue Sep 26 21:32:21 2017 TAP-Win32 Adapter OAS
Tue Sep 26 21:32:21 2017 Index = 15
Tue Sep 26 21:32:21 2017 GUID = {EAA89CB7-2F7F-4E80-8AB5-361C9BF1CF58}
Tue Sep 26 21:32:21 2017 IP = 169.254.105.84/255.255.0.0
Tue Sep 26 21:32:21 2017 MAC = 00:ff:ea:a8:9c:b7
Tue Sep 26 21:32:21 2017 GATEWAY = 0.0.0.0/255.255.255.255
Tue Sep 26 21:32:21 2017 DHCP SERV = 0.0.0.0/255.255.255.255
Tue Sep 26 21:32:21 2017 DHCP LEASE OBTAINED = Tue Sep 26 21:32:21 2017
Tue Sep 26 21:32:21 2017 DHCP LEASE EXPIRES = Tue Sep 26 21:32:21 2017
Tue Sep 26 21:32:21 2017 DNS SERV =
Tue Sep 26 21:32:21 2017 TAP-Windows Adapter V9
Tue Sep 26 21:32:21 2017 Index = 14
Tue Sep 26 21:32:21 2017 GUID = {E11F3954-2BEA-48BE-8B9C-C7A8C50B4933}
Tue Sep 26 21:32:21 2017 IP = 0.0.0.0/0.0.0.0
Tue Sep 26 21:32:21 2017 MAC = 00:ff:e1:1f:39:54
Tue Sep 26 21:32:21 2017 GATEWAY = 0.0.0.0/255.255.255.255
Tue Sep 26 21:32:21 2017 DHCP SERV =
Tue Sep 26 21:32:21 2017 DHCP LEASE OBTAINED = Tue Sep 26 21:32:21 2017
Tue Sep 26 21:32:21 2017 DHCP LEASE EXPIRES = Tue Sep 26 21:32:21 2017
Tue Sep 26 21:32:21 2017 DNS SERV =
Tue Sep 26 21:32:21 2017 Realtek PCIe GBE Family Controller
Tue Sep 26 21:32:21 2017 Index = 13
Tue Sep 26 21:32:21 2017 GUID = {D97ABF6E-CB82-4396-8874-0D2C2DB50998}
Tue Sep 26 21:32:21 2017 IP = 0.0.0.0/0.0.0.0
Tue Sep 26 21:32:21 2017 MAC = XXXXXXXXXXXX
Tue Sep 26 21:32:21 2017 GATEWAY = 0.0.0.0/255.255.255.255
Tue Sep 26 21:32:21 2017 DHCP SERV =
Tue Sep 26 21:32:21 2017 DHCP LEASE OBTAINED = Tue Sep 26 21:32:21 2017
Tue Sep 26 21:32:21 2017 DHCP LEASE EXPIRES = Tue Sep 26 21:32:21 2017
Tue Sep 26 21:32:21 2017 DNS SERV =
Tue Sep 26 21:32:21 2017 Microsoft Wi-Fi Direct Virtual Adapter
Tue Sep 26 21:32:21 2017 Index = 8
Tue Sep 26 21:32:21 2017 GUID = {276FA983-D997-4332-A6E3-C544D38683BF}
Tue Sep 26 21:32:21 2017 IP = 0.0.0.0/0.0.0.0
Tue Sep 26 21:32:21 2017 MAC = XXXXXXXXXXX
Tue Sep 26 21:32:21 2017 GATEWAY = 0.0.0.0/255.255.255.255
Tue Sep 26 21:32:21 2017 DHCP SERV =
Tue Sep 26 21:32:21 2017 DHCP LEASE OBTAINED = Tue Sep 26 21:32:21 2017
Tue Sep 26 21:32:21 2017 DHCP LEASE EXPIRES = Tue Sep 26 21:32:21 2017
Tue Sep 26 21:32:21 2017 DNS SERV =
Tue Sep 26 21:32:21 2017 Realtek 8821AE Wireless LAN 802.11ac PCI-E NIC
Tue Sep 26 21:32:21 2017 Index = 7
Tue Sep 26 21:32:21 2017 GUID = {0DD39889-2721-4D97-A872-F740FE32D701}
Tue Sep 26 21:32:21 2017 IP = 192.168.1.104/255.255.255.0
Tue Sep 26 21:32:21 2017 MAC = XXXXXXXXXXX
Tue Sep 26 21:32:21 2017 GATEWAY = 192.168.1.1/255.255.255.255
Tue Sep 26 21:32:21 2017 DHCP SERV = 192.168.1.1/255.255.255.255
Tue Sep 26 21:32:21 2017 DHCP LEASE OBTAINED = Tue Sep 26 21:28:35 2017
Tue Sep 26 21:32:21 2017 DHCP LEASE EXPIRES = Wed Sep 27 21:28:35 2017
Tue Sep 26 21:32:21 2017 DNS SERV = 192.168.1.1/255.255.255.255
Tue Sep 26 21:32:21 2017 Bluetooth Device (Personal Area Network)
Tue Sep 26 21:32:21 2017 Index = 4
Tue Sep 26 21:32:21 2017 GUID = {AF6F8E57-5A67-4924-A313-EDA9D304B0E1}
Tue Sep 26 21:32:21 2017 IP = 0.0.0.0/0.0.0.0
Tue Sep 26 21:32:21 2017 MAC = XXXXXXXXXXXX
Tue Sep 26 21:32:21 2017 GATEWAY = 0.0.0.0/255.255.255.255
Tue Sep 26 21:32:21 2017 DHCP SERV =
Tue Sep 26 21:32:21 2017 DHCP LEASE OBTAINED = Tue Sep 26 21:32:21 2017
Tue Sep 26 21:32:21 2017 DHCP LEASE EXPIRES = Tue Sep 26 21:32:21 2017
Tue Sep 26 21:32:21 2017 DNS SERV =
Tue Sep 26 21:32:21 2017 Initialization Sequence Completed With Errors ( see http://openvpn.net/faq.html#dhcpclientserv )
Tue Sep 26 21:32:21 2017 MANAGEMENT: >STATE:1506450741,CONNECTED,ERROR,10.211.1.49,109.173.85.239,1195,,
Click to expand...

So the initialization sequence is not successful. 00:ff:2f:e8:6f:70 seems to be TAP-Windows Adapter V9.

Also there are errors Route: Waiting for TUN/TAP interface to come up.

Code: 
Tue Sep 26 21:31:51 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:31:51 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:31:52 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:31:52 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:31:53 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:31:53 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:31:55 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:31:55 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:31:57 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:31:57 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:31:58 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:31:58 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:00 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:00 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:01 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:01 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:03 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:03 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:04 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:04 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:06 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:06 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:07 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:07 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:08 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:08 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:09 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:09 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:10 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:10 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:11 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:11 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:12 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:12 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:13 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:13 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:14 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:14 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:15 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:15 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:16 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:16 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:18 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:18 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:19 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down
Tue Sep 26 21:32:19 2017 Route: Waiting for TUN/TAP interface to come up...
Tue Sep 26 21:32:21 2017 TEST ROUTES: 0/0 succeeded len=-1 ret=0 a=0 u/d=down

According to old forums this error is caused by DHCP service failures.
 
Marko Polo said:
So the initialization sequence is not successful. 00:ff:2f:e8:6f:70 seems to be TAP-Windows Adapter V9.
Click to expand...
Actually it's "TAP-Windows Adapter V9 #2"

According to old forums this error is caused by DHCP service failures.
Click to expand...
I can't see that in the link. They asked whether DHCP was running, it was, so that was not the cause.

I would suggest the same approach as comment #7 in that thread. Uninstall OpenVPN and both TAP adapters, but before reinstalling OpenVPN check whether the messages have disappeared.
 
Last edited:
ColinTaylor said:
I would suggest the same approach as comment #7 in that thread. Uninstall OpenVPN and both TAP adapters, but before reinstalling OpenVPN check whether the messages have disappeared.
Click to expand...

Well, I've done that and messages seems to disappear. However, there are another odd messages in the log:

The name "WORKGROUP :1d" could not be registered on the interface with IP address 192.168.1.104. The computer with the IP address 192.168.1.100 did not allow the name to be claimed by this computer.
Click to expand...

The browser was unable to promote itself to master browser. The computer that currently believes it is the master browser is PCHOME.
Click to expand...

I believe the above messages are related to DHCP too.
 
The first hit in Google for that error message suggests that it could be caused by using a VPN and/or having both physical and virtual adapters connected at the same time. I'd have thought that the IP addresses might have made the cause apparent.
 
ColinTaylor said:
The first hit in Google for that error message suggests that it could be caused by using a VPN and/or having both physical and virtual adapters connected at the same time.
Click to expand...

But this time my VPN TAP adapters were deleted (as well as OpenVPN) and messages were showed anyway. Additionally on the other PC there are no problems with NetBIOS, despite they are connected to the same router and the same LAN. It's very odd.
 
You must log in or register to reply here.

Similar threads

C
Router trouble RT-AX88U
Replies
5
Views
636
ciprian.trofin
C
T
Smart Life Device Keeps Disconnecting Daily
Replies
1
Views
211
techdiver
T
J
Device all of a sudden is assigning itself a 169.254 IP address when coming out of standby
2
Replies
36
Views
2K
JTnola
J
T
Having some problems with my home network. Please Help!
Replies
3
Views
844
triggerh4ppy
T
cherio
(RT-AX88U/Latest Merlin 388.1) Takes 5 min to apply any Wireless setting
Replies
3
Views
1K
OzarkEdge
OzarkEdge
Similar threads
Thread starter Title Forum Replies Date
S Moving DHCP to Pi-Hole Asuswrt-Merlin 2
C LAN > DHCP List - Manually Assigned Name + Icon DONT SAVE Asuswrt-Merlin 4
garycnew [SOLUTION] WAN_Connection: ISP's DHCP did not function properly Asuswrt-Merlin 2
Philip Bondi Intermittent problem with DHCP offering 10.x addresses when configured for 192.x Asuswrt-Merlin 3
C Need some help with a DHCP problem Asuswrt-Merlin 9
A Inconsistencies and broken behavior with client status and DHCP leases - AX86UP 388.6_2 Asuswrt-Merlin 17
P Solved Router DHCP and DNS not responding to changes Asuswrt-Merlin 35
mekki Solved UPDATE: No longer required. See thread. - [Feature request] Option for DHCP Query Frequency Backoff Mode Asuswrt-Merlin 76
J Need to disable ipv6 dhcp server ip auto assignments in my lan. but leave ipv6 turned on for wan side. Asuswrt-Merlin 8
K Need help with a bad DHCP issue!!!! Asuswrt-Merlin 6

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Staff online

Members online

Total: 776 (members: 41, guests: 735)
Top