edwin2006 wrote: > I had something similar with transporter connected via ethernet cable. > After some research I noticed strange ip adres for the transporter > (outside dhcp scope) so I rebooted router and powered (again) the > transporter off and on. Surprisingly this solved the issue.
Not surprising, actually. For whatever reason, the transport wasn't able to get a "new" IP address, so it got that "strange" IP address, probably 169.254.somethingsomething). Rebooting the router (which presumably also is your DHCP server) may have fixed an issue with its DHCP server while power-cycling the transporter may have fixed if there was an issue. QLMS [email protected] x64 (digimaster) with perl 5.30.1 / QNAP 469L QTS 4.3.4 ------------------------------------------------------------------------ dolodobendan's Profile: http://forums.slimdevices.com/member.php?userid=67663 View this thread: http://forums.slimdevices.com/showthread.php?t=113127 _______________________________________________ Duet mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/duet
