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

Conference ranger::pwosf

Title:PATHWORKS for OSF/1
Notice:see also NOTED::PWDOSWINV5 (PW client) & TURRIS::DIGITAL_UNIX
Moderator:CPEEDY::LONG
Created:Thu Apr 22 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1874
Total number of notes:6870

1731.0. "Does PW5.0f support WAN logon via WINS proxy agents?" by WOTVAX::SHARKEYA (LoginN - even makes the coffee@) Mon Feb 03 1997 13:03

    Using PW v 5.0f.
    
    We are trying to get WAN logging on working. According to an MS
    article, if we have a WINS primary around, we can use the client (W95)
    to talk to the WINS server who will then forward our netlogon message
    to the OSF box (in another subnet). The OSF box should then ask a local
    WINS proxy agent for the address of the '95 PC and then validate from
    that.
    
    However, an IRIS trace shows that the WINS server does indeed pass on
    the netlogon SMB to the OSF server. But the OSF server never does
    anything with it.
    
    So, did you write the code in this version to broadcase the client name
    on the subnet for the proxy agent to pick up ? If so, any ideas what we
    are doing wrong ? 
    
    If not, does it work in PW6 for Unix ?
    
    Thanks for any advice.
    
    Alan
T.RTitleUserPersonal
Name		DateLines
1731.1All from memory...VMSNET::S_VORESmile - Mickey's Watching!Mon Feb 03 1997 16:328
I would not expect it to work with v5 and am pretty sure it dosn't work on the
v5 VMS server either -- the VMS server (for which we did some testing way back
when) appears to ONLY be listening for a broadcast -- which a WINS (or LMHOSTS
with the #DOM: entry) client isn't sending - it's sending a directed datagram.
 
With v6 being "NT", I would certainly hope that it works there.

-Steven
1731.2it works with 6.1WOTVAX::SHARKEYALoginN - even makes the coffee@Tue Feb 04 1997 04:514
    Yes, it DOES work with PW6.1 - now testing with 5.0g (ever hopeful)
    
    Alan
1731.3CPEEDY::HORGANCraicailte indiadh damhsaTue Feb 04 1997 10:5615
5.0G does have lmhosts support.  

If your using 6.1 ECO1 the servers have to be configured as either a 
WINS client or with the lmhosts file.  If your using the lmhosts file, 
please check the release notes and/or the System Guide to make sure it 
is configured correctly.  You need a special line that identifies the PDC.

	Example:

	125.100.200.13 	LOBSTER	    #DOM:LOBSTER.DOM
-->	125.100.200.12	"LOBSTER.DOM  \0X1b"


Julia
1731.4but thats not all !WOTVAX::SHARKEYALoginN - even makes the coffee@Tue Feb 04 1997 11:0210
    Yes, but the issue seems to be that the 5.0 server is not listening for
    a directed netlogon inquiry, only for a BROADCAST netlogon inquiry.
    
    Even if it did listen, it would mean putting every client into the
    LMHOSTS file - not a pleasant task !
    
    thanks anyway
    
    Alan
1731.5UPDP port 137/138EVTAI1::CASTELLOUNIX and PCI SupportTue Feb 04 1997 14:0222
.3 
> 5.0G does have lmhosts support.

I think NO. I suppose that it's a typo error.
V6.1 does.

.4
>Yes, but the issue seems to be that the 5.0 server is not listening for
>a directed netlogon inquiry, only for a BROADCAST netlogon inquiry.

True according lanman 2 specs.


With V5.0G the server responds by sending a directed DATAGRAM to the workstation
\mailslot\temp\netlogon and send its name to the workstation.
The only way as far as know is to let pass traffic throught router 
on port UDP 137/138.


WINS proxy is much more useful for net use once you have been validated!!. :-(

Jean-Pierre