Date : Fri, 23 Oct 2009 20:58:10 +0200
From : rick@... (Rick Murray)
Subject: Master Ethernet Upgrade
chris whytehead wrote:
> I am trying to mount a PC directory using *MOUNT. The PC runs W2K, is named
> sarah and is part of a domain not a workgroup. The domain controller is a
> W2k3 server which is also the DNS and the domain is chriswhy.local.
> I can ping SARAH, by IP address.
> I can *ping sarah.chriswhy.local , if I try *ping sarah I get "Host not
> known".
This is because nothing knows what "sarah" refers to.
Some routers have the ability to assign names to IP addresses, look up
the DNS part.
Otherwise, you ought to have a "hosts" file on the machine (every
machine!) which hold a simple translation table.
For example, here is mine. It is located at:
C:\Windows\System32\drivers\etc\hosts
It contains some legal blah as comments, then:
127.0.0.1 localhost # generic
192.168.0.1 alyson #*riscpc [10mbit only] ; historical
192.168.0.2 abigail # p75 64mb win95(!) [10mbit]; historical
192.168.0.3 angela # a5000 [10mbit] ; historical
192.168.0.6 ayleigh #*1.1ghz amd 1gb hotpsu! ; videostash
192.168.0.8 azumi #*eeeeeeeeee :-) ; newwork
192.168.0.9 aiko #*450mhz p3 128mb [10mbit!] ; oldwork
192.168.0.99 router # ittybitty 4 port router 10/100baseT
192.168.1.1 livebox # internet whoohoo, but only via wifi
# Notes, lest my tiny wetware fifo buffer overflows:
# > entries prefixed '*' are habitually connected to router
# > livebox & internet *ONLY* available to azumi; note if connecting
# router WAN port to livebox ethernet, current router firewall is
# set to block *ALL* outgoing traffic
# > aiko and ayleigh have open shares used by software; these MUST
# be blocked if the machines go online; simplest solution is just
# to not have connectivity here, it isn't necessary...
# > aiko's etherwire is a crossover so it can be plugged directly
# in to angela, usu for econet transfer (need to find !Gateway !)
# > abigail is a piece of $#!+, too slow to do much (can it even run
# a server on a pseudo-modern linux? is there such a thing as a
# DOS based server?) and as a Presario desktop, it is TOO DAMN BIG.
# > azumi's address is ETHERNET only; the wifi address is DHCP'd (but
# usu 192.168.1.10...
# =eof
This file, annoyingly and wastefully, is copied to the appropriate place
on all machines (and all operating systems, it's somewhere within
!Internet on RISCOS), so everything knows the name of everything else.
On the plus side, however, having a local configuration file means the
machines always know each other's names. No good having the router
'know' Angela (it can't, but if it did...) because as soon as I hooked
it back-to-back to Aiko, suddenly the name would be unknown (no router =
no dns). This way, faff with wires, keep on going. :-)
> If I try to mount sarah's Public directory using *mount, I get:
It won't work. "sarah" is not known, whether you use it as a separate
name (i.e. *ping sarah) or as part of a UNC (\\sarah\...whatever)
> 2. Does the Lanmanager rom support DNS suffix(es), if so how do I specify
> it?
It ought to have a "hosts" file. If you don't see it, look for a small
file containing, as text:
127.0.0.1 localhost
Failing this, you might be able to get your DNS server to do it. Which
machine is acting as the DNS server?
Are all your machines static IP or assigned via DHCP? The hosts file
only works with static IP.
> 4. Without change the rest of the network from a domain to workgroup model,
> how do I make this work?
Are you sure you understand what the domain model means? Don't mix up
Windows networking "domain" with an internet "domain" name. They are
related only by the word "domain"!
I mean... Is that degree of complexity necessary for your setup? Does it
reasonably support non-Windows technologies - given that even Windows XP
*HOME* edition cannot correctly log into a domain server!
If you are looking for centralised user management and such via Active
Directory, a domain is what you want (but all connected computers need
to be in on the act for it to work - could well proclude your Master on
that point alone, does it even support AD's "trust" issues?).
If you are looking for a peer-to-peer setup, a workgroup is better. My
network (described above) is a workgroup...
Refer:
http://www.ntcompatible.com/thread29911-1.html
Oh, and I saw this when looking for info about RISC OS use with "domains":
--8<--------
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.
--8<--------
[
http://newsgroups.derkeiler.com/Archive/Comp/comp.sys.acorn.networking/2006-01/msg00093.html
]
My final quote on the matter:
--8<--------
Windows NT/2000 seems to be Microsoft's answer to everything: file
server, workstation, application server, etc. Makes you wonder how it
can be good at all of them. Well, it's not. And frankly, shared file
service isn't even a top priority; they're too busy trying to turn it
into a stable web platform. For example, after Microsoft bought Hotmail
and converted the system from FreeBSD to Windows, performance suffered
badly (which is to say nothing of its chronic security problems). Its
new "Active Directory" authentication system works only with other
Windows 2000 servers (or clones such as Samba), making it nearly useless
for integrating mixed environments.
--8<--------
The bottom line is the one that interests me the most.
[ http://alternatives.rzero.com/nos.html ]
Best wishes,
Rick.
--
Rick Murray, eeePC901 & ADSL WiFI'd into it, all ETLAs!
BBC B: DNFS, 2 x 5.25" floppies, EPROM prog, Acorn TTX
E01S FileStore, A3000/A5000/RiscPC/various PCs/blahblah...