View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009143 | MMW v4 | Main Panel/Toolbars/Menus | public | 2012-02-15 18:14 | 2014-12-02 02:02 |
Reporter | peke | Assigned To | |||
Priority | urgent | Severity | major | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | 4.0.3 | ||||
Target Version | 4.1 | ||||
Summary | 0009143: Network Computers are not shown | ||||
Description | 1473 In Windows 7 pro x86 and ultimate x64 Using My computer -> network -> Ms Win network -> WORKGROUP only computer browsing and its shares are shown and users can't access network PCs. | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
|
Peke, I don't understand what exactly is not shown. 1. Could you attach a screengrap? 2. If you browse the WORKGROUP via Windows explorer is the behaviour same? 3. Is this a regression? |
|
1. uploaded to FTP 2. No issues there 3. No Same behavior in MM3 |
|
Thx, please attach also screengrap which network devices shows MM. |
|
1. MM screenshot Uploaded to FTP using 1474 |
|
We uses WNetOpenEnum function for enumerating the resources: http://msdn.microsoft.com/en-us/library/windows/desktop/aa385478(v=vs.85).aspx I simulated something similar as Peke, but I haven't been able to show all resources by using the function despite the fact I tried various input parameters. It looks that on Vista+ we need to use an alternate method for resource enumeration. |
|
You are right it looks that In Vista+ better approach would be to use network list manager http://msdn.microsoft.com/en-us/library/windows/desktop/aa370803%28v=vs.85%29.aspx , Network Management http://msdn.microsoft.com/en-us/library/windows/desktop/aa370672%28v=vs.85%29.aspx and/or P2P looks like used in Win7 HomeGroup http://msdn.microsoft.com/en-us/library/windows/desktop/aa371704%28v=vs.85%29.aspx More info at: http://stackoverflow.com/questions/7360487/network-list-manager-api-and-netwok-notification-area-overflow-updating |
|
Technical note: here is a way how to create the type library from Microsoft SDK's, namely netlistmgr.idl and netlistmgr.h https://forums.embarcadero.com/thread.jspa?messageID=400156&tstart=0 Used batch: cd "f:\Program Files\Microsoft Visual Studio 9.0\VC\bin\" vcvars32.bat cd "f:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin\" midl "f:\Program Files\Microsoft SDKs\Windows\v6.0A\Include\netlistmgr.idl" TRegSvr /t netlistmgr.tlb |
|
Nevertheless after the importing the type library I found that INetworkListManager is not a way as it cannot enumerate network shares, but only networks. The way could be to use NetShareEnum: http://msdn.microsoft.com/en-us/library/windows/desktop/bb525387(v=vs.85).aspx |
|
Shouldn't we check which network(s) PC Belongs before query/reading network shares? Or see if user is connected to any network at all (Home, Business, Public)? In some cases I had issues with users that Bridge Wireless to LAN where they have Storage devices and/or network PCs. |
|
Peke, I studied it further and our approach used so far is good (WNetOpenEnum) and there is no limitation on Vista/Win 7. I finally found that the difference was caused by bad security settings. Althought it shown the computer in windows, I actually cannot access its content, because it was a content on my laptop connected wirelessly and I haven't switched on the "File and printer sharing" on the Wireless network connection. See item 4) screenshot here: http://www.home-network-help.com/simple-file-sharing.html to understand what I think. Once I enabled the sharing then I could browse the shared folders both by Windows and MM. So there is in fact no issue with MM for computers that has correctly configured sharing/permissions. Could you confirm? |
|
Not an issue anymore |
|
Verified 1722 |