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

Conference utrop1::linkworks_v3

Title:LinkWorks V3.0 Notes Conference
Notice:LNX_APO = APO issues, LINKWORKS_V3 = V3.0 issues
Moderator:tacklr.apd.dec.com::TACK_Lm::TACK_L
Created:Tue Jun 28 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2269
Total number of notes:8338

2266.0. "Dissimilar TCP/IP addresses prob" by OASS::BURNAMAN_B (And now, live, from Atlanta . . . ) Wed Jun 04 1997 00:10

    Greetings:
    
    I have a customer that is seeing a problem when the TCP/ip addresses
    between client and server are dissimilar.  Here is what he wrote:
    
    We are trying to avoid giving people registered IP addresses and go
    with the non iternet 10.x.x.x addresses.
    
    When we put this address on a Win 95 client, we get about a minute
    before the Linkworks Server answers, and obviously another minute
    after we enter our user id and password.  Telnet, Ping come back
    immediately, no problems at all.  The network sniffer shows that
    there is some activity, then everything is on hold for about 53 seconds 
    until the Linkworks Server sends a message, then everithing goes quick. 
    When we put in one of our regular addresses, everything is fine and quick.
    
    We are running VMS 6.2/Oracle 7 Linkworks 3.08 Server and a mix of 3.08 
    and 3.07 Clients with both TCP/IP and DECnet.       
    
    The server address is 198.163.xxx.xxx and the client is 10.151.xxx.xxx 
    He did this to prevent internet access for his pc users.                           
    
    Obviously, since users are ultimately able to get logged in, the work-
    station information has been registered correctly in LinkWorks.  Why
    then is there a time delay in LinkWorks when there isn't one with Ping
    or Telnet?
    
    Thanks in advance,
    
    Bruce Burnaman
    CSC/Atlanta
    
T.RTitleUserPersonal
Name
DateLines