I have a workstation and a server. They are both windows 7 machines.
I can browse to the files via windows explorer from the workstation.
I have an application on the workstation that need to access files on the server, however it keeps on telling me that the \\server\Folder\File1.ini does not exist.
When I try to access an .exe file on the server, from the workstation via my application, it says, the \\server\Folder\app.exe does not exist.
We have tried doing this http://support.microsoft.com/kb/156276 but to no avail.
Cannot access network path via application
Page 1 of 16 Replies - 139 Views - Last Post: 07 February 2013 - 08:26 AM
Replies To: Cannot access network path via application
#2
Re: Cannot access network path via application
Posted 07 February 2013 - 06:47 AM
That KB article only applies to Windows NT 4.0. You are on Windows 7 which has long fixed that issue.
When you browsed using the Explorer, were you ever prompted for login credentials at some point in the past? (e.g. A dialog box asking for user name and password came up, and you filled it in, and marked the remember credentials checkbox.) If so, you'll have to figure out how to let your program also login to that UNC path with the same credentials.
When you browsed using the Explorer, were you ever prompted for login credentials at some point in the past? (e.g. A dialog box asking for user name and password came up, and you filled it in, and marked the remember credentials checkbox.) If so, you'll have to figure out how to let your program also login to that UNC path with the same credentials.
#3
Re: Cannot access network path via application
Posted 07 February 2013 - 06:52 AM
Skydiver, on 07 February 2013 - 06:47 AM, said:
That KB article only applies to Windows NT 4.0. You are on Windows 7 which has long fixed that issue.
When you browsed using the Explorer, were you ever prompted for login credentials at some point in the past? (e.g. A dialog box asking for user name and password came up, and you filled it in, and marked the remember credentials checkbox.) If so, you'll have to figure out how to let your program also login to that UNC path with the same credentials.
When you browsed using the Explorer, were you ever prompted for login credentials at some point in the past? (e.g. A dialog box asking for user name and password came up, and you filled it in, and marked the remember credentials checkbox.) If so, you'll have to figure out how to let your program also login to that UNC path with the same credentials.
Hi,
It does not require any login credentials when browsing through the browser. It usually works. We are currently facing
a rare case from 1 client of ours.
#4
Re: Cannot access network path via application
Posted 07 February 2013 - 06:59 AM
So on that particular workstation, instead of using the Explorer, try:
Start.Run
Enter 'cmd'
Within the CMD window, type in 'type \\server\Folder\File1.ini'.
Does that also fail?
Start.Run
Enter 'cmd'
Within the CMD window, type in 'type \\server\Folder\File1.ini'.
Does that also fail?
#5
Re: Cannot access network path via application
Posted 07 February 2013 - 08:05 AM
What is the actual path? Some paths are really dynamic shortcuts.
For example, in windows explorer you can click on the
link, but where you really are going is
C:\user\YourName\My Documents\
For example, in windows explorer you can click on the
- Desktop
- Libraries
- Documents
- Libraries
link, but where you really are going is
C:\user\YourName\My Documents\
#6
Re: Cannot access network path via application
Posted 07 February 2013 - 08:13 AM
Skydiver, on 07 February 2013 - 06:59 AM, said:
So on that particular workstation, instead of using the Explorer, try:
Start.Run
Enter 'cmd'
Within the CMD window, type in 'type \\server\Folder\File1.ini'.
Does that also fail?
Start.Run
Enter 'cmd'
Within the CMD window, type in 'type \\server\Folder\File1.ini'.
Does that also fail?
Yes we tried that and it failed, it said something about the UNC path (sorry cannot remember exactly).
We are currently using the actual path.
#7
Re: Cannot access network path via application
Posted 07 February 2013 - 08:26 AM
If the cmd line attempt to reach the path failed - then you don't have the right path. It really is that simple and direct.
Page 1 of 1
|
|

New Topic/Question
Reply



MultiQuote





|