[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference unxa::cde

Title:CDE on Digital UNIXonment - CDE
Notice:CDE on Digital UNIX - for CDE on VMS, please see Note 1.3
Moderator:UNXA::SYSTEM
Created:Tue Nov 23 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:660
Total number of notes:2674

598.0. "dtlogin Broadcast query problem" by ALFAXP::RETTERER () Wed Feb 05 1997 14:59

Hi,

I have a customer who is seeing some unusual behavior with dtlogin and XDMCP
Broadcast Query.

He has 2 VXT terminals and one PC running eXceed, in addition to 4 Digital Unix
4.0b systems.

From the VXT's and the PC, if he does a XDMCP Broadcast Query to populate the 
listbox of available hosts, he only sees 3 of the four hosts in the list box.

If he changes to Direct query, he is able to connect to the fourth host with 
no problem.  If he does a indirect query, he gets connected to the fourth node
and in the login box he is able to see all four host systems.

His Xaccess file in /usr/dt/config is:


*                       # grant service to all remote displays

#

*	CHOOSER BROADCAST


If he continually click's on the UPDATE button on the PC, one out of 10-15
tries will display the fourth node.  

Is there a resource setting in dtlogin that he can change to have it reply 
to the XDMCP Broadcast Query more frequently?

The odd thing is that the forth node, is one network connection away from the 
Pc.

Thanks,

Rick Retterer
Workstation/Graphics Support
Alpharetta
T.RTitleUserPersonal
Name
DateLines
598.1UNXA::BEUTENo good deed ever goes unpunished...Thu Feb 06 1997 09:509
>>Is there a resource setting in dtlogin that he can change to have it reply 
>>to the XDMCP Broadcast Query more frequently?

	Not that I can find in the sources. You might suggest switching
	this one system from CDE to XDM temporarily to see if the 
	problem remains or goes away. If the problem remains, there's
	something environmental to debug. The broadcast queries use UDP
	datagrams which can be dropped, ignored, etc. 
598.2XDMCP BroadcastALFAXP::RETTERERThu Feb 06 1997 16:406
We will give it a try.  


Thanks,

Rick
598.3Issue resolvedALFAXP::RETTERERWed Feb 19 1997 10:1310
    Ha.  I found that the there was a FAT fingered entry in the Xaccess
    file.  We corrected it and now all is well.  The customer owned up that
    he was not seeing the node at all as opposed to seeing it
    intermittantly.
    
    Case Closed.
    
    Thanks for the help.
    
    Rick