595: Accessing networked computers via IP addresses
Posted: 08.07.2012, 16:49
Hi,
I often have to work with networked computers which do not use a workgroup, and thus, do not appear in the list of "named" networked computers, either in FreeCommander or Windows Explorer. I need to access them via UNC paths using their IP addresses, e.g. "\\192.168.0.100". It works, and the computer is then shown (as "\\192.268.0.100") under "Network" in FC. I can navigate its shared folders as expected.
But, when I perform any file operation (e.g. copy a file to/from the computer, delete files, etc.), the computer in question immediately disappears from "Network". The focus in the folder tree moves to "Network" itself, and the list of files and folders in the right-hand panel is forgotten (replaced with the list of named network resources). I then have to click in the address bar and re-type the UNC path to get back to the networked computer.
Windows Explorer does NOT exhibit this behavior, it retains the UNC-referenced computer indefinitely in the folder tree (or at least until that Explorer window is closed).
Aimhere
[Edit: FCXE continues to behave this way as of release 613.]
I often have to work with networked computers which do not use a workgroup, and thus, do not appear in the list of "named" networked computers, either in FreeCommander or Windows Explorer. I need to access them via UNC paths using their IP addresses, e.g. "\\192.168.0.100". It works, and the computer is then shown (as "\\192.268.0.100") under "Network" in FC. I can navigate its shared folders as expected.
But, when I perform any file operation (e.g. copy a file to/from the computer, delete files, etc.), the computer in question immediately disappears from "Network". The focus in the folder tree moves to "Network" itself, and the list of files and folders in the right-hand panel is forgotten (replaced with the list of named network resources). I then have to click in the address bar and re-type the UNC path to get back to the networked computer.
Windows Explorer does NOT exhibit this behavior, it retains the UNC-referenced computer indefinitely in the folder tree (or at least until that Explorer window is closed).
Aimhere
[Edit: FCXE continues to behave this way as of release 613.]