|
Posted by =?Utf-8?B?U2NvdHQgU2hpbm5pZQ== on September 29, 2008, 7:11 am
If you were Registered and logged in, you could reply and use other advanced thread options
Thank you both for the response, I resolved this issue by pointing the
application to an alias on the unix cluster which was running samba. Unsure
why this has resolved the issue when the main A record already exists in DNS.
4 weeks since I made the change and servers have not dropped a single
connection to the share.
Thanks
Scott
"Anteaus" wrote:
> If you are using internal DNS, you need to add A and PTR records for the
> samba server.
>
> "Scott Shinnie" wrote:
>
> > We have a Windows Server 2003 cluster which accesses data held on a samba
> > share hosted on a Solaris 9.0 machine in a trusted domain. However we
> > regularly lose connectivity to the samba share from one of the application
> > servers. The share is up but the server is unable to access it.
> >
> > If I RDP on to the server and try and browse the share I receive the
> > following error.
> >
> > \serveralias\share is not accessible. You might not have permission to use
> > this network resource. Contact the administrator of this server to find out
> > if you have access permissions.
> >
> > No network provider accepted the given network path.
> >
> > If I use a FQDN (unix machine is in a different domain) or IP address to
> > access the share it works correctly. If i reboot the server access to the
> > share is restored.
> >
> > This one has me beat - any advice would be appreciated - kerberos issue??
> >
> > Thanks in advance
| 
XML site map