Strange NFuse issue 1

[bob1000]

We've been using NFuse Classic with no issues for some time now. Suddenly some of the users can't log onto the portal. The web page just sits there doing nothing. Others can connect some of the time. Sometimes they can log on but the launch.ica file isn't downloaded. Anyone any ideas? I've tried installing on another server and the same problems occurs. What should we be looking for to troubleshoot this?

 

[Jayuk76]

Check to see in the nfuseadmin that the Citrix server is being refered to for log ons.


Can you log in via ANY account?

 

[bob1000]

Sometimes the connection times out- sometimes the applications launch correctly. It's arbitrary.

 

[ReBooted]

Restart the XML service on the Citrix servers you have setup on the MetaFrame servers page on your NFUSE servers.

 

[bob1000]

yes We've removed all but one server from the browse list in NFuseAdmin and have rebooted the server, and restarted iis. Still intermittent connectivity.

 

[TOMMYyT]

We had a similar problem. We had run out of disk space on the Nfuse server. Once we made some room the problem went way.

 

[crazyadmin]

Do the users get any errors?

We have had issues that were cured by reducing the temporary internet files setting on the client systems. Since windows sets the default really large the citrix client sometimes has trouble sorting through it in time to launch the app. Try deleting these timp files and reducing the size on a user that is having trouble and see if that helps.

Also if you are clicking on the app and nothing is happening then citrix is probably producing an error you cannot see. Try right clicking the app and choosing "save target as". Save this file to your desktop and then open it in notepad, it is a clear text file that usually will include the error.

 

[Jontmke]

We have this occasionally also. Restarting the Citrixxml service and the ima service on the server with the datastore usually does the trick. You might have to restart IIS on the nfuse box also.

JON

 

[bob1000]

Thanks for the tips. Have checked and done all the suggestions and it seems to be now working ok better now. Still I'd like to get to the bottom of the issue..

 

[bob1000]

And guess what it happening again. So we have changed to using the Program Neighborhood and distributing PN.ini file via the logon script. There is nothing wrong with the farm using this method of connecting.

Does anyone know how I can test the XML ports?

 

[chjinmind]

Try to check the connectivity between all servers using tcpview from sysinternals (

http://www.sysinternals.com/ntw2k/source/tcpview.shtml).

U see all local and remote ip's and the binary endpoints, very useful.

Also check the metaframe settings for the farm on what port the xml-service is running on. (preferrably all appservers use the same port as configured in nfuse...)

Also check the settings in nfuse of the list of metaframe servers, check that all servers are listed and that the DC is in the list.

Hope to have helped a bit

 

[Djones1212]

Have you been rebooting the Master Browser in the farm. The NFuse server keeps a log of the servers that have been master browswer, if you have been rebooting servers, this is groing with several failed entries. Reboot the server, and the log is rebuilt from scratch. Sorry but I do not know the name of the log. We started getting XML errors and server timeout errors, and troubleshot the problem to this log.

 

[DDILL]

Just to check, do you have one Citrix server set to be the master browser? You should set this if it is not already and point Nfuse to that server. Then do not use loadbalancing on Nfuse for the Citrix server. It should always look to the same Citrix server "master browser" for best performance.