Unsolved

This post is more than 5 years old

1 Message

4142

October 29th, 2019 22:00

Wyse 5070 can't get IP address

I have a Wyse 5070 that I use to work from home for my company.

I have been using the Client for several months without issue. 

My router received a firmware update 10/23 and 10/26 I could no longer use the machine. It sits on "ENET0: Locating IP address from DHCP"

I took the device onsite and it connects via our external network testing lab.

I attempting hooking the client directly to the modem and it has the same issue. 

I have deleted all saved devices from my router with no change. I have attempted all ports on the router with 3 different cables and have determined that there is no issue with any of the router ports or the ethernet wires. 

The rest of my home network functions fine. 

I have another device that runs a VPN on the network that also functions fine. 

The tests have eliminated a standalone issue with each part of the equation and my help desk at work has seemingly run out of ideas.

Does anyone have any ideas on what could be causing my Wyce Client to not retrieve an IP address on my home network after working for several months?

1 Message

May 10th, 2020 10:00

I know this is a few months old, but I'm having the same issue.

I think it might have something to do with DHPC server options, as I can statically assign an IP address and get a wconfig pulled down.

What make/model of router are you using? Or, if you found a solution, what was it?

Moderator

 • 

901 Posts

May 11th, 2020 05:00

Getting an IP via DHCP, is normally a completely separate process from assigning a management server from DHCP Option tags.  

Normally issues receiving an IP by DHCP is related to the network you are connected to.  You have already proven the NIC works by manually assigning an IP.   Assuming you can get an IP via DHCP on the same port from a different device I would suggest the following:

Try to factory reset the device

Look at the port configuration on the switch port you are connecting to.   I have seen problems when spanning tree is turned on, or "PortFast" is not enabled.  Essentially the device boots too fast for the port to initialize while it is determining spanning tree.

 

1 Rookie

 • 

2 Posts

June 9th, 2021 00:00

Hi there, 

Did you ever find a solution to this ?

 

thanks,

1 Message

July 26th, 2021 13:00

We’re you able to find a solution?

No Events found!

Top