Here's my problem:

I got my D-Link 530TX+ card to finally work and got it installed. I know it is properly installed because I can ping its address I assigned it (10.10.0.1) and the internal address (127.0.0.1).

I can ALSO ping the Windows machine that it is hooked up with (on a peer-to-peer, hubless network using Xover cable). My Windows machine is 10.10.0.2.

I can ALSO ping the Linux (Red Hat 8) machine from my Windows machine.

However, when I go to the GNOME Menu > Extras > Server Settings > Samba Configuration, a Mozilla browser window pops up trying to access http://127.0.0.1:901 and I get an alert that says, "The connection was refused when attempting to contact 127.0.0.1:901." and I cannot configure it!

What am I doing wrong?

I appreciate all help.

Thank you much.

I did some searching and came to this thread:

http://www.linuxquestions.org/questi...t=127.0.0.1901

Thanks guys, even though you didn't help specifically me! You're the best!

If it's not one problem, it's another!

Okay...

My Windows Laptop's name is //cp-laptop.
I set up the Linux PC's name in samba to be //cp-linux

They don't communicate with each other.


If I try to do

# smbmount //cp-laptop/c /home/cparker/laptop

from my Linux PC, I get a message saying

16092: Connection to cp-laptop failed
SMB connection failed


In case it's not obvious, I want to mount all the contents of the Laptop's C:\ drive (shared as "C") to the /home/cparker/laptop directory on my Linux PC.

Apparently, samba isn't doing its job, because I can't even mount a share from my own Linux PC.

# smbmount //cp-linux/homes /mnt
16055: Connection to cp-linux failed
SMB connection failed

My Linux PC isn't recognizing its own NetBIOS name???

Still, I can ping my Linux PC from itself

# ping 10.10.0.1
pinging 10.10.0.1 (10.10.0.1) from 10.10.0.1

and I can ping my Windows Laptop from my Linux PC

# ping 10.10.0.2
pinging 10.10.0.2 (10.10.0.2) from 10.10.0.1

However, I never have access to the "localhost" name.

# ping localhost
ping: unknown host localhost

Could this have anything to do with my problem?

I think we dealt with something like that in a really long samba thread here, if I'm right it has to do with the way samba turns names into IP addresses.

smb.conf:
...
name resolve order = bcast host lmhost wins
...

maybe that helps

Can you post your smb.conf file? I would like to start by seeing how it is configured.

here we are:

# Samba config file created using SWAT
# from 127.0.0.1 (127.0.0.1)
# Date: 2003/01/23 00:53:26

# Global parameters
[global]
workgroup = HOME
netbios name = CP-LINUX
server string = Red Hat Linux Box
encrypt passwords = Yes
obey pam restrictions = Yes
pam password change = Yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
unix password sync = Yes
log file = /var/log/samba/%m.log
max log size = 0
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns_proxy = No
printing = lprng

[homes]
comment = Home Directories
path = /home
valid users = %S
read only = No
create mask = 0664
directory mask = 0775

[printers]
comment = All Printers
path = /var/spool/samba
printable = Yes

Okay.

I have never created the smb.conf with Swat and I have not used PAM for authentication. My help may therefore be limited.

I have read that PAM doesn't work with encrypted passwords so this is going to be an issue at some point.

Secondly, make sure that you configured Samba to support PAM.

If you are not sure how to do this, you may want to try setting up Samba to use the smbpasswd file.

Let me know if you want info. on how to set up a simple Samba implementation using the smbpasswd file.

-What exactly is PAM?

-Any information would be helpful.

-Should I have BOTH the smbd AND the nmbd daemons running in order for this to work?

If you don't run the nmbd deamon you won't get any sort of name resolution or browsing happening.

You can still mount shares by putting static entries in /etc/hosts, or (correct me if I'm wrong) /etc/samba/lmhosts and then you will be able to connect using names. But using nmbd is so much easier don't you think?

Don't forget this smb.conf paramater:
/etc/samba/lmhosts sounds right but I think the downloaded samba packages use one dir and every different distro uses something else. Man smb.conf (and the source Makefile) say lmhosts should be in the same dir as smb.conf but make sure you aren't looking for lmhosts in a dir with just a symlink to smb.conf.

Either way using your /etc/hosts works and won't cause any problems with just a small home network.

And here is the simplest smb.conf I can think of for testing. Back up yours and use this if it still doesn't work at this point:
You prolly won't get logged in with this smb.conf but should see both computers in window's net neighborhood, even if the tmp folder doesn't open or let you log in at least you know samba can work and you can merge this with your original smb.conf to get it working.

Just to let you know, I haven't forgotten about this post. I've just been SOOO busy lately.

That, and I kinda gave up for a little while.

I'll try all of your recommendations and get back to you to let everyone know what worked/what didn't work.

Your inablility to ping localhost (post #3) probably comes from someting missing in /etc/hosts file.
(like
127.0.0.1 loopback localhost loghost
10.0.0.1 linuxbox
10.0.0.2 whidowbox
....
)

Chapter 11 of Samba by John Blair gives good step-by-step on how to diagnose a samba SERVER. Still, some of the steps is useful in diagnosing samba client. (Like the use of command smbclient) Or you can try seraching using keywords like SAMBA and DIAGNOSTICS to get to a web page with similar procedures.

You have set your user id/password on your widiwbox, right?
You can try
smbclient '\\windowbox\directory' -U windouwboxusername [-W domainname]
and see if you need a password to "get in".

If you do, try
smbmount //windowbox/directory /mnt/smbmount -o username=windowboxusername,password=windowboxpassword
No space around the comm after -o.

Good luck

make sure nmbd is running
your smb.conf doesn't setup any share files so you won't be able to mount any either from linux or windows.
you don't have a guest account listed in your smb.conf so you will need users in the smbpasswd file. You didn't mention what version of windows you have. 9X machines can use PAM because they don't encrypt passwords. Since you enable encryption on Samba that disables PAM even though you enabled it (hope that makes sense)

I'm currently using a Windows ME machine, although I plan on upgrading to XP Pro.