AREV through a Com server (AREV Specific)
At 10 FEB 1999 10:48:58PM Don Bakke wrote:
I would really appreciate it if anyone can tell me if the following configuration can work and what needs to be considered to get it to work:
Current Setup - AREV 3.12 running on Novell 4.12 using NLM 1.5
Considering adding an NT Server to act as a communications server for 10 remote/WAN connections. As I understand it, this NT Server will provide a client access to the Novell server for remote users (ala Citrix Winframe but using NT's version of it).
Thanks in advance for any help.
dbakke@srpcs.com
At 12 FEB 1999 01:20AM Larry Wilson - TARDIS Systems, Inc. wrote:
Don,
The problem is that everyone has to run the same AREV.EXE on the same logical path to get locking, and this is compounded by the setup you describe. Does AREV use Novell or byte-range (NT LM) locking? WinFrame won't (AFAIK) pass byte-range locking, nor (I think) Novell locking. The only way to effectively use AREV remotely is to use something like NetMeeting or PC Anywhere to run AREV locally on the network with the remote machine just 'watching' (keyboard active, of course). Of course, this means (unless you're running VPNs) having one machine per remote user - not a pretty picture.OTOH, if you have SQL Server running on the base server, and use use the SQL bond to link a remote server that's servicing serveral (or lots) of Windows machines to the main server's SQL database, that works fine. Harry and David (the Fruit of the Month club folks) out in Medford, OR, use that setup to service 500 workstations. They concentrate the data at a central Novell server then SQL it to their mainframe in real time. Works great.I guess, tho, that what you're wanting is to remotely WAN in a individual machines to a central copy of AREV - that is something I haven't seen done with native AREV. If you find a way, please let me know.Larry Wilson
tardis@earthlink.net
At 13 FEB 1999 03:52AM Jonathan Bird wrote:
Don,
I've done what you describe, using Citrix Winframe 1.6. over a TCPIP WAN. You have to have the NLM in place to achieve locking, and like any normal NT session, the NLM TSR has to be loaded via the AUTOEXEC.NT or an equivalent. However, performance was not good. When an Arev session on the Winframe was doing anything (just going into a window for example, the CPU utilisation on the Winframe machine when to 100%. However, when we replaced the Netware server with an NT server and intsalled the NT service, the Winframe CPU usage, and consequently workstation performance, was much better. Funny, eh? Must have been something with the NLM and Winframe. Maybe a deep and meaningful time with a Winframe tuning expert would have helped…..
J
At 13 FEB 1999 09:44AM Don Bakke wrote:
Larry/Jonathan,
Thank you both for responding. At least I now know what pitfalls to look out for (i.e. locking and performance).
Hopefully Terminal Server will not have the same utilization problems that Winframe does…but I suppose the only way to find out is to test it.
I will post back once we attempt this and let you know how it went.
dbakke@srpcs.com
At 13 FEB 1999 09:45PM Jonathan Bird wrote:
]]I will post back once we attempt this and let you know how it went.«
I'd be keen to know how you go,
J
At 24 FEB 1999 09:01PM akaplan@sprezzatura.com - [url=http://www.sprezzatura.com]Sprezzatura, Inc.[/url] wrote:
It should work, but slightly slow. You'll have to use either the yield function or Citrix's YIELDDOS TSR (written for ARev apps). You'll also need the NLM. There's a few people running it. Try doing a Citrix search here on the board for other clues. A run through Citrix's site is very helpfull for these sorts of things.
akaplan@sprezzatura.com
