NT PDC and Visionfs
Jim Richardson
Boy it would be nice if some of you folks that know lots more than I
could give a short course on the relationships of Vision Logon Servers
and NT PDC servers. This will become increasingly important as we move
towards single logons.
Sure hope you're out there.
--
Jim Richardson
I like NT because it constantly reminds me of my daughter.
"Honest Daddy, I wasn't doing anything and it just broke."
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
Chad Lemmen
Jim Richardson wrote:
> Hey SCO Folks
>
> Boy it would be nice if some of you folks that know lots more than I
> could give a short course on the relationships of Vision Logon Servers
> and NT PDC servers. This will become increasingly important as we move
> towards single logons.
>
> Sure hope you're out there.
>
I've posted twice asking for help on getting VisionFS to act as a logon
server for my Win98 machines, but I haven't gotten any replies. I guess no
one is doing it or maybe they aren't having any problems. I really don't
want to have to turn the NT server back on, but it looks like I'm going to
have to since I can't get VisionFS to work. That sucks
--
"Do or do not. There is no try."
- Yoda
Words of advice for the makers of NT.
Seth R Arnold
If you are in the US:
http://us1.samba.org/samba/samba.html
^
can be 1, or 2, or 3
elsewhere, www.samba.org.au -- it will give you a list of mirrors to choose
from.
The last version I downloaded and installed was 2.0.0. It said it could do
PDC, but without further testing, they didn't want to advertise it. They
are now up to version 2.0.5 or so, and maybe it has enough that they will
sell it as a feature. Or maybe you can try it out.
samba in my experience isn't hard to get running nor configure -- it just
doesn't come with the OS, like VisionFS does. (Its licensing is a lot easier
than VisionFS too... unlimited users, and if you pass compiled versions onto
others, you have to give them the chance to get the source code too. :)
not too shabby. :)
--
Seth Arnold | ICQ 3172483 | http://cswww.willamette.edu/~sarnold/
I prosecute unsolicited bulk emails, using the RealTime BlackHole
List. You should too. Ask me how, or visit http://maps.vix.com/rbl/
Kenneth McCormick
|
|
|Jim Richardson wrote:
|
|> Hey SCO Folks
|>
|> Boy it would be nice if some of you folks that know lots more than I
|> could give a short course on the relationships of Vision Logon Servers
|> and NT PDC servers. This will become increasingly important as we move
|> towards single logons.
|>
|> Sure hope you're out there.
|>
|
|I've posted twice asking for help on getting VisionFS to act as a logon
|server for my Win98 machines, but I haven't gotten any replies. I guess no
|one is doing it or maybe they aren't having any problems. I really don't
|want to have to turn the NT server back on, but it looks like I'm going to
|have to since I can't get VisionFS to work. That sucks
Suck or suck not, there is no try. I am taking your evil crosspost put of
my To:. Ahhhh, you see, I've solved one of your problems just like that :)
From the vfsintro.pdf file,
' Network logon services let you configure what happens when Windows users
log onto the network. When you enable network logon services, users’
Windows profiles (personal Windows settings, such as desktop icons and
program groups) are stored centrally, on the VisionFS server. A VisionFS
server can use one of its server names to provide network logon services to all
the Windows PCs in a particular workgroup.
Once you’ve configured the VisionFS server and users’ PCs correctly, then
whenever a user logs onto the network from a Windows PC, Windows
retrieves their profile and user environment information from the VisionFS
server. Retrieving profiles from a central location like this is called roaming
profiles. Roaming profiles let users log onto different Windows PCs, yet
always see the same, consistent Windows environment—the same icons on
their desktops, the same applications started, and the same drive letters
mapped.
SEE ALSO “Network logon services overview”, in the Help index. '
It worked for me, so I disabled it. Many users of vision would do well to
prove to themselves that every comp on their LAN can ping every other comp
by node name, by full domain name, and by IP addy. This simple test helps
evoke any errors in Netbios and/or tcp config.
What specific problems do you all have?
Do you have vfs encrypted passwords and vision file locking
(both defaults) working properly?
What strange dns do you all have lurking about?
Do you realize that you can keep the windows side of names and finding
computers rather simple with just a few text files?
Do you realize that vision and windows use netbios for almost all
name and logon duties?
Have you been sure to enable File and Printer Sharing for Microsoft Networks
etc, etc, etc ?
Have you read, at the vision web site, the help documents, faqs, and tips that
are nowhere to be found on the ta site? I admit that I've been using visionfs
for a few years, very happily, but I still have all the problems that
everyone else does with the initial configuration. I have to read all the
docs at the vision web site every time I install a new version, then deja
news, the crowbar vision profile to run and read all the docs that are
available through there. It's wierd, but truely amazing when it works.
You can do it.
Ken
Chad Lemmen
> From the vfsintro.pdf file,
>
> ' Network logon services let you configure what happens when Windows users
> log onto the network. When you enable network logon services, users’
> Windows profiles (personal Windows settings, such as desktop icons and
> program groups) are stored centrally, on the VisionFS server. A VisionFS
> server can use one of its server names to provide network logon services to all
> the Windows PCs in a particular workgroup.
> Once you’ve configured the VisionFS server and users’ PCs correctly, then
> whenever a user logs onto the network from a Windows PC, Windows
> retrieves their profile and user environment information from the VisionFS
> server. Retrieving profiles from a central location like this is called roaming
> profiles. Roaming profiles let users log onto different Windows PCs, yet
> always see the same, consistent Windows environment—the same icons on
> their desktops, the same applications started, and the same drive letters
> mapped.
> SEE ALSO “Network logon services overview”, in the Help index. '
>
> It worked for me, so I disabled it. Many users of vision would do well to
> prove to themselves that every comp on their LAN can ping every other comp
> by node name, by full domain name, and by IP addy. This simple test helps
> evoke any errors in Netbios and/or tcp config.
>
> What specific problems do you all have?
>
VisionFS is providing logon services for my Win98 clients. I can see all computers
in network neighborhood, but the only one I can access is the VisionFS server. If I
click on any other workstations windows tells me that there were no logon servers
available to service the request. Everything worked fine when using NT for the PDC
so I know that the workstations are configured correctly since the vision doc's say
that the Windows computers need to be configures just like they were logging into an
NT server. Also If I try to add users to the windows shares it tells me that I
can't view a list of users at this time.
>
> Do you have vfs encrypted passwords and vision file locking
> (both defaults) working properly?
>
Well I assume they are working properly. I have vfs passwords set and when users
log onto the windows workstations they are validated by visionfs, I think. Windows
lets them log on without any error appearing. How do I tell if vision file locking
is working?
>
> What strange dns do you all have lurking about?
>
I have a 3com 56K Lanmodem, which is the router that the network uses for internet
access. All the Win98 computers have its IP set as there gateway and DNS
>
> Do you realize that you can keep the windows side of names and finding
> computers rather simple with just a few text files?
>
Is there any advantage to using VisionFS as a WINS server?
>
> Do you realize that vision and windows use netbios for almost all
> name and logon duties?
>
> Have you been sure to enable File and Printer Sharing for Microsoft Networks
> etc, etc, etc ?
>
yes
>
> Have you read, at the vision web site, the help documents, faqs, and tips that
> are nowhere to be found on the ta site? I admit that I've been using visionfs
> for a few years, very happily, but I still have all the problems that
> everyone else does with the initial configuration. I have to read all the
> docs at the vision web site every time I install a new version, then deja
> news, the crowbar vision profile to run and read all the docs that are
> available through there. It's wierd, but truely amazing when it works.
> You can do it.
>
I've read all of this and set it up just like it says in the pdf file.
Seth R Arnold
columns. Thank god vim can reformat to x columns with the quoting and
everything else.
One problem that gets many samba users is the pesky MS encryption of the
password.
The samba docs provide two files, one named WinNT.txt and one Win95.txt.
I snipped. Please forgive me.
From the WinNT.txt file:
Run regedt32.exe and locate the hive key entry:
HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\Rdr\Parameters\
Add the following value:
EnablePlainTextPassword:REG_DWORD=1
And from the Win95.txt file:
regedit.exe:
/HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/VxD/VNETSUP
Make a new DWORD : EnablePlainTextPassword = 1
I imagine this will help immensly. (I just *know* I misspelled that.)
All this is moot if VisionFS can do the encryption though. <shrug>
Chad Lemmen
handle encryption so I didn't think that was the problem, but it was worth a try
anyway. For now I'm using the NT server again. Has Microsoft won?
Seth R Arnold wrote:
> One problem that gets many samba users is the pesky MS encryption of the
> password.
>
> The samba docs provide two files, one named WinNT.txt and one Win95.txt.
>
> I snipped. Please forgive me.
>
> From the WinNT.txt file:
> Run regedt32.exe and locate the hive key entry:
> HKEY_LOCAL_MACHINE\system\CurrentControlSet\Services\Rdr\Parameters\
>
> Add the following value:
> EnablePlainTextPassword:REG_DWORD=1
>
> And from the Win95.txt file:
> regedit.exe:
> /HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/VxD/VNETSUP
>
> Make a new DWORD : EnablePlainTextPassword = 1
>
> I imagine this will help immensly. (I just *know* I misspelled that.)
>
> All this is moot if VisionFS can do the encryption though. <shrug>
>
scpo...@my-deja.com
encrypted passwords.
In article <37B16F7C...@lemmen.com>,
Chad Lemmen <ch...@lemmen.com> wrote:
> Thanks for the suggestion, but I tried it and it didn't work. Vision
does
> handle encryption so I didn't think that was the problem, but it was
worth a try
> anyway. For now I'm using the NT server again. Has Microsoft won?
Chad Lemmen
Kenneth McCormick
You're problem will not be solved with a registry hack....
It is your windows config that is at issue, though...
Recentky, ch...@lemmen.com said...
[...]
|> What specific problems do you all have?
|>
|
|VisionFS is providing logon services for my Win98 clients. I can see all computers
|in network neighborhood, but the only one I can access is the VisionFS server. If I
|click on any other workstations windows tells me that there were no logon servers
|available to service the request. Everything worked fine when using NT for the PDC
|so I know that the workstations are configured correctly since the vision doc's say
|that the Windows computers need to be configures just like they were logging into an
|NT server. Also If I try to add users to the windows shares it tells me that I
|can't view a list of users at this time.
When a comp tells you that there are no logon servers available, it is telling
your that it can't find the unix box. Why? Look in Profile editor and be sure
that you have the workgroups and server names listed properly. Do you have
correct lmhosts files on all the systems? Do all users have identical usernames
and passwords on all computers? You can tell if your roaming profiles are working
by modifying your desktop and then logging out of a windows box, then logging
into a different windows box and seeing if the changes show up. Is wins turned
off?
|> Do you have vfs encrypted passwords and vision file locking
|> (both defaults) working properly?
|>
|
|Well I assume they are working properly. I have vfs passwords set and when users
|log onto the windows workstations they are validated by visionfs, I think. Windows
|lets them log on without any error appearing. How do I tell if vision file locking
|is working?
Figure out whether users are being validated by visionfs. Do you have them set up
to log into a widows nt domain? The one that visions calls itself? Did the roaming
profile test above prove that your profile is being stored on the vision server?
|> What strange dns do you all have lurking about?
|>
|
|I have a 3com 56K Lanmodem, which is the router that the network uses for internet
|access. All the Win98 computers have its IP set as there gateway and DNS|
That bugs me. Why? It's because I have yet to hear that you need dns at all.
The easiest setup involves using netbios over tcp/ip, so all you need is
/etc/hosts and /etc/lmhosts + \windows\hosts and \windows\lmhosts.
|> Do you realize that you can keep the windows side of names and finding
|> computers rather simple with just a few text files?
|
|Is there any advantage to using VisionFS as a WINS server?
What I meant here I repeated above. Netbios is very easy to setup. DNS is
more configurable, scalable, routable.
Visionfs is limited by netbios to workgroups on a single subnet.
Wins allows you to run netbios over multiple subnets. See the Visionfs
PDF doc's, p. 64 -- Wins doesn't use broadcasts by all computers to find
each other, so it also can decrease traffic.
|> Do you realize that vision and windows use netbios for almost all
|> name and logon duties?
|>
|> Have you been sure to enable File and Printer Sharing for Microsoft Networks
|> etc, etc, etc ?
|
|yes
Then why are you running dns? Whether you are running dns or not, would
you please describe any dns going on.
|> Have you read, at the vision web site, the help documents, faqs, and tips that
|> are nowhere to be found on the ta site? I admit that I've been using visionfs
|> for a few years, very happily, but I still have all the problems that
|> everyone else does with the initial configuration. I have to read all the
|> docs at the vision web site every time I install a new version, then deja
|> news, the crowbar vision profile to run and read all the docs that are
|> available through there. It's wierd, but truely amazing when it works.
|> You can do it.
|>
|
|I've read all of this and set it up just like it says in the pdf file.
That may be almost true, but it sounds like you have other things in the way.
Why not include your hosts and lmhosts files, and some IP addy descriptions.
Confirm that you have named your domain consistently.
Good work so far, it sounds like you are very close.
Ken
Toby Darling
Correct, VisionFS should only function as a logon server when in
VisionFS (encrypted) passwords.
> |VisionFS is providing logon services for my Win98 clients. I can see all computers
> |in network neighborhood, but the only one I can access is the VisionFS server. If I
> |click on any other workstations windows tells me that there were no logon servers
> |available to service the request. Everything worked fine when using NT for the PDC
> |so I know that the workstations are configured correctly since the vision doc's say
> |that the Windows computers need to be configures just like they were logging into an
> |NT server. Also If I try to add users to the windows shares it tells me that I
> |can't view a list of users at this time.
This is due to the Win98 machines being in user-level security, rather
than share-level security. In user-level security, the 98 machine has a
name set in Network->AccessControl, that it queries when someone
attempts to access a shared resource.
Unfortunately, VisionFS 3.0 does not support the user authentication
requests made by the Win98 machines, VisionFS is not a Domain
Controller. AFPS can provide the functionality you require.
Cheers
Toby
Chad Lemmen
Toby Darling wrote:
Well I guess this is my answer right here. Vision won't do what I want. It is working for
net logon services because the users profiles are stored on the Vision server, but I also
would like it to be a PDC, which I guess it doesn't do. I've already got an NT server so I
don't want to buy AFPS. I have no choice but to surrender to Microsoft then.
Jim Richardson
Chad Lemmen <ch...@lemmen.com> wrote:
>
>
> Toby Darling wrote:
>
It's been a while since I started this thread and we've wandered off the
track slightly.
Let me try a different way of asking the question and see if WE, as a
group, can come up with some ideas.
Vision 3x can do password verification through NT Domain controlers.
This seems to work just fine. NT seems to be a resonable solution to
host windows based applications and to provide those to users. But then
we get to the problems of maintaining account information on a many
different servers.
My question is..
How can we best integrate the two systems so that we can use the
advantages of each OS with a minimum amout of administrative overhead?
What I'd like is some roadmap from SCO on integrating management
functions (passwords, permissions, desktops, printers, file systems,
etc.).
--
Jim Richardson
I like NT because it constantly reminds me of my daughter.
"Honest Daddy, I wasn't doing anything and it just broke."
Mike Kenyon
> I also would like [VisionFS] to be a PDC, which I guess it doesn't do. I've > already got an NT server so I don't want to buy AFPS. I have no choice but to > surrender to Microsoft then.
Doesn't Samba do the PDC stuff, in beta-test at least? You might want to try
www.samba.org for an alternative to VisionFS or AFPS, and I think a
precompiled version for SCO is available as part of Skunkware from the SCO
website.
--
Mike Kenyon <mke...@promtek.com> Software Engineer for Promtek Ltd
Kenneth McCormick
|> You're problem will not be solved with a registry hack....
|
|Correct, VisionFS should only function as a logon server when in
|VisionFS (encrypted) passwords.
|
|> |VisionFS is providing logon services for my Win98 clients. I can see all computers
|> |in network neighborhood, but the only one I can access is the VisionFS server. If I
|> |click on any other workstations windows tells me that there were no logon servers
|> |available to service the request. Everything worked fine when using NT for the PDC
|> |so I know that the workstations are configured correctly since the vision doc's say
|> |that the Windows computers need to be configures just like they were logging into an
|> |NT server. Also If I try to add users to the windows shares it tells me that I
|> |can't view a list of users at this time.
|
|This is due to the Win98 machines being in user-level security, rather
|than share-level security. In user-level security, the 98 machine has a
|name set in Network->AccessControl, that it queries when someone
|attempts to access a shared resource.
|
|Unfortunately, VisionFS 3.0 does not support the user authentication
|requests made by the Win98 machines, VisionFS is not a Domain
|Controller. AFPS can provide the functionality you require.
|
|Toby
|
I guess that should have been obvious, but I thought the original poster
was using share level security, because it is the default settings on
that tab for Win98.
Kenneth
Kenneth McCormick
Recentky, ch...@lemmen.com said...
|>
|> Unfortunately, VisionFS 3.0 does not support the user authentication
|> requests made by the Win98 machines, VisionFS is not a Domain
|> Controller. AFPS can provide the functionality you require.
|>
|
|Well I guess this is my answer right here. Vision won't do what I want. It is working for
|net logon services because the users profiles are stored on the Vision server, but I also
|would like it to be a PDC, which I guess it doesn't do. I've already got an NT server so I
|don't want to buy AFPS. I have no choice but to surrender to Microsoft then.
Can you get by with Share level access control, which is a choice on Windows,
or could you use samba?
Ken
Chad Lemmen
Kenneth McCormick wrote:
I don't really care for share level access, user level is much better. I could give samba a
try. Maybe there is hope yet to defeat the MS empire.