Unsolved
This post is more than 5 years old
180 Posts
0
23315
EOP Xtream not working since updating to 7.2
To be honest I've not had much time to play around yet (on a train) but...
Since updating our vWorkspace setup from 7.1MR1 to 7.2 any connection made to a VDI VM with EOP Xtream enabled fails! RDS connections continue to work correctly.
Disabling Xtream from a client setting allows the connection.
Any ideas?
Not critical (yet) as the environment is pretty stall but we are set to go live in the main production setup next Monday!
I'll post some screen grabs and more data when I get to a "real" machine - typing on the iPad has it's limits!
Just thought I would post just incase I'm have a Friday moment and missing something silly.
Dan
prit1
72 Posts
0
March 4th, 2011 13:00
we had a similar problem ...some of our VDI's with pntools 7.2 had the "pndnasvc.exe" file missing during the installing process - this is the EOP file ( after removing pntools 7.1mr1 and installing pntools 7.2 )
prit
dbolton
180 Posts
0
March 4th, 2011 13:00
Best I can to on the ipad!
The VM is then locked by the user until a forceful action or a long timeout is initiated.
Dell-Matt-E
57 Posts
0
March 4th, 2011 13:00
What is the error message you are seeing?
Dell-Matt-E
57 Posts
0
March 4th, 2011 13:00
Also worth checking if you can use MSTSC to connect to one or the rogue VMs. Also what is set in the regsitry on one of these VMs under HKEY_LOCAL_MACHINE > System > CurrentControlSet > Control > TerminalServer > WinStations > RDP-Tcp = port number?
dbolton
180 Posts
0
March 4th, 2011 13:00
Oh - to add...
EOP Xtream is working fine with VDI desktops that are using the previous version on PNtools! so it's something in the current 7.2 PNtools - I'm guessing.
dbolton
180 Posts
0
March 7th, 2011 15:00
Hi Prit,
I've seen that before but this happens on a virgin machine with a fresh install of the new PNtools! - I'll check the pndnasvc.exe file tomorrow though!
dbolton
180 Posts
0
March 7th, 2011 18:00
I can connect via standard MSTSC and the port No. is 3390.
Any other ideas?
dbolton
180 Posts
0
March 7th, 2011 19:00
I can confirm that c:\Windows\SysWOW64\pndnasvc.exe exists.
DELL-Marc Z
30 Posts
0
March 7th, 2011 19:00
Some additional things to check:
1. Is the EOP Xtream service running?
2. Is it listening on port 3389? (run from command prompt: netstat -an and look for listeners on both ports 3389(EOPX) and 3390(RDP).
3. Can you telnet from the client to the VM on both 3389 and 3390?
dbolton
180 Posts
0
March 7th, 2011 21:00
Hi Marc,
1. Yes
2. Yes
3. yes both work..
Forgot to try netstat....
DELL-Marc Z
30 Posts
0
March 8th, 2011 21:00
Hi Daniel,
Very strange. Curious, when you say you can MSTSC to the machine, which port are you able to connect to, 3389, 3390 or both?
dbolton
180 Posts
0
March 11th, 2011 06:00
Hi Marc,
3389 works fine... 3390 does not.
I can confirm that all the Quest services are running on the VM (F/W disabled at this moment to).
DELL-Marc Z
30 Posts
0
March 11th, 2011 20:00
Hmmm, so if you can RDP to 3389 but not 3390, and you can telnet to 3390, that would make me think the RDP listener is configured to listen on 3389 (HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\ Port Number) And something else is listening on 3390 (perhaps EOPX)?
dbolton
180 Posts
0
March 15th, 2011 22:00
Hi Marc,
Well I must of been telling a lie becuase I can no longer telnet into 3390!
Registry value is 3389.
I've since provisioned a set of VM's with nothing but the base OS (win7) and PNtools on to keep things simple.
It all works with the previous verion of PNtools!