Redrum wrote: > Regarding net:UDAP, I am an engineer, and can get around home network > stuff, but other than that, IT things and the latest software > development environments/languages can be a bit of a foreign language to > me. I stopped actively coding at C, before it got the "++", and on unix, > before there was linux :) I guess I am still stuck on this, once I run > this test, what do I do with the results? Does it lead to a solution, or > rather just a validation that the receiver can hang up?
Net::UDAP is not hard but it is "technical" in that it has a command line interface with rigid command structure and produces output which looks a bit arcane but it is easy to offer guidance You have a problem which can be caused by a number of possibilities. The output from Net::UDAP may help eliminate some possibilities and so enable you to focus trying to find a solution. If the problem is DHCP - then reconfiguring the router usually solves it. If the problem is WiFi power saving by LMS server or router - again disabling options may fix it. If the problem is caused by say a rogue device (e.g. IIRC a few years ago a smartTV which had uPNP enabled caused packet storms and knocked players off) - it will take more effort as Net::UDAP will probably only exclude possible causes. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=110844 _______________________________________________ Duet mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/duet
