nomachine error 138 no conecta a xp home

Your machine almost certainly has a .x IP address. If you see that status associated with your network connectivity, then you’re facing the problem discussed here. Situations resulting in a .x IP address are flagged as “limited connectivity” in Windows. And those “made up” IP addresses all begin with 169.254.

Your machine waits for a while and then gives up.īut when it gives up, it invokes what’s called Automatic Private IP Addressing, or APIPA, and makes up its own IP address. Whether due to a network problem - maybe not being on a network at all - or perhaps a lack of DHCP server to hand out IP addresses, the result is the same: the request for an IP address assignment goes unanswered. The difficulty arises when your computer asks for an IP address and no one responds. IP addresses beginning with 169.254, however, are special. If you’re directly connected to the internet, your IP address could be almost anything, but it’ll be assigned by a DHCP server run by your ISP. You’ll most commonly get an address in the .x range. If you are connected to a NAT router, it acts as a DHCP server and hands out IP addresses.

Using DHCP, your computer requests an IP address. Typically, the IP address of your computer is assigned when you boot your machine. That can happen for several reasons, so your computer, the path from your computer to its router, and the router itself should be investigated. indicate your computer never got a response. Dynamic IP addresses are assigned by your router or equivalent when your computer asks for one.

Nomachine error 138 no conecta a xp home