AS/400's Client Access and Novell IP/IPX Gateway

How can we eliminate a slow, sluggish connection when we run IBM's client access across a site with Novell's IP/IPX Gateway installed?
Background: We have two campuses, 80 miles apart, connected via a T-1 frame relay link. On the main campus we run client access on IP across our network with no noticeable slowdown in service or speed. This site also houses the college's ASW400. At the remote campus, whenever we install client access and try to access the AS400 via the T-1, the station comes to a crawl. It is so slow that we have had to remove the software. The only difference between the campuses is the fact that Novell IP/IPX gateway is being used on the remote campus. Has anyone had problems with a similar configuration? What can we check or reconfigure to improve service?
We have installed the latest version of client access and on the remote campus we have installed novell's service pack 4 on the server running the gateway.
mcammackAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

cshelmerdineCommented:
I suspect your problem is to do with the WAN link rather that the gateway. (Assuming a 10MB LAN, the WAN is 1/10th the speed)

Hope this helps - talk to the WAN people.
0
paulnicCommented:
1.  Does the client access program load across the T1, or from a server or workstation on the remote campus?

2.  Assuming your link supports IP, test the speed from a remote workstation (on the WAN side of the gateway) configured for IP only.  This will rule out the IPX/IP gateway as your bottleneck.

3.  Find out what the "CIR" - committed information rate - is on the frame relay circuit.  You may reach the frame relay "cloud" over T1, but be paying for a guaranteed data rate of 256 kbits/sec or less.

4.  Find out how much data is transferred by the app that seems slow using client access. Are you doing 10Mb files or 2Kb screenfuls when it slows down?  Get a rough idea from IP statistics on the workstation at the main campus.  For more accuracy, find a freeware packet analyzer on the Net to  count the traffic in bytes between IP addresses.  

If it's slow just moving a screenful or two at a time, there's a configuration problem.  If you're moving big stuff, and it takes roughly as long as a similar server-to-server file copy across the link, you need a faster WAN or a redesigned app with a smaller bandwith appetite.  

5.  You may also want to see how busy the link is with other traffic at the time(s) you test.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.