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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
You only need to set up the "Client for Microsoft Networks" and the TCP/IP protocol. If you can see the server name (the NetBIOS name) in your Network Neighborhood window then you've already got it. You don't need to set up "File and Printer Sharing" as that is only needed to share files + printers _from_ the Windows client.
this is my smb.conf. All I can say is,...remove everything from the file and use ONLY what you need. This is what I used to get mine working,.........finally,....lol
workgroup = workgroup
encrypt passwords = yes
server string = FILE BITCH
security = user
comment = For testing only, please
path = /var/ftp/pub
read only = no
guest ok = yes
comment = whatever you want here
Your 'hosts allow' is a little on the funky side. If you want the entire subnet to see it, you should use 184.108.40.206 255.255.0.0 as the bitmasking will be, well, different. I'm too lazy to find it right now, but if you look through the Net2 HowTo you should be able to find the netmask section. Have a look.
A 'netbios name' for your server might help windows see the server.
If you have 'win support = yes' then you might also want to add ' name resolve order = wins lmhosts host bcast '
Gotta run - We're having a garage sale and it's super busy!
Thanks for all the posts - even while having a garage sale! Hope it went well. I've worked at many a garage sale that's gotten out of hand and gave me nightmares about haggling with the oddest of people.
If anything, I'm learning a lot about my system, but still no luck with an actual connection to Samba from my Windoze box. (//BigRed not accessible...)
Here's the latest:
*There's a dail up TCP/IP, which I don't touch.
*The Ethernet TCP/IP settings are:
Wins: 192.168.1.1 (Linux)
No Gateway or DNS are defined, since it didn't seem to help any.
*The login I use is the same as my main LInux user (non-root).
*Network neighborhood will sometimes show the linux box (I successfully changed the hostname to BigRed), and other times it will not show it, and only show Gateway or say that the network is not browseable. It seems to mostly show BigRed after a reboot. Then if I close the NN window and reopen it, there's either nothing except the Entire Network icon, sometimes joined by Gateway.
*I added BigRed to the C:/Windows/host.sam file, and also created an Lmhosts.sam file:
192.168.1.1 BigRed #PRE
But this doesn't seem to matter as I can only ping BigRed by IP, and not name.
No default Gateway or Device specified.
matt:500:long encrypted password
*For the smbusers file, I added the last line as an experiment, which didn't help:
root = admisitrator admin
nobody = guest pcguest smbguest
matt = smbuser user
At risk of insulting you...
1 Setup network.... ping your localmschines
2 Setup Samba ..... see yourlocalmachines
3 Setup NAT via IPTables i.e. minimum
echo =1 /proc/sys/net/ipv4/ipforward
or something like that.
There are multiple posts on these boards about NAT and I don't have access to my RH machine to tell you exactly what you need to type, but that's nearly it!
I had the same problem for many days and many hours. (Yes, I'm a newbie to linux.) I even bought that Craig Hunt book. Today, I determined myself to fix it and found out that my ipchains firewall was configured to disallow all inbound connections except a few. I'm running redhat 7.1, and I configured the firewall when I installed it.
Here's my updated /etc/sysconfig/ipchains file:
# Firewall configuration written by lokkit
# Manual customization of this file is not recommended.
# Note: ifup-post will punch the current nameservers through the
# firewall; such entries will *not* be listed here.
-A input -s 0/0 -d 0/0 22 -p tcp -y -j ACCEPT
-A input -s 0/0 -d 0/0 80 -p tcp -y -j ACCEPT
-A input -s 0/0 -d 0/0 21 -p tcp -y -j ACCEPT
-A input -s 0/0 -d 0/0 139 -p tcp -y -j ACCEPT (***added***)
-A input -s 0/0 -d 0/0 139 -p udp -y -j ACCEPT (***added***)
-A input -s 0/0 -d 0/0 901 -p tcp -y -j ACCEPT (***added***)
-A input -s 0/0 -d 0/0 -i lo -j ACCEPT
-A input -s 220.127.116.11 53 -d 0/0 -p udp -j ACCEPT
-A input -s 18.104.22.168 53 -d 0/0 -p udp -j ACCEPT
-A input -s 0/0 -d 0/0 -p tcp -y -j REJECT
-A input -s 0/0 -d 0/0 -p udp -j REJECT
I added the three lines to enable samba on port 139 and swat on port 901 and it worked.