When will the 4G LTE Network Extended HeMS Server URL be fixed??

[ckd1191]

During setup of a 4G LTE Network Extender, the device gets hung up on "Connecting to HeMS Server." After logging into the device's Admin console (DEFAULT ADMIN PASSWORD = LTEFemto + the last 4 digits of the MAC ID), I can see the URL which is causing the issue (Connecting to HeMS ...  HeMS Url: http://tr069-casahems.vzwfems.com:8080/hems-web-ui/ws/cwmp) < THIS is the actual site my 4G LTE Network Extender is attempting to connect to. Well, when I did a WHOIS on the domain in question (VZWFEMS.COM) the response that comes back is: No match for domain "VZWFEMS.COM". The device will never find this domain, since ICANN has no idea where it is and it doesn't resolve to any IP address (using NSLOOKUP)! Conversely, the step before this SeGW Server looks for this domain (VZWFEMTO.COM) and this domain is registered to Verizon (in WHOIS) and resolves down to an IP address of 141.207.176.227 in NSLOOKUP. So, when I call Tech Support, all they know how to do is "provision the MAC address" ..which is fine, if you have the ServerError5A issue, but it will never help resolve a URL that doesn't exist! I've tried to explain basic technology to the Tech Support folks ...but, they have no idea what I am talking about (maybe because it isn't in the script they are reading?). Luckily, VZWFEMS.COM is for sale (maybe Verizon failed to renew it to begin with?) ...so, Verizon can purchase it, setup proper DNS entries for it ..so the continual "Connecting to HeMS Server please wait ..." issue can finally be resolved. OR ...allow me to take the device back to a Verizon store, where it can be flash updated with a valid URLfor the HeMS Server(s)? Either way ...Verizon has dropped the ball here, and needs to fix it ASAP

[ckd1191 · Accepted solution]

I never had a Samsung. Luckily, I talked to someone @ Verizon who actually understood what I was saying. They sent me another LTE 4G Network Extender which had the URL updated to the following: Connecting to HeMS ...  HeMS Url: http://[2607:f160:8203:a06c:c0:160:0:20]:8080/hems-web-ui/ws/cwmp-server  HeNB SN: SC0240300293 Removing the "bogus" URL and pointing to a specific address fixed the issue, as the title of this thread had requested. ...Just another VZW customer,... fixing stuff for Verizon.

[jav6]

---

@ckd1191 wrote:

During setup of a 4G LTE Network Extender, the device gets hung up on "Connecting to HeMS Server."

.  .  .

.HeMS Url: http://tr069-casahems.vzwfems.com:8080/hems-web-ui/ws/cwmp) < THIS is the actual site my 4G LTE Network Extender is attempting to connect to.

.  .  .

Verizon has dropped the ball here, and needs to fix it ASAP

---

What model 4G LTE Newtork Extender do you have, Samsung or Askey?  What is its software version and mfg date code?  I have the Askey SFE-116 with software GA5.14 V0.5.014.1657 and Date Code 20220521 which I just restarted with the following successful HeMS connection and subsequent Service Active.  I am in the Northeast US:

[ckd1191]

Sadly, knowing which model and software version will do nothing to assist with resolving DNS, NSLOOKUP, or WhoIS errors. It's just a red herring question.

[jav6]

---

@ckd1191 wrote:
Sadly, knowing which model and software version will do nothing to assist with resolving DNS, NSLOOKUP, or WhoIS errors. It's just a red herring question.

---

Well, my older 4G LTE Network Extender, Samsung SLS-BU10B stopped connecting to the Configuration Server.  It was replaced with the only one being provided now, the Askey ASK-SFE-116 and it connected immediately without issue.  My suspicion was the Samsung support was/is waning and the server it was configured to connect to was updated to only connect to the Askey.  Just my hunch.

[ckd1191 · Accepted solution]

I never had a Samsung. Luckily, I talked to someone @ Verizon who actually understood what I was saying. They sent me another LTE 4G Network Extender which had the URL updated to the following: Connecting to HeMS ...  HeMS Url: http://[2607:f160:8203:a06c:c0:160:0:20]:8080/hems-web-ui/ws/cwmp-server  HeNB SN: SC0240300293 Removing the "bogus" URL and pointing to a specific address fixed the issue, as the title of this thread had requested. ...Just another VZW customer,... fixing stuff for Verizon.

[gmw0113]

Broken here too. On second extender- has never worked. Spent probably 10 hours on the phone with Verizon. They are completely useless in helping me. Everytime they say they will call back- they don't. When I call back in, they want me to repeat all the same rebooting/resetting steps again. Last call was 1 hour 22 minutes. I have no interest in resetting the LTE Extender again. It's not going to magically work.

Spectrum ISP fyi
Askey 4G LTE Extender (*2)

Fails at HeMS server also- 

One time it said it connected, but then gave a server 9A error.

My Router is set to DMZ on the LTE IP. It's not my router. It's not my ISP. It's  you Verizon. It's you.

I'm going to cancel my service (which 50% of the time doesn't work at home) even though I'm 1 mile from a Verizon tower. Literally. It's 1 mile down the road. 

[vzw_customer_support]

Hi there! We know how important having service in the home is for you. Allow us to take a look at all options. I sent you a Private Message to review. -Nikki

[ckd1191 · Accepted solution]

In part of my troubleshooting, I searched for PORTS, PROTOCOLS and SERVICES which my "router" might be blocking. Anyone you call has no idea what you're talking about, BTW. They are literally following a script, they have zero technical knowledge...at all, other than how to hang up (and yes, they all promise to call back, but never do) - at just about the 1 hour trying to help mark...

Retrieved the below on my search for this information (associated with ServerError32 and ServerError27) - but if it helps you, it doesn't matter which thread they are attached to.

I’ve been on the Verizon and Xfinity support lines a “gazillion” times.  They each point the “finger” at each other!  Verizon says that Xfinity needs to “unlock” certain Ports for this to work.  Xfinity says that the required Ports are not blocked.  Verizon also says that the 4G LTE Extender is “registered”, so it should have no problem getting into the Servers.

Verizon provided me the following Ports/Settings that are needed to make the Extender work:

­Ports:

• UDP 319
• UDP 320
• UDP 500
• UDP 4500
• UDP 52428 + 20906
• TCP/UDP 443 + 80

Other Settings:

• Make sure ESP packets are not blocked by the firewall on the downstream
• Enable high QoS for the Femto (LTE Extender)
• Make sure MTU Size is set to 1448 or higher
• Enable DMZ: recommended.  NOT required.  Common on most consumer routers.

[vzw_customer_support]

Hello ckd1191, we see you have an issue with your Network extender. I will be reaching out via private message to better assist you.

-Luis

[vzw_customer_support]

We are still here for your support. Please let us know if you still need assitance. 

-Jazzy