Conference bulova::decw_jan-89_to_nov-90

2779.0. "Server on another area when client is a router." by TMIS01::DORON (Doing my BEST !!!) Thu May 17 1990 08:33

  Hi,

 We are having here a problem that I did not see reported pn this notes file
before. Since our Decnet area (51) allocated all it's node numbers, we got to
start working on an 'hidden' area (63). Lately, we have cluster configured a
satellite (VS2000) to a MI cluster runnibg VMS5.3 . Decnet seemed to operate
just fine (regual operstion such "set host", "copy", "mail", "phone"...) both
ways, between this particular satellite and other nodes on the network. (All
cluster nodes are on area 51 except the satellite that has been configured on
area 63). We have expirienced problems running DECwindows applications (such as
Notes, DECW$MAIL, Decwindows terminal, Decburger...) that requires input from
the server node, when the client is running on a Decnet ROUTING node on other
area then the server node. (E.G.: Rounting node on area 51 when the DECwindows
server is on the VS2000 in area 63). What we saw (or actually did not see) is no
window was opend on the server. I have checked the server node for logical links
and saw that there was a X$X0 logical link between the client node and the
server. When I have tried running the application on a non DECnet routing node
on area 51, every thing worked smoothly. I did try it from other satellites
configured on the same cluster as the VS200 satellites or from any other non
DECnet routing nodes (in area 51).

 We need to know if there is any known problem before we go on and configure
more DECwindows work stations on the 'hidden' area.

 
	Urgent help is needed and will be appreciated,
					*-Doron Angel-*,
					Israel S.S.D.U.