Two quick Samba questions EDIT: one down...one to go!

beer

Lifer
Jun 27, 2000
11,169
1
0
EDIT: Alright, I solved the samba issue regarding connecting from an NT machine. Props to all those that helped me, I really appreciate it. Linux is harder than it looks :p at least with KDE3

Now the only issue I am having now is that, when I enter lan:/ in the address bar, all I see are IP addresses. I don't see any hostnames. Anyone got a clue? If you need me to post a config file I will. I don't know what is relevant.
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
You need to create a smbpasswd file with smbpasswd -a username to be able to login with the Linux accounts. Or you can set it up to authenticate against the domain, although if your username really is "Joseph R. Koenig" that might cause problems as most unixes don't like usernames with spaces.
 

Renob

Diamond Member
Jun 18, 2000
7,596
1
81
I think you need to make a workgroup/users/password in the linux box there is a command to do this all in one line. then activate the passwords.

When your in the root# type in---- id then the name of the workstation and see if it comes up. example id pam
 

Renob

Diamond Member
Jun 18, 2000
7,596
1
81
have you made a workgroup and put the other computers in it, have you put in there IP and names in the forward and reverse lookup zones? can you ping them by name and IP from the linux machine??

and the id with the users computer name after it will let you know if there in a group and have a password.
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
Workgroup doesn't matter.
Neither does DNS, broadcasts will be used as a last resort if name resolution fails.

Elemental007:

I now notice you're using 'security = server'. My first guess is that the spaces in your username are causing problems. Try setting 'security = user' and running 'smbpasswd -a jkoenig', you should be able to connect after that.

Also all the lines in the config file beginning with # or ; are comments, there's no need to post them here.
 

Renob

Diamond Member
Jun 18, 2000
7,596
1
81
Try turning off the Firewall in the linux machine.
type setup and click the firewall tab. I think it is set to medium by default.
 

beer

Lifer
Jun 27, 2000
11,169
1
0
Back in the office. About to do these suggestions. Coupla things I wanted to say:

Originally posted by: Renob
Try turning off the Firewall in the linux machine.
type setup and click the firewall tab. I think it is set to medium by default.

I turned it off on the install. No need for it on an internal network for a test machine.

ve you made a workgroup and put the other computers in it, have you put in there IP and names in the forward and reverse lookup zones? can you ping them by name and IP from the linux machine??

I should not have to specify computer names in hosts. There are 100+ hosts on the network and 30 in my domain. It should broadcast for name resolution...but it's not....

what should my broadcast address be??
 

beer

Lifer
Jun 27, 2000
11,169
1
0
Originally posted by: Nothinman
Workgroup doesn't matter.
Neither does DNS, broadcasts will be used as a last resort if name resolution fails.

Elemental007:

I now notice you're using 'security = server'. My first guess is that the spaces in your username are causing problems. Try setting 'security = user' and running 'smbpasswd -a jkoenig', you should be able to connect after that.

Also all the lines in the config file beginning with # or ; are comments, there's no need to post them here.


I did this. I added user 'jkoenig' and also user 'webadmin' with the smbpasswd -a with both smbd and nmbd daemons running. I also switched security to user. I also did a -e to make sure they were enabled (they are).

Now I am getting, from 2000:

//JoeyLinux is not accessible
The credentials supplied conflict with an existing set of credentials.

WTF?
 

Nothinman

Elite Member
Sep 14, 2001
30,672
0
0
Check the log files, if there's nothing interesting turn up the log level.

Now I am getting, from 2000:

//JoeyLinux is not accessible
The credentials supplied conflict with an existing set of credentials.

Apparently you got connected once as somene, you have to disconnect before you can login again. Your choices are 'net use /d \\joeylinux' and that should log you out, if not you can try \\ip.address or logout of Windows and back in. This is one of MS' more obvious stupidities.
 

beer

Lifer
Jun 27, 2000
11,169
1
0
Awesome. I can now long in, and with a symbolic link to var/www, can access what amounts to a remote directory that contains web stuff. Excellent job!

The only other issue is that in lan:/, all I see are IP addresses and no hostnames. Got a clue as to why that is?