Page 1 of 1
Using UNC paths
Posted: 27 Aug 2007 20:51
by Orson
I've asked about this in the past, but the need to recognize and honor UNC paths is becoming more important in my company as some drive letters are being retired. As of now, the following path does not get recognized by Xyplorer (6.20, latest beta as of Aug 27):
\\calix.local\storage\public\FieldOps\FieldMarketing\
And this is true despite my having enabled Show Hidden Drives, Show Hidden Files and Folders, Show System Files and Folder, and Show My Network Places.
Am I missing another setting that will correctly recognize UNC paths?
Thanks.
Re: Using UNC paths
Posted: 27 Aug 2007 21:17
by admin
Orson wrote:\\calix.local\storage\public\FieldOps\FieldMarketing\
Is this in the main/default workgroup?
You may download the little test app
"ExistUNC" and check which of various methods does see your UNC path.
Posted: 27 Aug 2007 21:55
by Orson
I don't understand your question about whether this is in the main/default workgroup.
I tried the ExistUNC app and got these results:
Path: \\calix.local\storage\public\FieldOps\FieldMarketing\
- Check 1: True. Time needed: 2.878 msec = 0.00 seconds
- Check 2: True. Time needed: 0.544 msec = 0.00 seconds
- Check 3: True. Time needed: 2.841 msec = 0.00 seconds
- Check 4: True. Time needed: 1.123 msec = 0.00 seconds
- Check 5: True. Time needed: 0.990 msec = 0.00 seconds
- Check 6: True. Time needed: 3.334 msec = 0.00 seconds
Posted: 27 Aug 2007 22:19
by admin
Orson wrote:I don't understand your question about whether this is in the main/default workgroup.
I tried the ExistUNC app and got these results:
Path: \\calix.local\storage\public\FieldOps\FieldMarketing\
- Check 1: True. Time needed: 2.878 msec = 0.00 seconds
- Check 2: True. Time needed: 0.544 msec = 0.00 seconds
- Check 3: True. Time needed: 2.841 msec = 0.00 seconds
- Check 4: True. Time needed: 1.123 msec = 0.00 seconds
- Check 5: True. Time needed: 0.990 msec = 0.00 seconds
- Check 6: True. Time needed: 3.334 msec = 0.00 seconds
All True. All correct. So XY
should work correctly too!
This result, by the way, answers my workgroup question (answer is "yes").
Is this location password protected?
Posted: 27 Aug 2007 22:26
by Orson
Re: password protected or not: Different groups within our company have varying permissions for different folders. However, my permissions allow me access to the listed folders without any additional login (beyond the login I use when I boot up my PC in the morning).
By the way, for what it's worth, when I paste the path into the address field in XY, I get as far as \\calix.local\ and the tree shows two folders (or perhaps they're servers) that do not match what's in the path.
Posted: 27 Aug 2007 23:25
by admin
Orson wrote:By the way, for what it's worth, when I paste the path into the address field in XY, I get as far as \\calix.local\ and the tree shows two folders (or perhaps they're servers) that do not match what's in the path.
Ok, that's interesting info. Those folders are "shares". So XY has problems to list those shares.
Here's another test app
"NetworkList". Please check which of various methods does list your shares correctly.
Posted: 27 Aug 2007 23:38
by Orson
Using NetworkList, it appears the shares are not being detected/recognized. The servers being recognized do not match with the path I have been given, either. Kind of confusing, but I'm not IT guy.
Posted: 27 Aug 2007 23:55
by admin
Orson wrote:Using NetworkList, it appears the shares are not being detected/recognized. The servers being recognized do not match with the path I have been given, either. Kind of confusing, but I'm not IT guy.
Aha, probably my first guess about a non-default workgroup was right. You should be able to see the workgroup when you use Explorer's Nethood tree to browse to your UNC locations.
Posted: 27 Aug 2007 23:59
by Orson
Under My Network Places, I can see a portion of the UNC path, but not the entire path.
Posted: 28 Aug 2007 07:42
by admin
Orson wrote:Under My Network Places, I can see a portion of the UNC path, but not the entire path.
In Explorer? Hm. Is there any software that can see your path?
Posted: 28 Aug 2007 17:42
by Orson
The path can be pasted into Windows Explorer and it works -- I see the location in the list as well as in the tree.
In Total Commander 7, I can see the location, but the tree does not display it -- just the list.
In Xplorer2 I can see the location in the list and tree.
In XY, I can't get there. But with a drive letter provided by my co. as a kind of alias, I can get to it. I'm able to work with the files, but I have to use the alias drive letter, not the UNC path.
I hope this helps. I gotta believe *someone* else out there must have a similar situation. But again, in good old Windows Explorer, it all works just fine.
Posted: 28 Aug 2007 20:23
by admin
Orson wrote:The path can be pasted into Windows Explorer and it works -- I see the location in the list as well as in the tree. ...
Hm, difficult. It would help to know what's so special about this location / server / share... Explorer goes there but does not show it in the tree (before going there). Weird...
Posted: 29 Aug 2007 00:08
by lukescammell
This sounds similar to the problems I'm having with all versions of XY after 6.10.0071. That's the last version that I can use to view ANYTHING on my work network.
Incidentally, when loading up XY at home using my work .ini file it takes nearly THREE minutes!
Application loaded in 177,604 ms; Configuration dialog loaded in 114 ms
Any chance you could try 6.10.0071 and see if that has any more luck with your network shares? I can send you this version if need be.
Posted: 29 Aug 2007 00:27
by Orson
Luke,
I'd be happy to try that other build. How can I get it?
Posted: 29 Aug 2007 07:51
by admin
lukescammell wrote:This sounds similar to the problems I'm having with all versions of XY after 6.10.0071. That's the last version that I can use to view ANYTHING on my work network.
Did you try v6.20.0009 or later. I thought I fixed your problem!
lukescammell wrote:Incidentally, when loading up XY at home using my work .ini file it takes nearly THREE minutes!

Sounds like a hard disk problem.