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

Conference irocz::common_brouters

Title:Digital Brouters Conference
Notice:New common-code brouter family: RouteAbout, DECswitch 900
Moderator:MARVIN::HARTLL
Created:Mon Jul 17 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:929
Total number of notes:3736

768.0. "RA 90EI V.2.0 IPXWAN over ISDN" by NETRIX::"ulf.nilsson@dmo.dec.com" (Ulf Nilsson) Thu Feb 20 1997 14:02

We are using RouteAbout Access EI V.2.0 where we have configured to units via
ISDN. We have a Novell Server at IPX network no. 100 and some clients at the 
other side, -IPX network no. 20.

In between, we have a common network, numbered 101 as Net3 which is the DIAL
DEVICE over ISDN.

We are able to communicate and the system is working well! When not using the
client, the line is tered down. But! When starting to work again, we receive 
this message:

   WAITING FOR CONNECTION TO SERVER. CONNECTION REFUSED

        RETRY OR ABORT


The first time you retry, you get the same message. The second time you try,
the
connection is there, and you ar able to communicate!

Is this right???? I thought you avoided this type of error messages since IPX 
spoofing or IPXWAN, was taking care of this!



The configuration is like this:


IPX config>list all

IPX globally                	enabled
Host number (serial line)   	000000000345
Router Name (IPXWAN)        	ODENSE
NodeID (IPXWAN)             	857
Maximum networks            		        32
Maximum total alt. route entries        	128
Maximum alt. routes per dest. network   	3
Maximum services                        	32
Maximum Network Cache entries           	64
Maximum Local Cache entries             	64


List of configured interfaces:

                Frame                   	SAP nearest	Split        
Ifc  IPX net #  Encapsulation           	server reply 	Horizon      IPXWAN    
   

0    100        	ETHERNET_802.3         	Enabled      	Heuristic     N/A      
    
2    27         	N/A                    	Enabled      	Heuristic     N/A      
    
3    101        	N/A                    	Enabled      	Heuristic     Enabled  
    


RIP/SAP Timer Intervals

Net  IPX net #        SAP Interval(Minutes)   RIP Interval(Minutes)
  0        100                   	1                      	1
  2         27                   	1                      	1
  3        101                  	30                     	30

IPX SAP Filter is: disabled
No IPX SAP Filter records in configuration.
IPX Access Controls are: disabled
No IPX Access Control records in configuration.

IP Tunnel Mode Disabled
No IPX IP TUNNEL records in configuration.

Keepalive Configuration
Net  IPX net #        	Keepalive               Timeout(Minutes)
  3    101        	Enabled                         30

NetBIOS Filtering Configuration

Net  IPX net #    NetBIOS Filtering
  3    101        Disabled

IPX config>


The router in the other end has the same configuration except for:

Host number (serial line)   	000000000227
Router Name (IPXWAN)        	XBORG
NodeID (IPXWAN)             	137



Please let me here from someone who is experienced in this!

Kinds
Ulf


[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
768.1MARVIN::CLEVELANDFri Feb 21 1997 08:4212
    IPX spoofing (in the current versions) only spoofs the server, not the
    client.  The intent is to keep the dial line from staying up
    constantly, not to make the IPX stations think their connection is
    still alive.
    
    I suspect your client has timed out the connection, and then when you
    retry the call is made and everything connects back up.  But I'm not
    an IPX expert by any means...
    
    Another possibility is that the connection isn't reestablished quick
    enough for the client.  Can you tell if the first attempt (that fails)
    actually triggers the RouteAbout to make an ISDN call?