Troubleshooting heterogenous Microsoft networks is notoriously difficult, and good practitioners who can nail all the issues with the varied protocols, versions, etc, are hard to find and worth their weight in platinum. I've seen similar issues with "Network Discovery" and just worked around them.
I would just suggest you build a table that lists of the machines in your network, and when you want to access any one of these, you pop up that list and have it run explorer.exe \\machinename and that should get you what you want. I'll bet KC could whip it up in Xojo, Stephen in DotNet, or Ed in Python in no time :) You could even use FoxPro! On Fri, Oct 30, 2015 at 10:53 AM, Ken Dibble <[email protected]> wrote: ... >> >> I have been going nuts for the past week researching this on the web and >> discussing it with our IT consultants. I am not getting the results I would >> like. I thought maybe some people here could fill in the missing links. >> -- Ted Roche Ex-MSCE, Ex-MCSD, MCP, 9xMVP Ted Roche & Associates, LLC http://www.tedroche.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CACW6n4u0nBuock8tAVjfRwShT_B3uSFJ+_d5q=pabk8et0a...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
