[Info-vax] Pathworks problem

[Joe Bloggs]

On Fri, 24 Feb 2012 11:16:24 -0800 (PST), Dave <BaxterD at tessco.com> wrote:

>The Windows guy set up an external trust between WAVE and TESSCO,
>which should "permit"
>TESSCO to set up WAVE as a trusted domain.
...
>The Windows guy thinks we need a WINS entry to link TESSCO to the
>Remote Domain Controller.

Two thoughts.  neither of which may apply to your situation. 
but maybe they'll provoke some other insights.   particularly as it relates to the (network) browsing. 

if you have a linux box near the systems in question, 
sometimes 'smbclient' with elevated debug-mode (-d 10) can be illuminating.  or not.  


0. look at the WINS server entries, in the pathworks config menus. 
   sometimes WINS updates across different subnets is problematic. 

1. if your system has more than 1 interface (likely, these days)
   you might try to verify that the pathwork traffic is going out on the right nic(s)
   
 $ define/system/exec/nolog NETBIOS$DEVICE         EWx0:
 $ define/system/exec/nolog PWRK$KNBDAEMON_DEVICE  EWx0:
 $ define/system/exec/nolog PWRK$NETBEUI_DEVICE    EWx0:


2. push come to hard-shove, you could try to look at how the windows controllers are resolving
   the netbios names.  at wits end, you might mucking w/ lmhosts ([PWRK$ROOT.LANMAN]LMHOSTS.) 
   and, possibly the same, on the windows servers.  (eg punt around WINS) 

#
10.0.5.33  PWRK$LXX   #PRE #DOM:DOMAIN1
10.0.5.36  PWRK$LYY   #PRE #DOM:DOMAIN1
10.0.5.35  PWRK$LZZ   #PRE #DOM:DOMAIN2                    
#
10.0.5.1   DC1        #PRE #DOM:DOMAIN1
10.0.5.2   DC2        #PRE #DOM:DOMAIN2
#
#          1234567890123456
#          |              |
10.0.5.33 "DOMAIN1        \0x1b" #PRE #DOM:DOMAIN1
10.0.5.36 "DOMAIN2        \0x1b" #PRE #DOM:DOMAIN2
10.0.5.41 "ZZZZZZZZZZZZZZZ\0x1b" #PRE #DOM:ZZZZZZZZZZZZZZZ
#
# Copyright (c) 1993-1995 Microsoft Corp.
#
# This is a sample LMHOSTS file used by the Microsoft TCP/IP for Windows
# NT.
#
# This file contains the mappings of IP addresses to NT computernames
# (NetBIOS) names.  Each entry should be kept on an individual line.
# The IP address should be placed in the first column followed by the
# corresponding computername. The address and the comptername
# should be separated by at least one space or tab. The "#" character
# is generally used to denote the start of a comment (see the exceptions
# below).
#
# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
# files and offers the following extensions:
#
#      #PRE
#      #DOM:<domain>
#      #INCLUDE <filename>
#      #BEGIN_ALTERNATE
#      #END_ALTERNATE
#      \0xnn (non-printing character support)
#
# Following any entry in the file with the characters "#PRE" will cause
# the entry to be preloaded into the name cache. By default, entries are
# not preloaded, but are parsed only after dynamic name resolution fails.
#
# Following an entry with the "#DOM:<domain>" tag will associate the
# entry with the domain specified by <domain>. This affects how the
# browser and logon services behave in TCP/IP environments. To preload
# the host name associated with #DOM entry, it is necessary to also add a
# #PRE to the line. The <domain> is always preloaded although it will not
# be shown when the name cache is viewed.
#
# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
# software to seek the specified <filename> and parse it as if it were
# local. <filename> is generally a UNC-based name, allowing a
# centralized lmhosts file to be maintained on a server.
# It is ALWAYS necessary to provide a mapping for the IP address of the
# server prior to the #INCLUDE. This mapping must use the #PRE directive.
# In addtion the share "public" in the example below must be in the
# LanManServer list of "NullSessionShares" in order for client machines to
# be able to read the lmhosts file successfully. This key is under
# \machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
# in the registry. Simply add "public" to the list found there.
#
# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
# statements to be grouped together. Any single successful include
# will cause the group to succeed.
#
# Finally, non-printing characters can be embedded in mappings by
# first surrounding the NetBIOS name in quotations, then using the
# \0xnn notation to specify a hex value for a non-printing character.
#
# The following example illustrates all of these extensions:
#
# 102.54.94.97     rhino              #PRE #DOM:networking  #net group's DC
# 102.54.94.102    "appname  \0x14"                    #special app server
# 102.54.94.123    popular            #PRE             #source server
# 102.54.94.117    localsrv           #PRE             #needed for the include
#
# #BEGIN_ALTERNATE
# #INCLUDE \\localsrv\public\lmhosts
# #INCLUDE \\rhino\public\lmhosts
# #END_ALTERNATE
#
# In the above example, the "appname" server contains a special
# character in its name, the "popular" and "localsrv" server names are
# preloaded, and the "rhino" server name is specified so it can be used
# to later #INCLUDE a centrally maintained lmhosts file if the "localsrv"
# system is unavailable.
#
# Note that the whole file is parsed including comments on each lookup,
# so keeping the number of comments to a minimum will improve performance.
# Therefore it is not advisable to simply add lmhosts file entries onto the
# end of this file.