Hi,
Your smart TV connected to Surf Soho via wired or wireless connection?
Please open ticket for us to investigate.
Thank you.
It is a wired connection. I opened a support ticket way back when I first had trouble with the new firmware. My case was handed off to the 3G store where I purchased it. They were of course unable to help because it is a firmware issue.
Hi,
I managed to find your ticket number. I noticed your box was upgraded to v6.3.0s016 before, not v6.3.0s013.
Please load this firmware I suggested here into your box.
Thank you.
Build 1996 fixed the Samsung TV problem, but now I cannot visit certain websites, for example gap.com or stream Sirius XM. Here is a copy of the tracert from the Surf for gap.com:
2 72.31.237.17 (72.31.237.17) 10.750 ms 10.328 ms 9.906 ms
3 72.31.117.128 (72.31.117.128) 13.628 ms 72.31.208.18 (72.31.208.18) 11.315 ms 72.31.117.128 (72.31.117.128) 12.782 ms
4 72.31.3.152 (72.31.3.152) 11.661 ms 13.579 ms 13.181 ms
5 72.31.3.116 (72.31.3.116) 14.046 ms 72.31.3.118 (72.31.3.118) 14.146 ms 71.44.17.38 (71.44.17.38) 11.935 ms
6 66.109.6.96 (66.109.6.96) 15.759 ms 10.122 ms 13.549 ms
7 66.109.1.70 (66.109.1.70) 36.543 ms 33.471 ms 33.394 ms
8 66.109.6.39 (66.109.6.39) 41.107 ms 38.041 ms 40.129 ms
9 107.14.17.232 (107.14.17.232) 40.179 ms 107.14.17.236 (107.14.17.236) 34.063 ms 107.14.17.232 (107.14.17.232) 32.731 ms
10 66.109.9.91 (66.109.9.91) 34.260 ms 32.485 ms 34.028 ms
11 64.125.20.233 (64.125.20.233) 30.482 ms 32.590 ms 33.234 ms
12 64.125.30.182 (64.125.30.182) 123.842 ms 120.797 ms 120.117 ms
13 64.125.28.102 (64.125.28.102) 84.986 ms 84.435 ms 80.979 ms
14 64.125.30.241 (64.125.30.241) 52.371 ms 51.764 ms 51.148 ms
15 64.125.31.66 (64.125.31.66) 76.207 ms 75.791 ms 74.390 ms
16 208.184.238.98 (208.184.238.98) 269.986 ms 242.973 ms 242.507 ms
17 198.153.202.20 (198.153.202.20) 77.340 ms 76.545 ms 75.658 ms
It looks like everything should be working, but when I try to load the site it won’t load. Going back to 6.2.2 fixed the web browsing issue. But I still cannot stream Sirius XM. I’ve been having trouble with that since upgrading from 6.1.2. Bypassing the Surf and connecting the cable modem directly to my notebook also solves the streaming issue, so I know it’s not my ISP.
Hi,
I managed to browse gap.com and stream Sirius XM. Please change the DNS server on WAN interface to 8.8.8.8 and 8.8.4.4 to confirm this will help?
If changing DNS server doesn’t help, please open ticket for us to investigate since this is a different problem. I need you help to prepare a testing PC which directly attached to Surf Soho LAN port. Please provide Remote Desktop service for tech support to access the testing PC.
Thank you.
Was puzzled why half my wired connections were not found after the update to 6.3.0
Glad I found this thread. The update to 6.3.0s013 build 1996 seems to be working.
Thank you.
In my case, 18 out of 20 wired and wireless devices worked fine on firmware 6.3 build 1967 but two devices could not get online. Each device was seen by the router, in fact it gave one an IP address via DHCP (a ROKU box) as shown in the new logging feature for DHCP in fw 6.3. The other device (a stereo receiver) has a static IP and via that IP it is reachable on the LAN side from a computer via HTTP. But neither can get online.
What the two problem devices have in common is they are 100mbps connected via Ethernet to a Netgear GB switch which is connected to a Surf SOHO** hardware version 1**. The 100Mbps speed is from the indicator lights on the switch. Two computers, one Windows one a Chromebook, plugged into the same Netgear switch work fine but each computer makes a GB connection to the switch.
Boot to firmware 6.2.2 both the ROKU box and stereo receiver are fine. Reboot to firmware 6.3 build 1967 and they go offline. Switch back to 6.2.2., they are fine again. Switch back to 6.3 they go offline.
Hi Michael,
May I know you able to ping both units from Surf Soho’s Ping tools in v6.3.0?
If you able to ping them but they still failed to access internet, please open ticket for us to investigate further.
Thank you for your help.
Not sure if this is the same problem as the rest of this thread or not. To recap: my problem devices are a ROKU box and a stereo receiver. Both are connected to a Netgear GB switch and the Ethernet lights on the switch show they have 100mbps connections. Both devices work fine in firmware 6.2.2 and fail to get online in 6.3 build 1967. This has been verified by switching back/forth three times. As background, the four LAN ports on the Surf SOHO are used by three switches and a VOIP telephone adapter. No switch is connected to another switch.
As TK requested, from the router (system -> ping -> LAN) running fw 6.3, I tried to ping each problematic device. It failed. Pings to a NAS box connected to a different switch work fine. Pings from fw 6.2.2 work fine.
The Roku box was powered off when the router switched over to fw 6.3. After the router was up and running the Roku box showed up in the attached client list as inactive but with an IP address due to expire in 1 minute. Sure enough, the IP address expired and it fell off the client list. Then, I powered the Roku box on and it shows up again as an inactive client. DHCP logging is enabled on fw 6.3 and the event log shows that the Roku box gets an IP address via DHCP
DHCP Server: 192.168.1.11 assigned 192.168.1.208 to cc:6d:a0:ce:c2:54, lease time 86400
So, DHCP communication works but Ping does not.
Then, I connected a computer via Ethernet to the same switch as the problem devices. Nmap running on the computer looking for open ports on the IP address of the Roku box complained that the Roku box was offline.
The stereo receiver is slightly different. For one thing, it has a static IP address. When the stereo is powered off the router does not show it in the list of attached devices. When its powered on, it does show but as inactive. After playing over the air FM for a while, the stereo receiver falls off the list of attached devices. Switch it back to playing Internet radio and it appears again, as an inactive client.
Here’s where it gets weird. The stereo has an HTTP interface. If I plug a computer into the same Netgear switch as the stereo, the computer can talk to the stereo using HTTP directed to its IP address and all is well. Likewise, NMAP from this computer to the IP address of the stereo receiver works fine and shows a handful of open ports. However, a different computer on the LAN, connected to a different switch, can not use HTTP to talk to the stereo. And, as noted earlier, pings from the router to the stereo fail in fw 6.3 and work fine from fw 6.2.2. Likewise, from fw 6.2.2 the computer connected to a different switch can talk to the stereo receiver just fine.
A lot to digest. I downloaded a diagnostic report from fw 6.3, if that might help.
Hi Michael,
Possible to share the us the support ticket number here ? We will keep an eye for the ticket.
Thank You
Still having troubles w/ my iPhone not connecting. So I simplified my hardware to just the modem, SOHO, and iPhone. All other devices in my house were powered down. My iPhone refuses to connect to to the SOHO with any functional LAN or WAN connectivity. The SOHO is configured to assign a non-static IP via DHCP. The interesting thing is the iPhone itself indicates it is connecting (click little “circle-i” next to network name in iPhone), but with an IP that is way out of the designated DHCP range. When I switch back to old firmware, it connects just fine with a proper IP.
Hi,
Please find my earlier suggestion here. Without doing the suggested steps, I have no idea why iPhone was connected to a different IP range.
Thank you.
the Ticket number is 758827. In brief, firmware 6.3.0s28 build 2000 did not fix the problem.
I just wanted to pop in and add my experiences.
Our issue was exclusively with VoIP phones. Yealink and Polycom phones were unable to get an IP address \ access the internet. When assigned a static IP, the device is reachable over the LAN, but remains blocked from internet access.
Since we use these for live deployments, I have just reverted back to 6.2.2, but do still have a test unit that I can provide testing information on if required. Peplink - Let me know if you need any additional testing or if you would like me to open a new ticket in addition to the existing ones from this thread.
This fixed my problem. After updating to this firmware all my devices connected no problem. However it now says this firmware will expire on March 25
Firmware 6.3.1 will contain the fix and this will be released prior to that date.
1 Like
I too can confirm that upgraded 6.3.x firmware fixed my Ethernet connectivity issues (WiFi was fine) that started with firmware 6.3. So too did falling back to firmware 6.2.2 - a big plus for Peplink in allowing this. In my case, older Surf SOHO, hardware version 1.
Hello, I’m having the same issue but with a Balance 30.
Firmware 6.3 won’t work with some WinXP and CentOS PCs, but it will with windows 7 and up.
I had to switch back to 6.1.0 build 2517
Jarid, could you send me the special fix?
Thank you
Hi,
The reported problem in this thread only happened in Surf Soho. I suspect your problem might not be same. Please help to open a ticket for us to take a closer look.
Thank you.