Accessing NAV 5.0 slow through wide-area network/leased-line

aquawater

Hi All...
We are using NAV through out our office branches.. but we notice that in branch office opening any form or posting will have significant delay, while in HQ there is no delay at all.

We were suggested to use remote desktop for client connection. It is faster but we have more issues on printing / printer. The server is windows server 2003 (64 bit)..

My question is how can we speed up NAV client when we are using leased line.
Any advice?

Few things to note:
+ NAV 5.0 SP1
+ Database on SQL Server 2008
+ Leased line connection at 10Mbps upload and download
+ Notice slow connection only if we use NAV Client and not from Remote desktop connection

David_Singleton

If remote desktop is a problem then try Citrix instead. It is not possible to use Navision over a WAN.

aquawater

Citrix ? Which product are you refering to? XenServer ?

It is not possible to use Navision over a WAN.

Would you mind to elaborate more on this ?
Why is it not possible ?
The vendor who sells it to us said NAV is a client-server application.
Why couldn't it handle WAN ??

garak

u can handle it on WAN. But the perfomance is very poor.
If, lets say, the Server with the database in in City A and the users are in City B or in a other area on city A, it's better to use a Terminal Service like MS TerminalService or Citrix.

Citrix has changed his product portfolio. The old Citrix progamm neighborhood is expired.
The new version is the XenApp. But this is not released for WinServer 2008R2.

defiant701

Hi aquawater,

you said that you have a W2K8 R2 server so why not using the remote apps technology? It's (nearly) the same protocol from Citrix via RDP connection. We have all of our subs connected like that and the speed is absolutly perfect. \:D/

BR
defiant701

aquawater

The server is windows server 2003 (64 bit)..

we are using SQL server 2008 in windows server 2003, 64 bit.
using remote desktop aka terminal services is definitely a faster solution for NAV.
but our only issues are printing..remote desktop printing seems not stable at all.

defiant701

aquawater wrote:

The server is windows server 2003 (64 bit)..

Ups didn't read that...

well printing issues on RDP is a well known problem. Tech.net is full of answers... (e.g. WHQL driver, no local printers, no trendy & unsupported fonts from your marketing...... etc.). Otherwise make sure that a skript will restart the spooler every 10 minutes.

BR
defiant701

aquawater

Thanks for the feedback, guys..
conclusion:
+ NAV is not a decent client-server application for WAN even with 10Mbps connections
+ RDP printing is a known issue
+ Consultant/Vendor NEVER mention about system weakness =D>

David_Singleton

aquawater wrote:

Thanks for the feedback, guys..
conclusion:
+ NAV is not a decent client-server application for WAN even with 10Mbps connections
+ RDP printing is a known issue
+ Consultant/Vendor NEVER mention about system weakness =D>

Did you specifically ask the vendor these questions? I agree that they should have brought the issues up and told you, but on the other side, don;t forget due diligence.

As to Client Server, Are you aware what Client Server means? :whistle:

idiot

aquawater wrote:

Thanks for the feedback, guys..
conclusion:
+ NAV is not a decent client-server application for WAN even with 10Mbps connections
+ RDP printing is a known issue
+ Consultant/Vendor NEVER mention about system weakness =D>

If the consultant mentioned system weak, would you still buy? \:D/

wing2299

RemoteApp printing has been significantly improved which eliminate the need to install printer driver on TS. it's well worth upgrade or add a Windows 2008 server to your 2003 server.