VisionFS problem with Windows 7
Steve M. Fabac, Jr.
access VisionFS shared on an SCO server?
I tried for a couple of hours but was not successful
using "visionfs password" authentication method.
I was able to access a VisionFS share by setting
"guest" access for read/write on a test share but
that defeats any attempt at enforcing user access security
(you need only supply a nonexistent user name to
get "guest" status).
The other problem with Windows 7 is that I was unable
to install TermLite, getting several warning messages and
the installation just hangs.
These are academic questions at this point as the user
plans to abandon Windows 7 and downgrade to WinXP.
--
Steve Fabac
S.M. Fabac & Associates
816/765-1670
Pat Welch
I haven't worked with Windows 7 yet (have with Vista - what a pile of
crap) but perhaps expecting VisionFS to work when development stopped
when 5.0.7 came out was a trifle optimistic.
I know people are also having problems with the older version of SAMBA
SCO provides.
Perhaps a simple NFS mount would work here, with the M$ Unix support
tools loaded?
--
----------------------------------------------------
Pat Welch, UBB Computer Services, a WCS Affiliate
SCO Authorized Partner
Microlite BackupEdge Certified Reseller
Unix/Linux/Windows/Hardware Sales/Support
(209) 745-1401 Cell: (209) 251-9120
E-mail: pat...@inreach.com
----------------------------------------------------
Steve M. Fabac, Jr.
I'd considered blowing away Vision and installing SAMBA but did not want
to make the change until I saw problem reports on SAMBA.
>
> Perhaps a simple NFS mount would work here, with the M$ Unix support
> tools loaded?
>
Ok.
One last thing, when I failed trying to install Termlit, I tried
just "run - telnet" and Windows 7 does not appear to have a native
telnet program. It did have ftp. Perhaps the Unix support tools
would have provided telnet?
Pat Welch
Hi, Steve.
Don't know - surprised there's no native telnet. Vista has it. The W7
version is not the 'for netbooks' basic version is it?
Did you check the optional Windows available components to see if it now
requires installing instead of being part of the base?
There's always PuTTY, or a commercial package like SCRT or Anzio or Tiny
Term.
I personally prefer and use SCRT for telnet and SSH/SFTP (www.vandyke.com).
Rick_Hoyle
>
> - Show quoted text -
I had a Client upgrade to Windows 7 recently. I was able to get him
the ability to access their VisionFS shares. In this circumstance,
their SCO box (running 5.0.7) is configured to pass authentication to
their Win2000 server. That configuration might make a difference.
I don’t know if all of these were required. But, these are the changes
we made on the Windows 7 system that allowed it to map UNIX shared
drives:
Run – gpedit.msc
Local Computer Policy -> Computer Configuration -> Windows Settings ->
Security Settings -> Local Policies -> Security Options
Domain member: Require strong (Windows 2000 or later) session
key: Disabled
(default was Enabled)
Microsoft network client: Send unencrypted password to third-party SMB
servers: Enabled
(default was Disabled)
Network security: LAN Manager Authentication
level: Send LM and NTLM
responses
(default was undefined)
Let me know if these help. I don't know if this would cause related
connectivity issues with other (i.e. Microsoft) servers. But, you can
always try them and put them back if required.
Steve M. Fabac, Jr.
> we made on the Windows 7 system that allowed it to map UNIX shared
> drives:
>
>
>
> Local Computer Policy -> Computer Configuration -> Windows Settings ->
> Security Settings -> Local Policies -> Security Options
>
> Domain member: Require strong (Windows 2000 or later) session
> key: Disabled
> (default was Enabled)
>
> Microsoft network client: Send unencrypted password to third-party SMB
> servers: Enabled
> (default was Disabled)
>
> Network security: LAN Manager Authentication
> level: Send LM and NTLM
> responses
> (default was undefined)
>
> Let me know if these help. I don't know if this would cause related
> connectivity issues with other (i.e. Microsoft) servers. But, you can
> always try them and put them back if required.
>
>
Rick,
Thanks for the above info. It is academic at this time as the client took
the Win7 pc back and replaced it with WinXP.
I did stumble into "Network security: LAN Manager Authentication level"
from a Google search and added the key using regedit but none of the
settings (0 - 4) fixed the problem. I also enabled plain text passwords
and that did not resolve the problem. I did not find the "Domain member:
Require strong (Windows 2000 or later) session" setting and would have
ignored it as the client does not have a domain controller, just the
UNIX box and 20 Windows XP systems.
In the past, I have configured VisionFS (at a different client's location)
to authenticate to the Windows Server 2003 system and that worked for
access from the Windows 2003 server terminal services sessions. To me
that configuration is strange on the surface as it results in users
logged into the Windows Server 2003 system clicking on VisionFS shares
and providing credentials to VisionFS which then asks the Windows 2003
server if the credentials are correct.
All the authentication problems with Windows and VisionFS seems to have
started when MS changed the user name from just "user" to "server\user"
at some point in the security updates for XP.
I'm sure that I'll get a chance to try this again when another client
purchases a Win7 pc without asking me before they make the purchase.