FreeCommander Forum

i have installed Free commander on XP, likewise we connect to network by using windows+R to access shared network how can i do it using free commander when i edit the address bar and give the name of the shared network it just does nothing

for exaple:

in windows to access the shared n/w XYZ i do the following

1) press windows+R to see the Run
2)then type the shared network \\XYZ
3) eventually i see the shared network opened

where as in free commander i do the following

1) edit the address bar and type \\XYZ but it does not connect to the shared n/w

how can this be done in free commander without using windows+R

Alt+G is what you are looking for.

hi clanman

i'm not looking for the Alt+g shortcut, what i exactly mean is when i edit the address bar and give the name of the shared n/w it does not do anything where as using windows+r the same shared network gets opened up for accessing

sureshspeaks wrote:hi clanman

i'm not looking for the Alt+g shortcut, what i exactly mean is when i edit the address bar and give the name of the shared n/w it does not do anything where as using windows+r the same shared network gets opened up for accessing

This is a Windows Authentication issue.

Check that the user you are trying to access with has explicit permission to view the root of the machine at \\MachineName (an example name).

For example, if I have a restricted user (or have removed the guest user from my machine) then typing \\MachineName will show nothing (or possibly return an error stating that I do not have permission to view that resource on MachineName)

But, if I have a share named Share on MachineName, that the user has explicit access to, then they can see \\MachineName\Share with no problem.

If I later try to authenticate with a more privileged user, then I should be able to see \\MachineName (but may only see "Printers" or "Scheduled Tasks" as the shares may all be hidden i.e. \\MachineName\C$).

To test this, try to access the shares by running FreeCommander as a different user (right click on Start Menu Shortcut and "Run As"), preferably as an Administrative user on \\MachineName.

HTH,

E.

Great i will try your suggestion infact it should not be a Privilege issue as i am authenticated to log in to that Server.but anyways thanks for your Reply

HI FC Fans !!!

This is my first post

I also want to access a network folder but FC doesn't want to do it via the address bar (right-click and select edit address bar). I do have permissions.

Surely I don't need to use the 'My network places' icon and drill down to the relevant network folder manually.... that will take forever

Doesn't seem FC can access a UNC path. That's a real bummer as it's a basic function.

Only way I can see is to map a drive letter to the UNC path, and then use the new drive mapping.

Perhaps the upcoming version will be able to do this.

UNC looks like this: \\ComputerName\SharedFolder\Resource

For me, FC can access a SharedFolder, but not (initially) a ComputerName.
E.g.
\\10.0.0.3\ will not work, but
\\10.0.0.3\myshare\ will work in FC

If you go to \\10.0.0.3\myshare\ and then up one folder (..)
you'll be at \\10.0.0.3\ and see the other shares

I am not so knowledgeable about this matter. So i have to learn it. Thanks for the post.



plan solution commission de surendettement - commission de surendettement, vous pouvez demander un dossier de surendettement.plan solution commission de surendettement

1. FreeCommander can definitely access UNC paths
2. Alt+G will open the dialog box to enter an address (I have remapped this to CTRL+G - because I find it to be more intuitive)
3. This also works in the address bar at the top of the folder pane
4. I have three custom toolbars for separate grouping of UNC shares on my networked machines.

If you cannot see the root of the machine (i.e. \\MachineName) then you most likely are in the user or 'power user' (in addition to, or instead of the administrators) group on the machine where you are trying to access the root path.

I can assure you (if you are using FC 2009.02) that this issue is positively related to drive share permissions on the machine where you are trying to navigate the UNC path.

Note that I said 'administrators' group. Not, the Administrator account.

Also, when I create a new user, I immediately add them to the Administrators group (me and my wife, her brother - a few other accounts that I use for file permission purposes), then I add other groups (our surname, role based groups (MP3, etc), and similar other groups) that I use to keep us from accidentally deleting files (and to keep curiosity in check )

After that, I remove the User and Power User context for those users.

Additionally, I rename the Guest account and remove the Guest group (but that should be making it harder to 'assure' you this is all possible - not something the non ultra-paranoid user would do )

Matiaan wrote:UNC looks like this: \\ComputerName\SharedFolder\Resource

For me, FC can access a SharedFolder, but not (initially) a ComputerName.
E.g.
\\10.0.0.3\ will not work, but
\\10.0.0.3\myshare\ will work in FC

If you go to \\10.0.0.3\myshare\ and then up one folder (..)
you'll be at \\10.0.0.3\ and see the other shares

I'd like to back this up. This happens for me too. The UNC behaviour is definitely not right.

You can enter \\computer\share and it's fine. \\computername, however, fails. However from \\computer\share you can use .. to go back to \\computername.

And it's not an access rights issue as i access these computer names all day using both windows explorer and x2 and both are fine. And in fact FreeCommander will let you access these paths too, just not type them in after pressing alt+g.

And as said by someone else, this is basic functionality these days. It was practically the first thing I tried to do after downloading FreeCommander.