Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

2003 AD w/ Linux DNS

Status
Not open for further replies.

DelaneyL

MIS
Mar 17, 2006
1
US
We are building a Windows Domain with 2003 Server on an existing workgroup, using a Linux server as DNS and DHCP. Only 3 PCs are join in the domain, and the rest of the PCs are still remain in workgroup. I've set forwarders on the 2003 server.

Somehow, the PCs on the windows domain is having a hard time to access shares in the workgroup. The computer will freeze with we open up network neighborhood. But sometimes users can connect to the workgroup without any problem. All computers can access to internet. And I've succeed in pinging all the servers and PCs with their names and IP.

Can somebody help me with this issue please?
 
Do the computers in question have rites for the shared files? It sounds like a permissions problem.

Glen A. Johnson
If you like fun and sun, check out Tek-Tips Florida Forum
"Maybe this world is another planet's hell."
Aldous Huxley (1894-1963), English critic & novelist

 
I have a similar setup with Linux DNS and 2003 Domain and XP Pro and 2000 Clients. The XP Pro boxes were really the only ones having problems with the shares. The clients would work fine for about 15 or 20 min then drop. The messages always seem to indicate the users were still connected to the shares and would not reauthenticate them. If the users log off and back on again they would work fine for a short period, then same ole problem. I tried and tried to make this work, and there may be a solution out there. However, I ended up moving the internal DNS and DHCP off the linux box to 2003 Domain and most all of my problems have gone away. I still use the Linux for external DNS.

I spent more time trying to figure this one out than it took to move the interal DNS and DHCP over to the 2003 DC. If you find a solution other than what I have suggested I would like to know, but if your in a need a quick fix that works, I would suggest moving your internal DNS and DHCP over to the 2003 DC.

Good luck.
Adminbydefault
 
Check and make sure your share_dir on Samba has 2775 permissions setup.

It should halp!

Cheers,
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top