All,
I have been helping a dedicated server customer of mine with a move
of their offices. They are running two Debian Sarge servers. One
hosts email and web. The other is internal and is a file server
running samba. I know nothing about samba. It appears that whomever
set these things up was sniffing glue. I have it all sorted out
except the samba stuff.
When we moved the servers from the old location to the new one we
changed from what appeared to be a silly D-Link NAT device/router
with port forwarding to allow mail and web in through the firewall...
to a real firewall with a real DMZ, etc. It turns out both servers
had three IP addresses in different subnets and all kinds of
craziness that seems totally unnecessary. For the samba server, I
removed the IP's that were on external subnets and unused subnets,
and left only the one IP address which was on the same subnet as the
other internal hosts (Windows XP workstations). Other than the IP
address changes, there have been no changes to the samba server.
There is no firewall between them and the samba fileserver.
Now that the servers have moved, the users can not map a drive to
the share which they have mapped to daily in the past. The logs don't
seem to show anything useful. I do see the traffic at the server
(with tcpdump). Can anyone give some direction to go in give the above info ?
Given the number of IP addresses and DNS changes in the move, I
wonder if there is anything in the configs that I am missing. The
smb.conf file has the correct socket address. Are there other config
files ? Where are samba authentication errors or failures logged ?
Thanks,
Mike
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
