10-13-06 06:29 AM
Dear all,
I have a very strange file/folder sharing problem.
There is a folder which hosts program A's DLL file and all of shared images
and data for all users. There are two ways to handle the shared folder. One
is mapped drive as W when it happened automatically during installation, the
other one is using UNC. The UNC is: \\Server A\Shared folder A. The DLL file
controlled the program logon. If unable to access the DLL file, the program
will not be availabe for users. Both methods failed for remote offices after
server was up for certain period. Users from remote offices can’t see the
shared folder which results in failed logon to the Program A. In the mean
time, any users in host site have no problem continue using the program.
From remote offices:
I tried to ping the server. It replied.
I tried to access other folders in other servers, it works fine.
I tried to access different folders in the same server (\\Server A\Shared
Folder B). It works fine. I can get the list of folder contents.
The temp solution for that is to reboot the server.
Any suggestion? Help~~~~~
[ Post a follow-up to this message ]
|