We are in a mixed NOS environment, using a NT server just for
Vantage, and a Netware 4.11 server for everything else. We're also
using Novell's 'NDS for NT' to assist in our LAN user management
(not Vantage users, the LAN users).
Most of our workstations are running Win95 (we do have a couple of
WinNT4 workstations), and we're using both Novell's Client32 for
the NetWare side, and Microsoft's client for the NT side. The
workstations have both the TCP/IP and the IPX protocol installed.
(We also have a shared Internet connection, so the workstations
needed TCP/IP anyway).
Each workstation logs into the Novell server for authentication and
access to the LAN, and then 'attach' to the mapped drives on the
NT server. So far, this has worked well for us.
We're still on Vantage 3, but will be moving up to Vantage 4 at the
end of this month. I have Vantage 4 on yet another NT server, have
been testing it, and *so far* I don't have any problems (network
problems, that is <g>). After the migration to Vantage 4, I'll re-use
the existing Vantage 3 server for something else (possible setting it
up as a Terminal Server. We'll see).
Note: We haven't moved up to Netware 5.x (yet?), so I do not have
any experience in a 'pure' IP environment. Thanks for the heads up!
David Crook wrote:
Malcolm Spann
MIS
Malmberg Engineering
(925) 606-6500 x19
(925) 606-6505 FAX
Malcolm@...
===============================================
Vantage, and a Netware 4.11 server for everything else. We're also
using Novell's 'NDS for NT' to assist in our LAN user management
(not Vantage users, the LAN users).
Most of our workstations are running Win95 (we do have a couple of
WinNT4 workstations), and we're using both Novell's Client32 for
the NetWare side, and Microsoft's client for the NT side. The
workstations have both the TCP/IP and the IPX protocol installed.
(We also have a shared Internet connection, so the workstations
needed TCP/IP anyway).
Each workstation logs into the Novell server for authentication and
access to the LAN, and then 'attach' to the mapped drives on the
NT server. So far, this has worked well for us.
We're still on Vantage 3, but will be moving up to Vantage 4 at the
end of this month. I have Vantage 4 on yet another NT server, have
been testing it, and *so far* I don't have any problems (network
problems, that is <g>). After the migration to Vantage 4, I'll re-use
the existing Vantage 3 server for something else (possible setting it
up as a Terminal Server. We'll see).
Note: We haven't moved up to Netware 5.x (yet?), so I do not have
any experience in a 'pure' IP environment. Thanks for the heads up!
David Crook wrote:
>===============================================
> For those of you still running a "real" NOS (Meaning NetWare) here is
> one of those gotcha's you may encounter. We upgraded from version
> 4.11 to NetWare 5.1 this past weekend. After the change we started
> seeing errors when trying to "add" parts to part master (and a couple
> of others as well). We discovered that if your using the latest
> client from Novell and have it installed as either an IP only or both
> IP and IPX client. The problem seems to be that the for whatever
> reason, the Novell client doesn't recognize the UNC path of the OCX
> MessageLabel.OCX. Vantage registers this as
> "\\<server_name>\<share_name>\VANTAGE\OCX\MessageLabel.OCX". If you
> change the UNC path to this OCX (there may be others affected that we
> haven't tripped over yet) to the "mapped drive letter" path, it will
> work. In other words, if your mapped drive letter to the vantage share
> is "F", you can change the registry data to
> "F:\VANTAGE\OCX\MessageLabel.OCX". This can be edited manually or you
> can write a batch file to do it for you regsvr32 /U /S
> \\<server_name>\<share_name>\VANTAGE\OCX\MessageLabel.OCX regsvr32 /S
> F:\VANTAGE\OCX\MessageLabel.OCX
>
> I believe the above should be correct, but make sure you test it
> first. Also don't forget to modify it for the proper drive letter,
> server_name and share_name (share name should be epicor if you
> followed the instructions.)
>
> If anyone has seen this one and knows of a different workaround, I'd
> like to hear about it.
>
> Thanks to the Vantage Support Team for pointing me in the right
> direction to track this one down. (you know who you are)
>
> Good Luck and "long live NetWare",
> David
> JM Laboratories
>
Malcolm Spann
MIS
Malmberg Engineering
(925) 606-6500 x19
(925) 606-6505 FAX
Malcolm@...
===============================================