clients, and let me tell you it hogs bandwidth. If you can, rather go for a
terminal server or citrix solution. We have just started testinbg and
rolling out terminal server and the difference is incredible. Of course it
also comes down to cost - if in your situation bandwidth is cheaper than
hardware I suppose you can go overkill on the pipe ;)
In answer to bandwidth needs, the calculation we were given for bandwidth
estimation was:
bandwidth = max((ASU x 6.4), 28.6kbps)
where 1 ASU = 10 sales orders per hour (if I remember correctly- please
correct me if I'm wrong ;))
So if you're running 10 ASU you need 10x6.4 = 64kbps.
Keep in mind this is just Axapta's requirements (and from my experience I
would say this is a really underspecified).
Regards,
Matt Benic
.Net/Axapta Analyst Developer
UTi Sun Couriers Division
Support the Xbox 360 in SA campaign
<http://forums.xbox.com/ShowPost.aspx?PostID=12592431>
-----Original Message-----
From: [email protected]
[mailto:[EMAIL PROTECTED] Behalf Of ajioajioajio
Sent: 04 August 2005 03:26 PM
To: [email protected]
Subject: [development-axapta] Remote connection to Axapta
Hi.
I'm having problems conecting remote clients of one office, to the
Axapta main servers in an other office. ¿how much Bandwidth or whitch
type of connection do i need? I know than a typical client can't be
connected trough this types of connection, but ¿could it be enough for
an AOS client?
I've been searching for some info on remote conection to an axapta
application, but haven't found any.
thanks.
Regards
Camilo Virguez
Yahoo! Groups Links
SPONSORED LINKS
| Computer part | Programming languages | Microsoft axapta |
| Support exchange |
YAHOO! GROUPS LINKS
- Visit your group "development-axapta" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
