Centos 5 / Samba / DNS
Posted: 2019/02/06 21:05:49
I just inherited a problem on an EOL Centos 5 server.
There are two servers involved in this problem. Centos/Samba Server and Windows/AD/DNS server.
Windows mounts shares on the Samba Server.
Here is the problem.
Samba cannot ping the Windows server.
Windows cannot ping the Samba server.
Both servers are on the same subnet and on the same switch.
They can both ping all other devices on the network.
Both can reach the internet.
Samba get's it's DNS from Windows.
I created a forward zone on a remote Windows server in DNS to test DNS for Samba ... and it works fine. (just temporarliy changed /etc/resolv.conf)
On the Samba server, the network interface is a bridge - but it only has eth0 associated with that bridge.
I can change that - but I don't see the point since I can see the rest of the network.
I have changed ports on the switch (to eliminate this from my list of possibilites) it had no impact.
I have rebooted the Samba Server - after trying various service restarts.
All firewalls are off.
My last clue is that ssh connections take forever after you enter your password.
I am working on the console of the Samba server so I have direct access,
Has anyone seen this before? I am not finding anything similar in online searches.
Thanks for any ideas.
Yes - I know this needs upgraded to the new OS - but as I said, I just inherited this server when they called in the problem.
There are two servers involved in this problem. Centos/Samba Server and Windows/AD/DNS server.
Windows mounts shares on the Samba Server.
Here is the problem.
Samba cannot ping the Windows server.
Windows cannot ping the Samba server.
Both servers are on the same subnet and on the same switch.
They can both ping all other devices on the network.
Both can reach the internet.
Samba get's it's DNS from Windows.
I created a forward zone on a remote Windows server in DNS to test DNS for Samba ... and it works fine. (just temporarliy changed /etc/resolv.conf)
On the Samba server, the network interface is a bridge - but it only has eth0 associated with that bridge.
I can change that - but I don't see the point since I can see the rest of the network.
I have changed ports on the switch (to eliminate this from my list of possibilites) it had no impact.
I have rebooted the Samba Server - after trying various service restarts.
All firewalls are off.
My last clue is that ssh connections take forever after you enter your password.
I am working on the console of the Samba server so I have direct access,
Has anyone seen this before? I am not finding anything similar in online searches.
Thanks for any ideas.
Yes - I know this needs upgraded to the new OS - but as I said, I just inherited this server when they called in the problem.