[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Edlug Archive Mar 2004
]
RE: [edlug] Samba problem
Thanks to all for advice. Unfortunately it looks like the problem
is that I am running XP Home (not Pro), so running into the
traditional 'gimme more money if you want it to work properly' M$
crap. XP apparently lacks certain networking components.
d.
On 6 Mar 2004 at 11:31, Robert (Rob) M. Schneider wrote:
> David,
>
> Samba doesn't provide WINS and isn't something you need turned on XP.
>
> I enclose a few files from my working setup (Samba as file/printer
> sharing along with domain controller running on Linux for 3 xp and Win
> 2003 server machines). Perhaps you can spot differences.
>
> Also, if things still not working, can you reframe the question/issue
> again to clarify what you think is broken and what's needed.
>
> Also ... I've written up what I know (and that's not much) on XP and
> Samba and published it at
> http://www.rmschneider.com/writing/xp_and_samba.html. This also may
> provide you clues.
>
> ---------------------------------------------------
> Robert (Rob) M. Schneider
> RMSchneider Limited
> rmschne@xxx.xxx.xxx
> Phone: 44(0)7793-084230
> Fax (UK): 44(0)8701-68-0997
> Fax (USA): 1-253-295-3085
> ---------------------------------------------------
>
> -----Original Message-----
> From: owner-edlug@xxx.xxx.xxx [mailto:owner-edlug@xxx.xxx.xxx]
> On Behalf Of David R. Baird Sent: 05 March 2004 14:33 To:
> edlug@xxx.xxx.xxx Subject: Re: [edlug] Samba problem
>
>
>
>
>
>
>
>
>
> Thanks for the help, a smidgeon of progress.
>
> I added
>
> 192.168.0.123 zerofive.mshome.net zerofive
>
> to C:\Windows\System32\drivers\etc\hosts
>
> and can now ping zerofive successfully.
>
> I also turned on WINS in the TCP/IP settings (giving it the IP
> number of the Linux box).
>
> Now I get the error 'No service is operating at the destination
> network endpoint on the remote system'.
>
> Still nothing in the samba logs.
>
> ps aux shows smbd and nmbd (2 of those).
>
>
> Then I added the extra global configs
>
> os level = 33
> name resolve order = lmhosts host bcast wins
> dns proxy = no
>
> but no change.
>
> Any more hints? I guess I'll have to get into the XP logs.
>
> Cheers,
>
> d.
>
>
> On 5 Mar 2004 at 12:59, Angus Rae wrote:
>
> >
> > > Hostnames are set up, with XP = eveshampc.mshome.net, and Linux =
> > > zerofive.mshome.net
> > >
> > > From Linux, I can ping eveshampc successfully.
> > >
> > > From XP, I can NOT ping zerofive, but I CAN ping 192.168.0.123
> >
> > No name resolution setup, by the sound of it. Unless you are using
> > DNS, name resolution for most purposes would have to be done via
> > hosts files (/etc/hosts on Unix,
> > C:\Windows\System32\drivers\etc\hosts).
> >
> > One exception is SMB, which can be done via WINS resolution.
> >
> > > On XP, in network places, I see the Linux box, and it has the name
> > > I set up in the Samba config, so at some level they are talking to
> > > each other. However, any attempt to access the machine results in
> > > a '\\Zerofive is not accessible' error, also saying 'The network
> > > path was not found'.
> >
> > Implies that the Samba server is sending out the browse information,
> > but that only contains a hostname, not the IP address it equates to.
> > So when the XP machine tries to connect to \\zerofive it still has
> > no idea what IP address to connect to.
> >
> > > Nothing at all appears in the samba logs, nor in the messages log.
> > >
> >
> > Not surprising, it never gets there.
> >
> > > Here is my Samba config:
> > >
> > > [global]
> > > workgroup = MSHOME
> > > server string = Samba Server
> > > security = user
> > > encrypt passwords = yes
> > > local master = yes
> > > wins support = yes
> > >
> > > [homes]
> > > browseable = no
> > > writable = yes
> > > create mode = 0664
> > > directory mode = 0775
> > > map archive = no
> > >
> > > [data]
> > > path = /home/data
> > > read only = no
> > > map archive = no
> >
> > Seems fine. If you want to avoid configuring a DNS then set up your
> > Windows boxes to use the Samba box as a WINS server by its IP
> > address; the option is on the TCP/IP control panel or if you're
> > using DHCP you can set it via that route. The "wins support = yes"
> > means that you're set up to provide WINS to the network anyway.
> >
> > Of course, if you're in a hurry, then \\192.168.0.123\sharename will
> > work fine; you don't need to resolve the name.
> >
> > --
> > Angus Rae
> > Science & Engineering Support, EUCS, University of Edinburgh
> > The above opinions are mine, and Edinburgh Uni can't have them
> >
>
>
>
> --
> Dr. David R. Baird
> ZeroFive Web Design
> dave@xxx.xxx.xxx
> http://www.zerofive.co.uk
> -
> ----------------------------------------------------------------------
> You can find the EdLUG mailing list FAQ list at:
> http://www.edlug.org.uk/list_faq.html -- Virus scanned by edNET.
>
--
Dr. David R. Baird
ZeroFive Web Design
dave@xxx.xxx.xxx
http://www.zerofive.co.uk
-
----------------------------------------------------------------------
You can find the EdLUG mailing list FAQ list at:
http://www.edlug.org.uk/list_faq.html