Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
ok, i'm new to linux and like it. sometimes. I'm a convert from windows and have become quite obcessed with linux.
i run 98 on two machines, laptop and newly built box...and linux on an old PB p1 266/64mb/3.2g - im just experimenting with linux here, but plan to run linux/smb server on the new box and network the laptop and PB, at least one will still have 98.
so, i have not been able to see anything more than teh server in my network icon on the 98 machine. i can't get into the file with out a password error. "ipc$" ???
I can't get the swat utility working either, since /etc/inetd.conf doesn't exist.
I've read many books and info on the net about smb, but am still having difficulites making sense of all this.....there isn't too much trouble shooting help in the books, they assume all works well the first time around, but no help if it doesn't.
Your having the same problems that I am having.
1. The docs are ancient.
2. People telling you to read the docs.
3. Every doc is for a different distro than your using.
4. No distros are set up the same.
And we wonder why linux isn't mainstream (no flames please, I am aggravated)
I set up all the proper fields according to intructions, but i always get, at best : name of server in network neighborhood, but can't access any shares. no pw prompt or anything.
if i do # smbclient -L (sharename)
it says connection to (sharename) failed.?
so what should i do besides go back to windows and use peer - peer,,,,,,,naaaaaa, that wouldn't happen, i'll figure it out, but some help would be vital. - for my marriage, my stability, my ego,,,you guys get it.
fail66: you're right about this not being mainstream. It is not intuitive at all, but there is alot of potential with it if you have the time and patience, which i have neither right now.
and thanks to all those who read the strings but don't post anything. even if it is a newbie flame!
I can't pretend to be an expert (only been using linux for a few months), but I've managed to get Samba and Swat (partially) working. The guide I followed was at http://www.linuxnewbie.org/ - do a search on samba.
For information, you are right - the documentation you have is out of date. inetd has been replaced by xinetd (more secure). Xinetd has two parts - a file called /etc/xinetd.conf which refers to (the second part) a directory called /etc/xinetd.d. This directory contains a number of little files which used to be included in inetd. You should have a file in here called swat.
I hope this information helps. If not, I'll post the configuration files I use.
My experiance with Samba has had its ups and downs spent 2-weeks geting it to work read the online Samba manual front to back twice. http://www.oreilly.com/catalog/samba/noframes.html
But now one year later and 93-days uptime
(would be longer if I'd leave it alone)
I'm completly happy alot of the problems I encountered were my own fault... RTFM
alot of errors are somtime's clarical somthing I spelled wrong did not put Browsable in the corect field did not set up a host file correctly forgot a dot between the IP's the above link is my bible a little outdated but if read correctly all is gold (I'm in debt to google.com) just type in an error message and walla!!
did you set up a group or user to allow browsing ???? is your security set for user, or share , or domain and last server SWAT kicked my butt till I found out via Google that a binary I installed set the htlm files in a differnt directory moved the files and BINGO
Dear All Forum Readers,
I tooooo am screwed with this samba.
I have installed it properly. I have smb.conf in /usr/local/samba/lib.
# Global parameters
workgroup = excelinux
server string = Samba Server
interfaces = 10.1.1.7/10 127.0.0.1
hide dot files = Yes
path = /home/public
dns proxy = No
security = share
bind interfaces only = Yes
log file = /var/log/samba/log.%m
guest account = smbuser
wins support = true
os level = 65
max log size = 50
read only = No
comment = Public
read only = No
directory mask = 0775
guest ok = Yes
comment = Data
path = /home/samba/data
read only = No
create mask = 0660
directory mask = 0770
guest ok = Yes
1) Swat dont run
2) if I start samba as ./smbd -D and then ./nmbd -D it starts well. But if I say ./smbstatus it puts this
Samba version 2.2.2
Service uid gid pid machine
No locked files
3) if I say ./smbclient -L localhost (from my linux box.) it thows
[root@rajesh lib]# ../bin/smbclient -L localhost
added interface ip=10.1.1.7 bcast=10.63.255.255 nmask=255.192.0.0
added interface ip=127.0.0.1 bcast=127.0.0.255 nmask=255.255.255.0
error connecting to 127.0.0.1:139 (Connection refused)
Connection to localhost failed
My setup is like this
1) myself rajesh localhost running Linux box samba server name excelinux
2) two other machines (win-me) [YES everything wins etc. etc. etc. is set as read from all the forums and Ying Zhang's Samba Server Step by....Guide.
Can anybody be polite on me and tell me just why
1) I dont see the shares from winboxes (I just see a group excelinux...and exploring it shows on the two winboxes)
2) CAN I PRINT ON PRINTER ATTACHED TO WINBOX SINCE I HAVE SAMBA INSTALLED.(If yes HOW?)
But I have spent about a month on this and not getting any success so please please help me.(OR help me to KEEP LINUX ALIVE IN THE HEART OF ITS LOVERS)
As I said, I'm no expert with Samba, but I have managed to get it running.
Not sure about all of your problems, but it took me a while to get swat to work. After that everything else seemed to fall into place.
The swat file I use in xinetd.d is:
# default: off
# description: SWAT is the Samba Web Admin Tool. Use swat \
# to configure your Samba server. To use SWAT, \
# connect to port 901 with your favorite web browser.
port = 901
socket_type = stream
wait = no
only_from = localhost
user = root
server = /usr/sbin/swat
log_on_failure += USERID
disable = no
Also check that your lmhost, host, and hosts.deny files are all ok.
What exactly is the error you get when you try to connect to Swat?
ok. after banging my head for several days, and tossing my box against the cinder block wall a few times samba finally decided to work.
I reloaded my windows machine which I suspect was a problem since i was tampering with the registry, so starting clean helped.
equipment: Packard Bell 233/3.2gig/64mb netgear nic
Compaq Presario 1930 - laptop, 433celeron/9.5gig/192mb/3com pc card nic
Linksys etherfast cable/dsl router
I just configured the laptop with tcp/ip for connectivity, used ms login and that was it in windows.
I used webmin to setup shares on the PB and it worked, beofore all i could see at best would be the server in windows networkneighborhood...albeit unstable.
I am no master, but if anyone needs help with BASICS, i maybe able to help if you email me.
I know how you all feel. Samba can be an absolute nightmare. The most important thing to remember is that if you don't have a PDC set up (if you don't know what that stands for, you don't) you need to have samba do your password authentication. There are some great posts to this effect on another samba thread: