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

Conference utrop1::decadvantage_support

Title:DECadvantage Support
Moderator:UTROP1::beersmh.uto.dec.com::beersma
Created:Fri Aug 28 1992
Last Modified:Fri May 23 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:375
Total number of notes:1446

371.0. "Problems with WIN/TCP and LAN Workplace" by ATZIS2::TEZAREK_H (Harald TEZAREK @AUI) Thu Feb 06 1997 18:53

    Hi,
    
    one of our customers has a configuration with an applicationDEC 433
    running SCO,WIN/TCP and SMB-Server and about 30 PCs running TCP for DOS
    and SMB-Server, too.
    The application they use is an old MEGADOC-Application using Netbios
    and SMB-Requests for communication to the server.
    
    Unfortunately the customer has to change the Wollongong TCP/IP on PC
    against LAN Workplace.
    I have installed now one of the PCs with both TCP for DOS and LWP
    (using the 2 stacks alternating).
    
    If I use LWP TCP/IP is OK; so I can use ping, ftp and telnet, but
    netbios does not work.
    
    Looking into nbmon-logfile I see that a netbios call is made with
    netbios name "SMWEISS" - the name of the server - but the call is not
    answered.The same is for the following calls for NB-names "ULSMWEISS"
    and "TYSMWEISS".
    
    On the server I can see that an udp-session exists with ip-address of
    this PC and service netbios.
    On the PC I can see with LWPCON that the PC already knows the
    MAC-address of the server.
    It seems that the name_query request ist anwered by the server; the ARP
    packet is sent with the MAC address of the PC and answered with the ARP
    repsonse with the server's MAC-address, but the TCP connection is not
    build.
    The same works without any problem if I change the protocol to TCP for
    DOS and use the same TCP/IP configuration.
    
    PC and server are in the same subnet.
    
    NET.CFG is:
    
    Protocol TCPIP
    
    	ip_address 	193.187.131.61
        ip_router	193.187.131.30
    	nb_sessions	12
    	nb_commans	16
    	nb_adapter	0
    	nb_domain	none
    
    (I have tested without nb_domain, too).
    
    I'm running out of ideas now. The onl thing that I can try is to
    upgrade WIN/TCP on the server (they still use 6.0.1b), but I don't
    think that that will change anything.
    
    Maybe someone has an idea what I can still try.
    An help is appreciated.
    
    Many thanks and best regards
    
    Harald
     
T.RTitleUserPersonal
Name
DateLines
371.1Lan adapter numberUTROP1::utobeersma1.uto.dec.com::BEERSMA_HThu Feb 20 1997 17:565
Hi
I think theproblem is in the dual protocol stack. Lanwork place uses in your configuration 
nb_num=0. Probably when you change this to one and let TCP for DOS use 0 then it will work
Hans Beersma