Salah Posted March 5, 2017 Share #1 Posted March 5, 2017 If you get a 169 IP it's due to DHCP not communicating your netblock/device correctly. Just slap a manual ip 169 to your computer on same router and you can connect. No magic here. Some people set up networks on non routable 169 ips(same as 192.x, 172.x, 10.x) Quote Link to comment Share on other sites More sharing options...
0 Salah Posted March 5, 2017 Author Share #2 Posted March 5, 2017 usually A ID10T error is applied Quote Link to comment Share on other sites More sharing options...
0 Rusty Posted March 6, 2017 Share #3 Posted March 6, 2017 APIPA Quote Link to comment Share on other sites More sharing options...
0 error403 Posted March 7, 2017 Share #4 Posted March 7, 2017 Definitely true, but I encountered a strange behavior lately where I set my machine to correct parameters on ESXi 6.5 recently, and it wouldn't save my changes (it defaulted to SATA instead of SCSI for the virtual HDDs). Once I deleted the machine and started from scratch it worked, but this is something you wouldn't think of. Since I set the correct parameters and clicked "save" I assumed it would do so.. Quote Link to comment Share on other sites More sharing options...
Question
Salah
If you get a 169 IP it's due to DHCP not communicating your netblock/device correctly.
Just slap a manual ip 169 to your computer on same router and you can connect.
No magic here. Some people set up networks on non routable 169 ips(same as 192.x, 172.x, 10.x)
Link to comment
Share on other sites
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.