@Michael234 from what you describe, I would think that what you are experiencing is a different problem with similar symptoms. The problem diagnosed in this thread on the MK3, stemming from the leak of certain LAN traffic to the WAN port under certain configurations (when you have LAN physical ports set to other than Trunk/Any on the SOHO), is usually exacerbated by booting the cable modem while the SOHO is live. In fact, this is when the cable modem rebooted/re-acquired the cable signal unattended while the SOHO was live that caused the issue to be detected in the first place. In that case, unplugging the up-link to the modem, rebooting the modem and then reconnecting the up-link was a valid recovery mechanism, that succeeded most of the times (technically there was still a small time window for it to fail now that we understand the root cause, but in practice I only had it fail a handful of times compared to 10s of successes).
One quick way to be sure if it could even be the same problem is to check the configuration of your LAN ports. If they are set to Trunk/Any then it is definitely not the same problem. If you are using wired VLAN tagging settings then it could still be the same problem, but as described above it seems unlikely nonetheless. Hope this helps.
@peparn
Thank you for your help to explain on this 
.
@Michael,
Please open a support ticket for us to check. We need to further check from the device. Just worry the issue can be related to port link state issue. You are saying Netgear CM600, did the modem able to set the port speeds ?
Does this problem affect all Balance routers? I have a Surf Soho MK3 and a Balance 20 using the latest firmware. When I use the Balance 20, I occasionally have my Comcast WAN connection enter a âConnectingâ state forever. When I use the Surf Soho MK3, I havenât experienced this problem using the patched firmware, but then I donât use the Surf Soho a great deal. I do have wired vlans in both Trunk mode with a custom VLAN configuration and in Access mode (only one port in Trunk/Any).
The Balance 20 is what I normally use since the Surf Soho MK3 doesnât support 2 WANâs at the same time, just failover. I only have the Surf Soho MK3 because I support about 20 other people to whom I have supplied Surf Soho MK3âs.
If the problem does exist on Balance routers, when will there be a patched version available?
So far we only see the problem happen for Surf SOHO MK3.
For Balance 20, would you please open a support ticket for us to further check ?
Good Morning,
Yesterday I ran into this (or a similar) problem myself.
The SOHO MK3 is connected to a DSL modem which is in bridge mode.
I missed internet during the day (got notification for it) and when I got home I restarted the DSL router (normally the cause) but no solution. After restarting the SOHO MK3 problem still not resolved. Then I did multiple checks (Manually set MTU, statically set DNS, Changed network cables) but in the GUI it always just showed âConnectingâ and sometimes briefly showed âAcquiring IP Addressâ but it never really connected. When I connected the DSL router to the AmpliFi router it immediately connected and I had at least internet on my Home network. Even upgrading to the latest firmware (7.1.2) did not resolve this issue
Iâve read through this tread a bit last night, and even though i see possible solutions mentioned about switching the LAN ports to trunk instead of access, and what else, I do not believe this should be an issue for a router in this segment. I will try and see this weekend what I can find out by using a switch / port mirroring between the SOHO and DSL but since this does change a bit in the set-up I donât know it this would change the workings and might already resolve the issue.
Does the support team already have a real idea what causes this problem? And when will the diagnostic report be available in english ? Might help others with doing some fault-finding since the event log shows nothing on the DHCP / WAN process.
Confirmed 7.1.2 fixed the issue reported in this forum.
Base on your issue description:
The behavior is totally different from what have been discussed here 
âSurf SOHO MK3 never finishes connecting to cable modem if modem rebootsâ
For your case, can you please open a support ticket here to allow support team to check on this.
My Cable modem is Motoral 6120 docsis 3.0 & Pepwasve soho router hw 2 ,firmware 7.12
sometimes my apartment power cycle, then issue came:
-Soho rouer WAN= Always Connecting BUT NO connected:
I have to powercycle the Motoral Modem to make Router connected:
@AndrewStytx
Base on the description, suspected the issue more on modem it self as rebooting the modem restore the connection. Do you test before by direct connect a PC to the modem when the issue happen ? Do the PC able to get connection ?
Hi,
yes, It worked direct to the PC and also netgear router! pepwave soho my first using it!
btw, the pepwave router takes 3-5 min to came up to website login after power cycle!
Do you mean when the issue happen, you still able to get connection for direct connect a PC to the modem ? If yes, please open a support ticket for support team to further check on this.
https://contact.peplink.com/secure/create-support-ticket.html
I know this is an old thread, but I recently started seeing the same issue with a Balance 20X. It worked fine for a long time, but recently began failing to complete the connection to a cable modem just as described in the first post here. My ISP is Comcast. This issue affects at least 3 different models of cable modem.
Another reference to this issue possibly being reintroduced in firmware 8 is here
beginning at âPerhaps the worst thingâ
Anybody else seeing this issue?
Thanks
This again? Ugh. My only suggestion is to boot the devices in a different order. That is, if you power on the modem when the router is up and running, and that fails, then turn both off, power on the modem, wait a minute, then power on the router. Also, be sure you are on the latest firmware.
The problem with juggling the order of booting devices is that it requires someone physically present to manually intervene. Kind of defeats the purpose of having a router thatâs supposed to be âunbreakable.â Also the cable modem can reboot itself from time to time when Comcast has issues, so it can occur frequently.
Thanks
I fell victim to this too, and had to make a site visit to a client after their SOHO would not connect to their cable modem. In my case Spectrum was the ISP. One suggested hack was to insert a switch between the router and modem.
I wondered if placing an unmanaged switch between the modem and router would help. Peplink support also suggested trying it. It didnât appear to make any difference in the behavior.
Thanks,
Michael
Bah, humbug. Out of guesses.
@cover, I can confirm this error still exist, as it just happened the other day for me when the power went out and came back on. My ISP however is Cox, and I am using a Balance 310X. I have had this problem before with a 580 on both Cox and Comcast.
For my 310X the cellular module connected to Verizon just fine, it was WAN1 where Cox was plugged into that just would not connect. The only fix was to power cycle everything and wait for the cable modem to connect completely first before plugging in the router. Not optimal if you are not on site.