Problem eXcursion on XP

[Willem Grooters]

Nor really VMS related but probably the right forum....

VMS 7.3-2, TCPIP 5.4, XDM, RSH and REXEC enabled.
eXcursion (as from Pathworks 7.2 CD that came with 7.3-1) installed on a Win2K machine, there was no trouble connecting - nor as XServer nor running an X-Windows application.
Installed eXcursion on an XP machine, but NOT ANY WINDOW is shown. Nor as XWindows server, nor any application will end up in a usefull window.
I did try to get just ONE window (Control panel/Xwindow tab, checked 'single window'on leftside of the panel) but then it just started the backplane and that's it.
Log window shows server started and winsock 2.0 is running (two lines). That's it...After about 2 minutes it says ERROR: Too many retransmissions.

Does this look familiar to anyone?

Willem

[Antoniov.]

Willem,
I don't know eXcursion so I can only guess ..
Windows xp if fully different from win2k and other windows system; main differences are located on network layer becuase xp use crypted password.
This means every application needing password can't work in network: for example win xp can't work within old advanced server/Pathwork.
I guess on windows xp you need open Control Panel, Administration tools, security policy and enable xp to use uncripted password; or else you must enabel cripted passwork on server.

Antonio Vigliotti

[Kris Clippeleyr]

Willem,

Doesn't ring a bell.
What version of eXcursion are you using.
Here, we use "eXcursion V7.2.177" (so the log says) on XP machines and no problems whatsoever.
I know this doesn't help.

Sorry,

Kris

[Karl Rohwedder]

May be you are using WinXP-SP2 and the firewall is blocking something?

[Guillou_2]

Hi,

I 'm not sure that this could solve your problem, but i think there is a procedure to copy on the vms server (pcx_serv.com in cdrom:\xcursion\host\vms_v) and some operation to do on it after the transfert.

This procedure have to be copied in sys$system, renammed in pcx$server.com and the protection have to be (s:rwed,o:rwed,g:rwed,w:re)

Did you do it?

regards

Steph

[Lokesh_2]

Hi Willam,

I am using eXcursion on my XP machine and having no problem.

Add the IP address of your XP machine on host database of your VMS machine and then try again.

For example,

$ucx set host MY_NAME/ADDRESS=

HTH,
Thanks & regards,
Lokesh Jain

[Willem Grooters]

For what I erad from your answers: there should not be a problem.

Antonio:
If this were the problem the log would state taht authentication failed. It doesn't - si I _guess_ this is not the problem. I'll check accounting, though.
Kris:
7.2-177 (indeed that doesn't help...)
Karl:
I did get the pop-up telling me the problem, and that gave me the opprotunity to unblock -and I did. eXcursion X-server is one of the unblocked programs (just checked)
Guillou:
I know. This has been placed on the VMS box from the beginning - eXcursion works from a W2K and W98 machine without any problem.
Lokesh:
This might be a point, I'll check this. Not in HOST files ince it's a laptop that I want to keep as DHCP client (working on different networks, some of the _require_ DHCP...). When directly connected, it will be in DNS so that would also solve the problem.(I found it when connecting using a subnet)

One other thing: I remember there is a facility - on VMS - to restrict XServer connections by either hostname of IP-address. I remember to heva setup something like taht - but I fail to remember how. Anyone a QUICK idea (doesn't matter - can look it up but an easy find is ok ;-))

Willem

[Lokesh_2]

Hi Willem,

Check this:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=648140

HTH,
Best regards,
Lokesh

[Willem Grooters]

Lokesh,

Thanks. You have your >10 points now ;)

Willem

[Lokesh_2]

Hi Willem,

Thanks for the points. But I am more interested in knowing whether your problem is resolved or not. Please let me know if still you are facing the problem.

If problem still persist, then you can enable eXcursion logging from control panel and check what comes in your log file. This may give some hints.

HTH,
Thanks & regards,
Lokesh

[Willem Grooters]

Lokesh,
Not yet ;-(
Looking at the XDM logging, it turned out that XDM gets the router's address within it's own subnet (VMS box is 192.168.0.2 and the router is 192.168.0.31). It couldn't translate the name - so I added it in the hostfile. Still, it didn't work but I lost the messages.
Next, I found that what's behind this router (192.168.1.0) isn't seen - since the route did not exist - but my laptop in this net can access the VMS box without a problem except using XDM...
In XDM logging, I find lines:
%SYSTEM-S-NORMAL, normal successful completion
%NONAME-F-NOMSG, Message number 00000004

No intrusions, no messages in operator.log, and acc tells me on TCPID$XDM nothing more than that...

Any place to look for more in fo, just ask. Hopefully there is some time....

[Lokesh_2 · Accepted solution]

Hi Willem,

Is your PC and VMS machine on same LAN ? Check if your router is blocking this ? I have not tested XDM accross routers yet. XDM is port 177 and uses UDP.

Thanks & regards,
Lokesh

[Uwe Zessin]

Is the XP box running Service Pack 2 already? Any chance that the new firewall causes problems?

I would try to disable it at least on the LAN connection - it is somewhere on the properties. Sorry, can't tell you the exact names, because I use the German version of XP.

[Willem Grooters]

Lokesh,
It's not in the same LAN - that is: same IP network, as you could read in the addresses.
I don't know about the router, it's one of these black boxes that come with no documention and no management tools - just a VERY SIMPLE web-interface. Output IS said to come from this box (192.168.0.31) and so XDM will return it that way. Probably the router doesn't pass it on. I'll try to XDM on the same segment and see what happens there.

Volker,
Karl already mentioned that.

[Willem Grooters]

Solved, well, sort-of
When connecting this PC to the same LAN segment (= same network) as the server, there is no problem....So it wasn't XP after all - just a too simple router. Thanks Lokeh for your hint.