Date : Sun, 25 Oct 2009 13:00:00 -0000
From : christopher.whytehead@... (chris whytehead)
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.
I have a Windows domain and the DC is both DHCP and DNS server, rather than
the router.
> Otherwise, you ought to have a "hosts" file on the machine (every
> machine!) which hold a simple translation table.
>
on Sprow's advice I have added suitable Host entries to the configuration
file and "*ping sarah" now works
>
> > 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
See above
>
> Failing this, you might be able to get your DNS server to do it. Which
> machine is acting as the DNS server?
DNS server is the DC, but the DNS server servers a domain and therefore
expects the domain suffix. In fact the TCP/IP client can be configured to
try different domain suffixes until a match is found or it runs out of
suffixes. Look in the DNS tab in a Windows Network configuration, usually in
TCP/IP properties/advanced/DNS.
>
> Are all your machines static IP or assigned via DHCP? The hosts file
> only works with static IP.
>
Mixed static for normal machines and DHCP for occasional one. sarah is
static IP. master is DHCP. Sarah is in DNS server and Master's host file
now.
>
> > 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"!
Yes I am aware of the difference and what the different domains mean. Not so
hot on Active Directory ...
> 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!
Yes, I am using the Professional versions, 'cos I also use the set up as a
test bed for work problems.
> 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?).
A domain is what I need. It's not actually true that all computers have to
be in on the act. My Iyonix works perfectly well with the Windows domain,
accessing shared folders on the server using either Lanmanager (Omniclient
2.12) or NFS using !Sunfish and Microsoft's Window's services for Unix on
the server.
> 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.networ
king/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...
_______________________________________________
bbc-micro mailing list
bbc-micro@...
http://lists.cloud9.co.uk/mailman/listinfo/bbc-micro
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.423 / Virus Database: 270.14.25/2450 - Release Date: 10/23/09
06:56:00