Have anybody tried to setup Navision Attain terminal server? Any suggestions on software, hardware etc.
Do you mean a Navision Attain server which can host terminal sessions? If so, as far as I’m aware, this is just a Windows 2000 server (ideally), with Terminal Server option ticked to the Windows setup. Then just install Navision Attain and set a few access and security options and away you go! It can be done for an NT server except the terminal server addition is not part of the NT server setup (has to be purchased / downloaded separately). Hope this helps. [:)]
I mean I don’t need install Attain Client on workstation but run Client from terminal server. This way I need to transfer minimal amount of data between workstation and server (only request and result).
Sorry I might not be understanding this correctly, but do you mean not installing Navision Attain Client on the workstation, just running it through terminal services off the server?
Yes, I do. I know something similar is running in other NSC but I don’t know how to explain techology and how to achieve it.
Well this is what I meant in the first post. Basically you have a server (Windows 2000 server with terminal services) and Navision Attain server installed. You also need the Navision Attain client installed on the server with permissions set so users that log on to the terminal server, can run the application. As for the actually setting up of terminal server on a box, I would suggest consulting MSDN or TechNet (probably MSDN). I’ll have a quick look and let you know if I find anything. [;)] Good luck.
Thank you, I’m looking forward to hear more details about this from you and everybody else [:)]
We have a terminal services server in use, so all the clients connect to terminal services server on which the Navision Attain client is launched. It works very well. The reason we did this: the network cabling only allows 10 MBit, and that is too slow for Navision[:(] The terminal services should be on a dedicated server, it should have a lot of CPU power and enough memory to allow the number of concurrent connects. Any more infos needed?
quote:
Originally posted by mschenk It works very well. The reason we did this: the network cabling only allows 10 MBit, and that is too slow for Navision[:(] The terminal services should be on a dedicated server, it should have a lot of CPU power and enough memory to allow the number of concurrent connects.
That’s exactly what I need. Can you please tell what software is needed for this (on server and workstation). And maybe write a link to some RTFM about this. And one more … workstation will need to access it’s COM port and exchange some data to/from Navision. Will it be possible?
Hi,Arthur it is very easy,please do by following step. 1.install navsion client in windows2000 server. 2.install terminal server in windows2000 server. 3.install terminal client in windows 2000/windows98. 4.setup domain user remote access permission in Domain windows2000 server. 5.setup terminal client (detail see about terminal help) 6.login terminal server from desktop workstation 7.you will see navsion icon in windows2000 server from you computer,and run it
What about terminal server software? I heard there are many softwares but only few of them supports COM port access on workstation. Any comments?
Why do you use COM port instead of telephone line for remote user? if you must use COM port,I have any experience about it.
Connection to Terminal server will be made by low speed network … that’s not a problem. Problem is I need to use COM port for Fiscal Printer. Every workstation has it’s Fiscal Printer that have to print data from Navision. I heard that’s problem cause most Terminal server softwares doesn’t support that.
With Citrix ICA you will be able to map COM ports on workstations. Our customer use it for communication between Navision and barcode terminals. But with serial printers there can be any problem, I have no experience with it. Martin