This content has been marked as final. Show 4 replies
Check the ColdFusion 5 Server service on the working server. It is likely running as a service and using a specific user login. New installations default to localsystem to run the CF services. Localsystem will not have access to shared drives and other shared resources. Configure a similar user on the new box and have CF run under that user.
I appreciate your response. I have the services running under my account and I have logged the server onto the network using my account. Since I last posted I have tried various setup combinations and found a "working solution" (older Novell client 4.91 SP2 on w2K SP4 Server) on a development server. However, this solution may not last forever. The question posed to me by our Novell people is: Does CF use native API's on a windows server to do file operations or is CF coded to handle NCP (netware Core Protocols) calls and utilize Clustered DFS volumes on NetWare. I am hoping someone at Adobe can answer that question because I can't.
ColdFusion uses java to do all its file I/O. So, ultimately we use whatever java is using. We do not directly call any native API's.
Thanks again for responding. This past Friday we did a trace on our server to see why application it couldn't access the Novell share. It appears that when the application tries to access it passes the account username on CF Application Service with the domain appended to it like watchdog.co-nt-derd1 (username.domainname). Novell doesn't recognize the username with the domain appended to it. So we're trying to figure out how to get around this.
If you have any suggestions please pass them along.