Re: WindowsXP and RISC OS computers
- From: Alan Adams <alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 08 Jan 2006 20:02:24 GMT
In message <205a0be64d.D_Lane@xxxxxxxxxxxxxxxxxxxx>
David R Lane <D_Lane@xxxxxxxxxxxxxxxxxxxx> wrote:
> In message <dpiroi$g9u$1@xxxxxxxxxxxxxx>
> Mike Sandells <mike@xxxxxxxxxx> wrote:
>
> [snip]
>
> > Just so that I'm clear on exactly what you're saying above;
> >
> > - You ran !Samba on Nixiyo (10.0.0.101)
>
> Yes
>
> > - You configured samba with a share called Public, pointing to the
> > local directory ADFS::HardDisc4.$.Public
> > (Presumably with no share password set)
>
> Yes
>
> > - You tried to connect to Nixiyo from a windows XP machine
> > (IP address not indicated, but presumably a 10.0.0.X address)
> > and received the error described.
>
> Yes (see below for LAN ip addresses)
>
> > - You can however ping Nixiyo from the windows XP machine, both by
> > name and by address.
>
> Yes
>
> > Is this right?
> Yes
>
> > Do you have other machines on this network - i.e. is there another RISC
> > OS box you could use to connect to the samba share to check that it is
> > working?
>
> A Risc PC, but that is no better, but see below.
>
> > What other options do you have set in Samba?
>
> In Global Variables I have the default ones, in particular:
> server string: RISCOS Samba server
> interfaces: 10.0.0.101/255.0.0.0
> workgroup: WORKGROUP
> null passwords
> nameserver enabled
>
> (encrypt passwords and detect !LanMan98 not ticked)
>
> protocol: NT1
>
> Everything else left at default values.
>
> I notice on the centrex machine (Windows XP with SP2) the workgroup
> has name MSHOME, not WORKGROUP. Some say that this doesn't matter for
> what I need.
It doesn't prevent access. It does make browsing more difficult.
> [snip]
>
> > Mike
>
> I have just had some, limited success! :-)
>
> 1) Sharing Windows Directories.
> I discovered that the Server Name as LanMan98 calls it, or Computer
> Name as M$ calls it, had been changed on the centrex machine. It had
> been changed to the User Name, i.e., both were the same (= Kumari).
> Presumably, this can't happen without human intervention. I suspect
> that my Son has changed it at some point. Having changed it back
> to CENTREX, I can see the two shared directories on the centrex
> machine from both the Iyonix and Risc PC computers. So this part
> is solved.
>
> 2) Sharing Iyonix and Risc PC directories.
> Samba is configured the same way (see above) on both machines.
> I still cannot connect to either from centrex via the command line.
> Neither icon appears in My Network Places on the centrex. However,
> 'right' clicking on My Network Places icon produces a Search for
> Computers window where you have to enter a computer name. Entering
> 'iyonix', after a pause of about half a minute, produced an icon
> for Nixiyo with caption "RISCOS Samba Server (iyonix)". From there
> I could see the contents of Nixiyo's Public directory.
WindowsXP in this respect I find less friendly than Win9x and NT4. Those has
network neighbourhood, which showed you the members of the domain/workgroup
as currently known to the master browser, and hence running within the last
15 minutes or so.
My Network Places shows places you've accessed in the past, or added
manually. From there you need to select "view workgroup computers" on the
left-hand panel to get the old "Network Neighbourhood" display, and then
click "Microsoft Windows Network" to see the list of domains and workgroups.
(This requirement to use the left-hand panel prevents me from using "classic
mode" which I otherwise prefer.)
If you do that with your setup, you should see two workgroups - workgroup
and mshome. Opening the relevant one should show you the shares.
> Repeating this for the Risc PC gave the response of "no results".
> :-((
>
> I have checked the hosts files on all three machines and they all
> include the lines
> 10.0.0.2 router
> 10.0.0.100 riscpc
> 10.0.0.101 iyonix
> 10.0.0.102 centrex
> 127.0.0.1 loopback localhost loghost
>
> (Nixiyo has an extra line for an iMac)
>
> I found the Hosts file for the Risc PC (on Adjust 4.39) in
> !Boot.Choices.Hardware.Disabled.Internet.Files . Is this right?
> The information was input via the Boot Configuration application
> which doesn't show the Hosts file. I am the only user of the Risc
> PC. There is no Hosts file in Choices.Users.Single.Internet nor
> in Choices.Default.Internet . Pinging works in all directions, by
> ip address or name.
Name resolution can get complicated. There are three mechanisms at work here.
TCP/IP standards provide DNS (domain name system) and hosts file, which is
older. These are the two used for resolving names for Internet use for
example.
Within a LAN there is also the Windows name browsing mechanism. This works
by a complex exchange of broadcast messages, and results in one machine on
the network being elected master browser, and possible a second as backup
browser. In your setup the master will be Centrex, and there will be no
backup.
The master browser builds up a list of machines on the network by listening
for "hello" broadcasts as machines start up. Browsing the network (e.g.
clicking on Microsoft Windows Network and opening a workgroup) is
interrogating these lists, fetched from the master browser on request. Hosts
and DNS are not involved. (When there is an Active Directory domain involved
then the story gets more complex, and DNS is involved, but that's a whole
different can of worms.)
Typing \\10.0.0.1 doesn't use name resolution at all. Typing \\iyonix does a
DNS and hosts lookup (and failing that also a Windows lookup) for the name.
That's why these methods can work when browsing doesn't.
Browse master problems are complicated in routed networks, and when more
than one protocol is in use. There is one MB for each protocol on each
network, and they may be different machines for each protocol.
Incidentally the confusion between a Windows domain (e.g. Workgroup) and a
TCP/IP one (e.g. riscos.org) is messy. Before Active Directory there was no
connection between them. With AD there is a strong link, and it is
recommended that the names should be the same, to avoid confusion.
In fact to add to the confusion a workgroup and a domain are different (so
the above is a bad example), but they are used in the same way, as part of a
name, and I imagine most of the code to deal with them is common.) A PC can
be in a domain or a workgroup, but not both.
>
> Thanks for help so far,
> Dave Lane
>
Regarding your other post - if you have Access (ShareFS) running, then the
menu from any disc has a share option. Ticking this allows peer-to-peer
sharing, which means other RISC OS systems, including VirtualAcorn.
As you saw, it's nothing to do with Smbserve, but it can cause confusion.
--
Alan Adams, from Northamptonshire
alan.adams@xxxxxxxxxxxxxxxxxxxxxxxxxxx
http://www.nckc.org.uk/
.
- Follow-Ups:
- Re: WindowsXP and RISC OS computers
- From: David R Lane
- Re: WindowsXP and RISC OS computers
- From: Brian Carroll
- Re: WindowsXP and RISC OS computers
- References:
- Re: WindowsXP and RISC OS computers
- From: Mike Sandells
- Re: WindowsXP and RISC OS computers
- From: Mike Sandells
- Re: WindowsXP and RISC OS computers
- From: David R Lane
- Re: WindowsXP and RISC OS computers
- From: Mike Sandells
- Re: WindowsXP and RISC OS computers
- Prev by Date: Re: Is there an app
- Next by Date: public dns
- Previous by thread: Re: WindowsXP and RISC OS computers
- Next by thread: Re: WindowsXP and RISC OS computers
- Index(es):
Relevant Pages
|
