lost

[gundamfool]

Well was wondering how I would be able to share windows hard drive and printer with linux server, I kno i can use linux client to connet on to a windows server with smbclient, but how would I get windows to become a smb server? which tool would i use? i thought samba could do this, i was reading and it kept saying linux client connect to windows server to access printer and stuff or maybe I am just confused...help is appreciated

[gundamfool]

oh yeah i use windows 2000

[jumpedintothefire]

When you share a folder or printer it becomes
a server.... nothing special needed on windows just ensure that print and file-sharing is turned on

[gundamfool]

Ok i understand now, printer and file sharing is enabled, but now I have problems with it...when i do smbclient -L 192.168.1.2 (win2kbox) it gives me access denied before, but i don't know what i did but it says this now
====================================
session request to 192.168.1.2 failed (Called name not present)
sesion request to 192 failed (Called name not present)
session request to *SMBSERVER failed (Called name not present)
====================================
I thought it didn't have much to do with mounting the file system so I took a look at smbmount.txt of samba and did "mount -t smbfs //192.168.1.2/c /mnt/winbox" I think thats how i would mount c drive of windows....Anyways it gave me
====================================
session request to 192.168.1.2 failed
session request to *SMBSERVER failed
SMB connection failed
====================================
So now I am lost again =) I got windows to see my linux box though, just need linux to be able to access win2k box

[gundamfool]

Would too ethernet cards mess up samba somehow? like it doesn't know which one is the server?

[mdwatts]

Never setup Samba myself and wouldn't know about the 'two' nics.

Have you read the NHF here on Samba.

There's also a complete free online book available on Samba here http://infobase.informit.com/linux/ of which you will need to register.

[gundamfool]

Yeah, i followed it and it worked, it didn't explain how to access from linux to windows though, only windows to linux


I also am looking at oreilly's free online book about samba =)..I think nmbd has something to with it..well just following the trouble shooting guide at the end of the book and i passed everything except when it came to test using nmblookup, didn't come out quite right so the book tells me to use testparm but that was succesful though...the more i read the more confused i get =(


[This message has been edited by gundamfool (edited 07 January 2001).]

[This message has been edited by gundamfool (edited 07 January 2001).]

[gundamfool]

After reading some more hard to digest stuff, i think i configuration on win2k is wrong...i couldn't follow the samba nhf for windows configuration cause they didn't show how to do it with win2k, i did manage to set everthing except the share-level access part and the browse master part...dunno if they could be of any trouble

[Mountainman]

The way to access from linux to windows is this

smbclient \\\\windowsname\\fileshare

the share you should see if you do a :
smbclient -L windowsname

you could also do it with liNeightborhood.

------------------
---Meddle not in the affairs of Dragons, for thou art but a snack, and tasty with ketchup---
Http://www.geocities.com/mountainmancentral

[Counterstrike]

Are you doing it as a user or root? I know on my box I have a lot of problems trying to map drives in Linux if I'm not root.

Also, W2K has a user/pass database different from the one on your linux box. Do this ->


SU to root
Type ->smbmount //192.168.1.2/c /mnt/winbox -o username="W2K User Here"


If your Windows username contains a space, you'll need those quotation marks, otherwise they're not necessary. It should prompt you with something like:

Password:

Enter your W2K user password (for the account you just typed in). Then type "exit" to return to your user's account. Voila! You should be able to gain access by typing

cd /mnt/winbox

If you have any other questions, post here and I'll be happy to try to help.

[Counterstrike]

Oh yeah, if your C drive on your W2K box is hidden you have to add a $ after the share to signify it's hidden. For example,

smbmount //192.168.1.2/c$ /mnt/winbox -o username="W2K User Here"

You can also use the name of the computer, for example, if your W2K box is called "Server" you can do...

smbmount //Server/c$ /mnt/winbox -o username="W2K User Here"

[gundamfool]

Hmmmmm, I tried all of it, sadly it doesn't work.........I always do it in root....as for errors it gave the same errors for both commands smbclient and smbmount same as mount error

*kickz the computer......or maybe not, still need it*

I'm gonna keep looking at these docs, and maybe take a look at linNeighborHood

[gundamfool]

LinNeighborhood same thing, except that it says Connecting to 192.168.1.2 at port 139 then the session request failed comes up....hmmm port 139? is it a clue?....

[gundamfool]

I can smbclient and smbmount myself if that helps =) so atleast we knows its functional =) heh...I posted like 90% of this thread, just keeping u guys up to date with what i have done and discovered in hope that we lead to a solution=)

[gundamfool]

Hi!!!, back here to post on my current situation with the endless journey to a working samba....i found this in samba's forum:
====================================
Success! The problem was lanman (Solaris PC Net Link), which someone before
me installed on this machine. It wasn't running, but apparently the
software install mucks with something. I was digging around on lonepeak and
came across a directory that looked something like:

DOS----

That prompted me to check the groups file and I noticed a few related
entries and the password file had some SLSxxxx stuff in it. I checked
through the /opt directory and found a directory called lanman with an
uninstall in sbin, so I ran the uninstall (which complained that lanman
server was not running) but proceeded successfully. After that, I kill
-HUP'd smbd/nmbd and smbclient now recognizes it.

This might be worth putting in an FAQ someplace... Session request failed is
not generated from Samba (more likely lanman). If you get the message, see
if lanman is installed.
====================================
I did "find -name *lanman*" but i didn't find anything....maybe it has to do with win2k box...also when I read the DIAGNOSIS.txt of samba it said that my smbclient request is being refused by the client at port 139....=( Also another suggestion i found was /etc/hosts i think its set up fine...I am gettin convinced its bad settings wit win2k but i dunno anything about win2k

[gundamfool]

Ahhh everything has failed http://www.linuxnewbie.org/ubb/frown.gif, i'm gonna install windows 98 on my win2k comp and see if it will work =)

[jumpedintothefire]

check inetd.conf to see if the lines for 137 138 139 are #'ed out if so uncomment them.

then killall -HUP inetd to reload it.

How is the smb.conf setup?
check allowed hosts ...
interfaces...
passwords...

On w2k
who are the allowed users, add quest and set
quest's password to NULL (leave the box blank)


[This message has been edited by jumpedintothefire (edited 09 January 2001).]

[Lorithar]

*grins*

What version of samba are you running... I seem to recall a problem with win2k and older samba versions as MS has once again altered the functions of the Server Message Block.

[FoBoT]

Originally posted by gundamfool:
...maybe it has to do with win2k box......I am gettin convinced its bad settings wit win2k but i dunno anything about win2k

that is what i think, do you have the linux user created on the w2k box? with the same password? did you give that user permissions for the shares on the w2k?

if you haven't used w2k before, it isn't like 95/98, you can't just share a folder. you have to assign who can access the share. you have to create a user account (kinda like linux, gee think that is where the idea came from ? actually NT is the same, anyway) with the same password as the linux client (or 95/98 client)