Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
did you setup your samba config and get these errors, or did you just try to access it from win2k and thought that was all that you were supposed to do ?
I do not know much about Samba but, you should be able to ping your Linux box even if Samba was not installed or running. I do not think that Samba is your main problem. You might want to try pinging the loopback address on each computer first. In either Windows or Linux the loopback address is 127.0.0.1 Have each computer ping its own loopback address. If the can ping their own loopback addresses then TCP/IP and you network interface cards are probably working. Also, see if there is anything else that you can ping. You said the Windows box can not ping the Linux box. What about the Linux box pinging the Winows box.
Are you using static IP addresses that you assigned yourself or are you using dynamically assigned IP addresses from a DHCP server. If this is a simple home network and you happen to be using static IP addresses then make sure that both addresses are appropriate for the same network segment. If the numbers were too much different a router would be needed. If this is a home network and these computers do not need to be accessed by users on the Internet, you would most like want to use number that are in a range that is set aside for private IP addresses.
You should also look at the back of each computer and other network devices to see if the green LED near the RJ-45 plug is on. Are the computers connected to a hub with ordianry straight through CAT5 cable or are they directly connected to each other with a CAT5 crossover cable? It seems to me that you need to get your network working before worrying about Samba.
I agree with the suggestion that Peacdog made about looking at the output of ifconfig. On your Linux box the command would be ifconfig, in Windows 2000 the equivalent command would be ipconfig. Note that they are not spelled exactly the same.
In Linux when logged in as root all you need to do is type ifconfig. When logged in as a regular user you need to type /sbin/ifconfig or at least that is how it works on my computer. If you are using a static IP address using an inappropriate IP address and subnet mask would be among the most likely causes of your problem.
I have a basic set up with the Linux box (mandrake 9.1) connected to ADSL and also a hub. The hub also has three w2k machines connected to it. All using non twisted pair cables.
The windows boxes interact with each other ok.
Here is my smb.conf file.
# Samba config file created using SWAT
# from localhost (127.0.0.1)
# Date: 2004/02/20 00:12:24
# Global parameters
[global]
workgroup = WORKGROUP
netbios name = LINUXBOX
server string = Samba Server test %v
encrypt passwords = Yes
map to guest = Bad User
log file = /var/log/samba/log.%m
max log size = 50
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
printcap name = cups
dns proxy = No
wins support = Yes
default service = homes
printer admin = @adm
read only = No
printing = cups
[homes]
comment = Home Directories
path = /home/smbuser
guest ok = Yes
[printers]
comment = All Printers
path = /var/spool/samba
create mask = 0700
guest ok = Yes
printable = Yes
print command = lpr-cups -P %p -o raw %s -r # using client side printer drivers.
browseable = No
[print$]
path = /var/lib/samba/printers
write list = @adm root
guest ok = Yes
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.