Title: | DECWINDOWS 26-JAN-89 to 29-NOV-90 |
Notice: | See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit |
Moderator: | STAR::VATNE |
Created: | Mon Oct 30 1989 |
Last Modified: | Mon Dec 31 1990 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 3726 |
Total number of notes: | 19516 |
I've got a problem at a customer's site regarding the connectivity of a non-DEcwindows machine and a VMS machine. Consider the following scenario: -------------- TCP/IP ------------------ DECnet ------------------ | HP (X11R3) |--------| VS2000 UWS 2.0 |--------| VS2000 VMS 5.1 | -------------- ------------------ ------------------ When a HP client (e.g. xclock) issues a connect request to the VMS machine using the Ultrix machine as a DECnet/Internet gateway all DECwindows related processes on the VMS side will crash. But if the request comes from the VMS machine everything works perfectly fine. Also, there's no problem between the Ultrix and HP machine in any directions. Obviously, there's a process running on the gateway which "maps" TCP/IP to DECnet and vice versa. Any ideas somebody? /ga
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
901.1 | Compliant, just doesn't listen well | STAR::BRANDENBERG | Si vis pacem para bellum | Thu Jun 08 1989 09:20 | 4 |
Any chance that that HP machine is big-endian? If so, you can forget about using the V1.0 VMS Server. | |||||
901.2 | ULTRA::WRAY | John Wray, Secure Systems Development | Thu Jun 08 1989 09:45 | 5 | |
The dying DECwindows processes ought to be QARed, whether or not the problem is due to a big-endian/little-endian problem. DECwindows ought to be robust enough to cope with (what it perceives as) garbage coming in from the net. | |||||
901.3 | DECWIN::FISHER | Burns Fisher 381-1466, ZKO3-4/W23 | Thu Jun 08 1989 12:50 | 5 | |
If the problem is big-endian, fixed in a future release. If not, I agree with .-1. Burns | |||||
901.4 | STAR::BRANDENBERG | Si vis pacem para bellum | Thu Jun 08 1989 13:10 | 6 | |
Like burns said... We already have a QAR (and I believe a fix) for withstanding babbling clients. Big-endian is believed to be fixed in a future release but is desperately in need of testing by those who can do it. |