- This topic is empty.
-
AuthorPosts
-
5. October 2011 at 4:23 #6865
Hi,
I have a Xenith running 1.7 beta code that i got from a rep, having issues though connecting to my Xendesktop environment.
I am manually entering in the broker url on the GUI of the device, pnliteserver=url
When i logon, it authenticates successfully and I can see my desktops assigned but when i go to launch, the session connects and when its about to fully opens, it gets disconnected right away, happens with all 3 desktops.
I tested this all internally on the network, there is no certificates or anything require that i know of and nothing peculiar about how its setup as well, well i dont know for sure but i tested with an apply Iphone and ipad and they connect and launch the desktops just fine.I am not able to do any troubleshooting as i dont have access to the DDC server or an FTP server to configure network captures etc.
But does anyone have ideas on what it could be, a hunch so that i can start looking that way. is it a license issue or is it a setting on DDC that disables thin clients being connected to the desktops??
pls help!
5. October 2011 at 19:54 #21144Please do a factory reset of the Xenith unit and try again.
CG
5. October 2011 at 21:36 #21146Hi Confgen,
Thanks, can i please ask what you might think is the issue here in your experience?
is it a license issue?
Factory reset is going to reset the licenses on the device?
Ive been told that with the newer codes, you dont require to use fixlicense=clean messages anymore although i couldnt test because i dont have a ftp server setup in the network.6. October 2011 at 7:01 #21148Everything you sid is correct.
Did it fix it for you?CG
9. October 2011 at 23:37 #21168Hi Confgen,
As mentioned, i dont have an FTP server setup in order to test the fixlicense command.
In your opinion, is this a tscal license issue with the imediate disconnection when launching the virtual desktop?
thnx
10. October 2011 at 9:12 #21173Yes, I guess so.
Did you do a factory reset already? This can be done from the client itself in the shutdown dialog.CG
26. October 2011 at 11:16 #21244hi,
Factory reset did not fix the issue.
As we have found, we were using the full URL of the web interface or pnagent server with the pnliteserver= command and this was causing the issue.
When we changed it to the IP address of the DDC host, we were able to connect just fine.
Strange!DNS is setup properly but you should be able to just connect using the WI url or pnagent url, it works with Xenapp using the pnagent service with the pnliteserver= command.
Any ideas?
-
AuthorPosts
- You must be logged in to reply to this topic.