Newbie Q's: Tabs, extra len column, mapped drives

[admin]

Is there anybody else who could try, please?

lognetworkaccess: Vrai

sTu_Deimus: You probably need to enable "Quick Scripting" on Configuration - Advanced first, or enter it using using menu Scripting|Try Script...

Aaaaaahh, sure!! you see how much I need a break...

[sTu_Deimus]

Thanks Jacky. The quick scripting option did it.

I'll try this tomorrow.

[sTu_Deimus]

Ok, so now I can toggle lognetworkaccess (or supply 1 or 0), but I never see any log box pop up whether its in the condition where a) xy isn't properly seeing the mapped drive, b) when I browse directly to the server using xy (and it sees the available shares), or c) when I then browse to the mapped drive using Windows Explorer and then successfully browse to the same drive using XY.

Stu.

[sTu_Deimus]

LOL... then I do get the dialog when I've finished testing and disconnected the VPN:

Proc: IsShareAccessDenied

Path = \\<server>\<share>
Accessible = False
AccessDenied = False
Error = 53

XY ver 6.80.0112
OS Vista
Date 18/03/2008 8:43:41 PM

[admin]

LOL... then I do get the dialog when I've finished testing and disconnected the VPN:

Proc: IsShareAccessDenied

Path = \\<server>\<share>
Accessible = False
AccessDenied = False
Error = 53

XY ver 6.80.0112
OS Vista
Date 18/03/2008 8:43:41 PM

Ah, very good, that helps! I'll come back with the solution...

[sTu_Deimus]

2) The other as mentioned in the 8th post of this thread is where one logs in with the connection, and the shares work fine, but then when disconnecting and reconnecting (eg. LAN -> Nothing -> WiFi), Explorer will let you browse the shares again, but XY won't (until that is done in Explorer).

Stu.

Okay, but did the last beta solve at least one of the issues?

Ok, I'm still running 6.80.012, and having done much more of this scenario (#2 above), I have now found that XY does eventually find the shares... but only when I "try again later" as opposed to frantically trying to access them in desperation after reconnecting a link. I suspect it might need a few minutes before they can be accessed.

Stu.

[admin]

2) The other as mentioned in the 8th post of this thread is where one logs in with the connection, and the shares work fine, but then when disconnecting and reconnecting (eg. LAN -> Nothing -> WiFi), Explorer will let you browse the shares again, but XY won't (until that is done in Explorer).

Stu.

Okay, but did the last beta solve at least one of the issues?

Ok, I'm still running 6.80.012, and having done much more of this scenario (#2 above), I have now found that XY does eventually find the shares... but only when I "try again later" as opposed to frantically trying to access them in desperation after reconnecting a link. I suspect it might need a few minutes before they can be accessed.

Stu.

And Explorer is different in this respect? (= immediate access)

[sTu_Deimus]

There's definitely a difference - maybe "instantaneous" is the wrong word, but it is fairly clear that Explorer does think for a moment before finding the share, where XY doesn't.

Well, it might just be taking a long time, but unlike explorer, XY comes back straight away saying its not available, giving the impression that its not even looked. Its only after that few minutes that XY then finds the share.

[admin]

LOL... then I do get the dialog when I've finished testing and disconnected the VPN:

Proc: IsShareAccessDenied

Path = \\<server>\<share>
Accessible = False
AccessDenied = False
Error = 53

XY ver 6.80.0112
OS Vista
Date 18/03/2008 8:43:41 PM

I assume that you patched the error message quoted above, to obscure your real path? Because error 53 is ERROR_BAD_NETPATH, and "\\<server>\<share>" surely is a bad net path.
Now. the path that was originally displayed in the error message: is it an existing path? And would you expect to see a logon dialog for it at that point?

[admin]

There's definitely a difference - maybe "instantaneous" is the wrong word, but it is fairly clear that Explorer does think for a moment before finding the share, where XY doesn't.

Well, it might just be taking a long time, but unlike explorer, XY comes back straight away saying its not available, giving the impression that its not even looked. Its only after that few minutes that XY then finds the share.

I don't have a good explanation for this at the moment.

Did you try this test app already?
http://www.xyplorer.com/download/ExistUNC.zip
You might find a better way here to access your shares...