Re: Troubleshoot samba?

On Jun 28, 1:20 pm, Paul Branon <paulbra...@xxxxxxxxxxxxxx> wrote:
Samba, (smbd version 3.0.20) has been working splendidly on my machine
for more than four years. It has run without a hitch. And then
suddenly, today, it has stopped working. I haven't changed anything, I
haven't installed anything on the server and I haven't removed
anything. So I'm at a loss to know what's wrong with it.

The obvious question is "what changed"? Can you even ping
""? Does your local network use DHCP and was recently re-
arranged, or is the host itself even pingable from the other hosts?

The other obvious question is "it's been 4 years since your last major
upgrade: what do you expect"? Samba is an evolving toolkit because
CIFS is an evolving protocol, and there's always shifts to address new
clients, new types of servers, and new vagaries added to the protocol
to deal with new requirements. So seriously consider updating. Vesion
3.5.4 is out and considered stable, and I've tested with it myself: I
like it.

I can only interact with the server from the local command line. (I
haven't altered the allow hosts in the config file. I haven't changed
anything) I used to be able to reach it from all the machines on my
network with windows \\
ERROR: the network path \\ was not found

The machines can all reach each other remotely, (it's not a connection
or cabling issue. And I can't connect to the samba server from any of
my clients since this morning) But I can access all the other servers
running on the same host.)

What are these "other servers running on the same host"? Are they
virtualization based servers? Or did you really mean "other services",
such as SSH, telnet, or HTTP? In other words, make sure that other
ports on the same host are accessible in order to assure that it's not
a networking issue for the Samba server.

The samba server is running
root     243  0.0  1.9  4784 2356  ??  Is    9:24PM   0:00.02 /usr/
local/samba/sbin/smbd -D
root     245  0.0  1.9  4784 2356  ??  I     9:24PM   0:00.00 /usr/
local/samba/sbin/smbd -D
root     246  0.0  1.3  3104 1624  ??  Ss    9:24PM   0:00.05 /usr/
local/samba/sbin/nmbd -D

smbclient -L SambaServer1 -U%
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.0.20]

--then it lists my shares-----------

netstat -an|grep 137
udp4       0      0       *.*
udp4       0      0  *.137                  *.*
netstat -an|grep 445
tcp4       0      0  *.445                  *.*

And that's all good information to gather for debugging. Well done.

Relevant Pages

  • DMZ host deployment and maintenance procedures
    ... DMZ hosts are static web-content servers. ... another "private" access network contains specialized hosts with access ... Our recommended procedure entails the full configuration of a DMZ host ...
  • Re: registered domain name
    ... IIS servers. ... because of DNS heirachy structure name resolution and local dns ... You should never host a public website on your LAN - you could ... network, that is also a bad idea, in that you would need two DNS servers ...
  • RE: VMware ESX
    ... Because the VMware instances ... are not aware of each other inside the host, ... plugging each isolated VMhost network ... we've got a VMware ESX group of servers running on the inside of our ...
  • slow lookup to non-existent host
    ... When doing a nslookup of a non-existent host on the same network as the bind servers, ...
  • There are currently no logon servers available
    ... I recently added several Windows 2003 servers to my 2000AD. ... joined the domain fine and I can add domain users to resource ACL's however ... it will not resolve however pinging by only the host portion of the name it ... The redir is bound to 1 NetBt transport. ...