Anybody out there experienced this before at all and managed to resolve, not quite losing sleep yet but might do soon.
We are running an nt4 domain that encorporates a samba server 2.0.3 running on suse linux 7.1.
We have 5 subnets, 4 subnets are remote to the subnet where the samba server is physically situated, all bar 1 of the sites can connect to the samba server.
The 1 site that can not connect to the samba server gives the error message, "the semaphore timeout period has expired" on the windows 2000 client machine. I am able to map netowrk drives to Windows servers, 2000 and nt4, but receive the timeout error only when attempting to connect to the samba box. The client machine can connect to the samba server on different subnets as it was built on a different site with no problems whatsoever, and ideas at all?
The client box is able to ping the samba box using netbios name, name resolution appears to be working fine.
We are running an nt4 domain that encorporates a samba server 2.0.3 running on suse linux 7.1.
We have 5 subnets, 4 subnets are remote to the subnet where the samba server is physically situated, all bar 1 of the sites can connect to the samba server.
The 1 site that can not connect to the samba server gives the error message, "the semaphore timeout period has expired" on the windows 2000 client machine. I am able to map netowrk drives to Windows servers, 2000 and nt4, but receive the timeout error only when attempting to connect to the samba box. The client machine can connect to the samba server on different subnets as it was built on a different site with no problems whatsoever, and ideas at all?
The client box is able to ping the samba box using netbios name, name resolution appears to be working fine.