|
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
|
RE: [PLUG] Intresting question regarding SAMBA
|
Does the problem exist using the same windows login?
Try a couple of things...
1) Is the second machine's IP in your hosts file?
2) Make sure your workgroup is the same on all machines.
3) If the shares are not public, you will need to have encryption
configured. Since you are 98, I will assume that this is the case.
4) You will need to make sure SAMBA is aware of your user name and password.
Without it, the other machine will be rejected. Period. Use smbpasswd, I
believe to configure your smb password file.
5) Is their a domain controller on the network? Is it aware of your second
machine and user id?
This was a trial an error process for me as well. It all came down to SMB
passwords and how the shares were configured (i.e. additional users). You
may also try using unix->smb id mappings as well if your unix login is
different from your windows login.
The DNC problem surfaced with our VPN. Seems one guy had a DNC on his
network that only knew of his machines. Whenever he connected, we lost
network neighborhood.
Charles
-----Original Message-----
From: plug-admin@lists.nothinbut.net
[mailto:plug-admin@lists.nothinbut.net]On Behalf Of Michael W. Ryan
Sent: Wednesday, April 12, 2000 10:24 AM
To: plug@lists.nothinbut.net
Subject: Re: [PLUG] Intresting question regarding SAMBA
On Wed, 12 Apr 2000 DrexelDG@aol.com wrote:
> Question of the day is.... I have two Win98 SE machines in the office
here.
> One can work on the linux, meaning linux shows up in network neighborhood,
> and I can access the /home directory of the user that I made in the linux
> machine. The other one does not like to do this. I can FTP in on the
second
> one, but there is no access through the network neighborhood. I tried
> readding the user, shutting down SMB, and restarting it, shutdown the CPU
and
> restarting it. I even tried renaming the Win98 machine that does not
work,
> to see if I could get it to work that way. THat did not work either, and
nor
> did changing the IP address of the machine in question.
The network neighborhood should never be considered a diagnostic; look at
it as simply a user convenience. (I could explain why, but's not that
pertinent to Linux :).
Are you able to access /home directory (from the problem child) via UNC
type in through Start->Run?
Michael W. Ryan, MCP, MCT | OTAKON 2000
mryan@netaxs.com | Convention of Otaku Generation
http://www.netaxs.com/~mryan/ | http://www.otakon.com/
No, I don't hear voices in my head;
I'm the one that tells the voices in your head what to say.
______________________________________________________________________
Philadelphia Linux Users Group - http://plug.nothinbut.net
Announcements - http://lists.nothinbut.net/mail/listinfo/plug-announce
General Discussion - http://lists.nothinbut.net/mail/listinfo/plug
______________________________________________________________________
Philadelphia Linux Users Group - http://plug.nothinbut.net
Announcements - http://lists.nothinbut.net/mail/listinfo/plug-announce
General Discussion - http://lists.nothinbut.net/mail/listinfo/plug
|
|