Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm not sure how to phase this question, but how can I tell if the Linux machine is awake and able to answer network calls from an NT machine.
I've been trying to fix this for just about a week now, every single site/how to/tutorial I've been to has the same basic smb.conf file as mine.
I can see the Linux machine in windows but when I click on it the network path can not be found. Pinging the Linux machine from NT always times out but pinging the other way is fine
I'm starting to think that my smb.conf file is OK but that something else is amiss.
On two of many google searches on this topic I found a couple of your replies in other threads where you mentioned the "iptables -nL" commands, which I tried.
I have no idea what any of the results means but I don't see "error" anywhere, though I noticed that what appears to be IP addresses are all 0. If it helps, I can post what is there, though it would be much easier (I think) if you could tell me what to look for.
I tried "netstat" and can see the machine ip address in the result so assumes that it is working. (I've done both commands a couple of time now and am starting to mix the two result up)
I have no firewall in place anywhere
I know about port 137, 138, 139 and as far as I can tell they are good to go. (Both windows and Linux)
In another thread you also mentioned about permissions and as far as I can tell I own everything that I'm trying to share in Linux.
I have also seen a few times where I have to have matching accounts, (both in windows and Linux) I'm completely lost on that one. where are the accounts supposed to be?
I have done the "smb passwd" and can only have one password/account??? at a time and I have 6 machines that need access to Linux, sometimes at the same time.
This is the second time I've tried to network the two and the first time NT was able to see Linux right away but I couldn't do it the other way, exact opposite of what I'm experiencing now.
I've looked at the smb.conf from the earlier install and can see nothing different between the two, which brings me to the point that the problem must be somewhere else.
Since you can't ping the Linux machine from the Windows machine, it looks very much like a firewall issue. By default, Fedora will set up a firewall and you may not even be aware of it.
From the command line on your Linux box, as the root user execute:
iptables -F
and then try to ping/access the Samba shares.
If it works, you'll need to either disable the firewall on your Linux box or configure it to allow pings/SMB traffic.
I tried "iptables -F" and nothing happened and I tried pinging from window and was the same. Now I'm very new to Linux so your going to have to tell me how to check if there's a firewall.
Code:
[global]
workgroup = BBE
netbios name = BBE_SERVER
server string =
; message command = /usr/bin/linpopup "%f" "%m" %s; rm %s
printcap name = cups
load printers = yes
printing = cups
printer admin = @adm
; printer admin = @"Domain Admins"
log file = /var/log/samba/log.%m
max log size = 2000
log level = 8
; hosts allow = 192.168.1. 192.168.2. 127.
guest account = nobody
map to guest = bad user
security = user
; password server = <NT-Server-Name>
; password server = *
; password level = 8
; username level = 8
; min passwd length - 8
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
; unix password sync = Yes
; pam password change = yes
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n
; *passwd:*all*authentication*tokens*updated*successfully*
; username map = /etc/samba/smbusers
; include = /etc/samba/smb.conf.%m
; winbind uid = 10000-20000
; winbind gid = 10000-20000
; winbind separator = +
; winbind use default domain = yes
; template homedir = /home/%D/%U
; obey pam restrictions = yes
; template shell = /bin/bash
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
; interfaces = 192.168.12.2/24 192.168.13.2/24
; remote browse sync = 192.168.3.25 192.168.5.255
; remote announce = 192.168.1.255 192.168.2.44
local master = no
os level = 10
domain master = no
preferred master = no
; domain logons = yes
; logon script = %m.bat
; logon script = %U.bat
; logon path = \\%L\Profiles\%U
; logon home = \\%L\%U\.profile
; add user script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Account' -s /bin/false -M %u
; add user script = /usr/share/samba/scripts/smbldap-useradd.pl -w -d /dev/null -g machines -c 'Machine Account' -s /bin/false %u
; add user script = /usr/sbin/useradd -s /bin/false %u
; domain admin group = root @adm
; domain guest group = nobody @guest
; ldap admin dn = cn=root,dc=mydomain,dc=com
; ldap ssl = start_tls
; ldap port = 389
; ldap suffix = dc=mydomain,dc=com
; ldap server = ldap.mydomain.com
; name resolve order = wins lmhosts bcast
wins support = yes
; wins server = w.x.y.z
; wins proxy = yes
dns proxy = no
preserve case = yes
short preserve case = no
default case = lower
case sensitive = no
Mangle case = yes
client code page = 850
character set = ISO8859-1
[homes]
comment = Home Directories
browseable = yes
writable = no
; vfs object = /usr/lib/samba/vfs/recycle.so
; vfs options= /etc/samba/recycle.conf
; veto files = /*.eml/*.nws/*.dll/*.mp3/*.MP3/*.mpg/*.MPG/*.vbs/*.VBS/
; [netlogon]
; comment = Network Logon Service
; path = /var/lib/samba/netlogon
; guest ok = yes
; writable = no
; root preexec = /usr/bin/ntlogon -u %U -g %G -o %a -d /var/lib/samba/netlogon/
; root postexec = rm -f /var/lib/samba/netlogon/%U.bat
;[Profiles]
; path = /var/lib/samba/profiles
; browseable = no
; guest ok = yes
; writable = yes
; root preexec = PROFILE=/var/lib/samba/profiles/%u; if [ ! -e $PROFILE ]; \
; then mkdir -pm700 $PROFILE; chown %u.%g $PROFILE;fi
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
guest ok = yes
writable = no
printable = yes
create mode = 0700
print command = lpr-cups -P %p -o raw %s -r
; print command = lpr-cups -P %p %s -r #
; lpq command = lpq -P %p
; lprm command = cancel %p-%j
[JAN_COLLECTION]
comment = Stock piled software
path = /home/jan/Collection
browseable = yes
public = yes
guest ok = yes
writable = yes
If iptables -F didn't solve the problem then it's not a firewall issue.
The problem with not being able to ping the Linux machine from your Windows machine could be related to a setting in the proc file system. Execute this command as root on the Linux machine:
echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_all
Then try to pinging from Windows to Linux again.
Unless you definitely want to use your Samba server as a WINS server, remove the line:
wins support = yes
from your smb.conf file and restart samba. Then try to access your Samba server again from Windows. If you can't access it from Windows explorer, try executing this from the command line on your Windows machine:
net view \\BBE_SERVER
That should show you a list of the shares on your Samba server.
If that doesn't work, execute:
net view \\ipaddress
Substitute the IP address of your Samba server in the command.
Symptom 1. Pinging from the Linux machine to the NT machine works fine. Pinging from NT to Linux does not work.
There are 2 things that I'm aware of that usually cause this:
A firewall blocking the pings is the most common. When you executed iptables -F, that should have flushed the iptables firewall and allowed the ping requests to come in from the NT machine. It looks like an iptables firewall is not the problem.
The file /proc/sys/net/ipv4/icmp_echo_ignore_all containing a 1. This basically tells the kernel not to respond to pings. It's a security measure to make the machine less visible on the network. You changed the files contents to 0 and that didn't solve the problem so that eliminates that. This file usually contains a 0 by defualt. The only time I've seen it changed to 1 without the user being aware of it is by some sort of firewall software.
Symptom 2. The Samba server can be seen on the network but every time you try to access it, you get an error something similar to system error 53 has occured. The network path not found. There are 2 things that I'm aware of that usually cause this:
A firewall on the Linux machine. The Samba server announces its presence on the network by using broadcasts. These are not blocked by the firewall therefore the Samba server's presence is detected on the network. However, when you try to access the Samba server, the firewall blocks that traffic. We've already proven that it's not an iptables firewall issue.
The nmbd portion of Samba is not working properly. This is the portion of Samba that takes care of identifying itself on the network and other name resolution issues. We'll need to make some tests for that.
First we need to make some ping tests. Lets make sure the Linux machine can ping itself. Execute this from the Linux command line and post the results here:
ping -c 5 "ipaddress of your Linux machine"
Just put in the ip address of the Linux machine.
Next, I want to see the results of the ping to the NT machine. Execute this from the Linux command line and post the results here:
ping -c 5 "ip address of the NT machine"
Second, lets run some tests from the Linux machine to see if the Samba server is up and running. These next few tests should display the shares you have set up on your Samba server. Execute these from the command line of the Linux machine and post the results here:
smbclient -L localhost -N
and
smbclient -L bbe_server -N
If those 2 commands generate a list of shares on your server, try this one:
smbclient -L localhost -Uusername
Put in one of the Samba user accounts you created on your server. It should prompt you for the password and then display the list of shares.
Finally, I'd like to see processes running on your Linux machine. Execute this command:
ps -e > ps.txt
This saves the results of the ps -e command in a file named ps.txt. Paste the contents of ps.txt in your response.
first off I'd like to thank you for your time and knowledge.
What I did was cut and paste your commands into konsole and I'm a little hesitant to just paste all the result in one post, by reading the result I understood what the commands were "asking" so I'll just post summaries and if you need more I'll post everything as needed.
Both
ping -c 5 "ipaddress of your Linux machine" and
ping -c 5 "ip address of the NT machine" returned this
5 packets transmitted, 5 received, 0% packet loss, time 3997ms
smbclient -L localhost -N
smbclient -L bbe_server -N
smbclient -L localhost -Uusername. (I used both root and my account on the last one)
All returned basically the same results which I recognize from smb.conf file. Now as I said I'm new to Linux and want to understand, both bcast and nmask look odd to me
Sharename Type Comment
--------- ---- -------
homes Disk Home Directories
print$ Disk
pdf-generator Disk
pdf-screen Disk
pdf-printer Disk
pdf-prepress Disk
JAN_COLLECTIO Disk Stock piled software
VIDEO Disk Video
MUSIC Disk Music
BBE_BACKUP Disk BBE Backup
BBE_GLOBAL Disk For general use
IPC$ IPC IPC Service ()
ADMIN$ Disk IPC Service ()
usually when I get a new OS I install it a couple of time to get a feel for it and on this last install I was a little picky about some of the packages that I wanted;
Webmin is installed but not running
SWAT is not installed
I'm using linNeighborhood
I lost the KDE menu and it took a bit of work to get it back but I knew what I was looking for, so I don't think I messed anything up.
This time I did nothing with the gateway setup cause I don't need internet on this machine
When I installed I set the security to high
My root password is only 7 charactors but install didn't tell me to use 8 like it usually did
Now I know some of these things may sound ridiculus and have nothing to do with what's going on, but I have seen weirder things in windows. . . and my kids
I beleive the maximum length for the name of a share is 15 characters. JAN_COLLECTION comes in at 14.
As long as you can access it as \\BBE_SERVER\JAN_COLLECTION from your Windows machines, I wouldn't worry about it. It may just be that the output of the smbclient command is truncating a character.
If you can only access it as \\BBE_SERVER\JAN_COLLECTIO from Windows, I would shorten the name of the share to avoid problems in the future.
Still quite new to Linux So I'm not quite sure how to answer.
It was (Past tense, I already uninstalled it) called Shorewall in the "service list." I saw it during boot up and shut down and it was called Shorewall there also.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
I've been to has the same basic smb.conf file as mine. 
