Lost connection with published apps

[ChrisH123]

Last week we were bombarded with calls after the helpdesk received lots of calls saying "People cannot connect to Citrix". We checked and found that we could terminal serve into the Citrix boxes and also setup an ICA desktop connection to the Citrix servers. When connectiong to any Published App we got an error saying "Citrix Server could not be found"
A reboot fixed the problem but management wants to know if there is a way to prevent this as our plan is to move more apps to Citrix. This may stop our move to Citrix as no new user could attach to the Citrix farm.

 

[byteya]

Hmmm... could be a lot of things. Check the event log and see if there are any clues. Maybe a print driver issue.

I tell the boss, "The internal subbleflux was conflicting with the DMA channel interface. We got it corrected for now but future application interfaces may cause problems." That usually shuts them up. Quickly walk away. *J*

 

[dprello]

This is pretty vague, but we have a similar problem once every 2 months. Our problem is that the IMA service on the first Citrix server does not start up after being rebooted. No biggie, people just forget to check it after they reboot it. If anyone knows why that service doesn't start, let me know. We're running Win2k Server with Metaframe XPe. Compaq Proliant DL380.

 

[tekskin]

Are the people who are experiencing the problem on the same subnet? Have you applied the Hotfix from Citrix to deal with disconnected clients? Are you running DOS apps on your box? Do you have SQL & Oracle services on the same boxes? Ar eyour users who are experiencing this problem connecting across a router?

Please answer any or all the above, and we may be able to find a solution.

Kevin

 

[SirCam]

We recently changed to a fully switched network. I have found that when we cold boot the server, although we can attach to the server via terminal services, we can't connect to the published apps. Also, the server could not see any network drives. A warm boot fixed this, as did disabling/reenabling the network card. We tracked it down to portfast settings on the switch. We turned Portfast on, and all is now sweet.