HELP! Upgrade Novell 3.11 to Novell 4.11 (AREV Specific)
At 30 DEC 1998 05:13:36PM Egbert Poell wrote:
HELP HELP HELP!!!!!!!!!!!!!!!!!!
We are experiencing a strange problem at a clients site :
- Old situation :
14 Win95 (Pentium 200/233) workstations in the LAN
1 DOS dedicated index server
1 DOS workstation with barcode reader
1 Win95 workstation remote (other building)
1 DOS 5.0 workstation remote (other building)
Novell 3.11 server (Pentium 90)
TOKEN RING 4 Mb topology
All running smoothly
- New situation
14 Windows NT 4.0 workstations (Pentium 200/233)
1 DOS dedicated index server
1 DOS workstation with barcode reader
Novell 4.11 server (Pentium II …., RAID 5) with NLM 1.5
ONLY the 2 remote workstations (1 DOS\1 WIN95 are hanging at the logon screen when starting AREV.
The rest works fine but is slower than Win95
The versions of the DOS client software is checked.
When we unload the NLM we can get into the AREV app.
We tried everything with the parameters of the NLM server and
clients.
They are using now :
LHIPXTSR /C:120 /R:32 /S:1
LOAD LH /F:500 /H:6000 /S:16
LOAD LHIPXSER /M:10 /N:CCSCOA01 /P:4054
Could on e of the issues be :
- different Novell owner
- VLM 1.20B vs VLM 1.20
- Transactional flag
PLEASE HELP!
TIA
Egbert Poell
Mecomp Automatisering
Mecomp@xs4all.nl
At 31 DEC 1998 06:56AM Steve Smith wrote:
Egbert - what version of the Novell Intranetware client are you running?
Sounds like a locking-related issue. As the LH NLM uses the IPX protocol ensure this is included in your workstation configuration
in addition to TCPIP if you use it too. How many dots do you get at the point of hanging on startup on the 2 remote PCs?
Flag AREV.EXE read-only sharable and all other LK & OV files SHAREABLE READ-WRITE. Flag transaction tracking off.
Win NT is somewhat slower than Win 95.
Steve
At 31 DEC 1998 07:09AM Egbert Poell wrote:
Steve,
Thanks for your reaction.
The Client32 version they are using is 4.11, I believe.
All .EXE files are flagged ROSh and all others RWSh.
Transaction flagging is looked after today or so.
The startup shows only one dot after the text string.
Remember, we have only problems with the REMOTE DOS station, the local ones are running fine and so are the WIN NT ones.
If you need more please let me know.
Best regards,
Egbert Poell
Mecomp Automatisering vof
Mecomp@xs4all.nl
At 31 DEC 1998 08:32AM akaplan@sprezzatura.com - [url=http://www.sprezzatura.com]Sprezzatura, Inc.[/url] wrote:
The one dot is where it sets the network lock, so there something happening during the configuration. I seem to recall there being problems with the a and b revisions of the 1.20 VLM. Can't remember what happened with the 1.21 and 1.22, if they even made it that far.
I'd still go for loading the 1.20 standard on the remotes and see of that happens. It also could be a SAP thing as well.
akaplan@sprezzatura.com
At 31 DEC 1998 04:32PM Steve Smith wrote:
The Novell VLM.exe was OK in 1.20, 1.20B and 1.21. The 1.02 (one point zero two) that shipped with Novell 3.12 was bad.
How are these guys connecting remotely?
Steve
At 01 JAN 1999 05:50AM Egbert Poell wrote:
The remote DOS station is using the same client software as it did in the old 3.11 situation so :
LSL
"networkcard driver"
LANSUP
IPXODI
VLM
The local index server is using the same software (only VLM 1.20 instead of VLM 1.20B) and the same NET.CFG and this one works fine.
We checked the SAP thing in the recent past before Aaron came here and it was OK.
Any more suggestions?
Best regards
Egbert Poell