Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cisco Routers and Citrix Metaframe

Status
Not open for further replies.

Cristhian

ISP
Sep 27, 2000
25
PE
Hi all,
i have a big problem with Metaframe 1.8 for NT Terminal 4.0 and Windows 2000, the wan is :

citrix client --> router cisco 1600 --> isdn --> router cisco 2600 --> Pix Firewall --> Citrix Metaframe Server

The conexion in the client and the server is very slow and it lost frecuently.
i think that problem is in the NAT in the two routers because the client remote (PPP conections) i not problem in the conexion.

Any Idea?

Thanks

Crishtian
 
Its possible that the link is too slow for the timing that is needed with metaframe. Are you using TCP or RDP? Which ports have you opened on the PIX box? I know that MS Proxy has fits with Metaframe unless you open certain ports and there is a third party socket manager that help alot with the MS product.

To really get the details of what is *wrong*, you would use a sniffer and see what the timing is and who is really losing what.

Mike S
 
Hi friend,
i think that problem is in the ISDN because not is only the Citrix problem, the mail and the ftp inside is slow and its close frecuently.
The telnet in the client a port 1494 request good, i don't idea what happening

About the sniffer as you recommend to me that it uses?

Sorry friend, my english is very bad :)

 
Your english is fine enough for me to understand so not to worrry about it.

You are correct, if other applications are slow then it's not just a Citrix problem. If it's closing the ISDN port, take a look at your timers. You can force the router to hold the ISDN link for a period of time after the last "interesting " data packet has gone by.

router#show dialer idle-timeout

You may need to increase that. You may need to work with the access list of just what interesting traffic you startup the ISDN link on.. is it any traffic or just certain types?

If this is a single B channel at 64 K, it's gonna to be slow no matter what. 2 Bs at 128K work very well.

Look at this link

Mike S
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top