[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

797.0. "netware across RA90 EW with bridging" by PRSPSU::JACQUOT (I'm a poor lonesome boy) Wed Mar 12 1997 16:17

Can anyone help me.
I install two Routeabout90 ew in bridging, every thing ok, decnet lat and so
on.
Expect NOVELL. Connection stop when launch VLM.EXE
Client novell is a 3.12 of novell, same for server, frame is 802.2 on both
side.
When i plug the client directly on the same physical thinwire than the server
connection to server is ok.
When i try ipxmicrosoft with my MS WINDOWS 95 pc I can connect to the server,
trough the bridge. ( frame autodiscovery or force frame 802.2)
When itrace with iris, Clieent handsaking with server they exechange 23 frames
and stop, and it's always the number of frames....) 
I try whith IPX routing but same result
version of routeabout is 2.02

Thanks in advance

eric
T.RTitleUserPersonal
Name		DateLines
797.1WAN issue? PBURST?FOUNDR::OUIMETTEZat was Zen, Dis is Dao...Wed Mar 12 1997 17:2719
    	Eric,
    
      The following is about the sum total of *my* IPX experience, but I
    want to suggest it in case it happens to apply. Based on your
    description (client is fine on same lan segment, but fails across
    bridged WAN link), it sounds like a possible WAN link saturation/error
    issue. And the one parameter for IPX that comes to mind is discussed in
    NOTED::NETWARE note 492, PBURST, which allows IPX traffic to "burst",
    not requiring every packet to be acknowledged- This is especially
    appropriate for IPX across WAN links. Also see NETCAD::DEWBR note 628.
    What is the WAN speed anyhow? Any errors, lost frames, or other
    evidence of saturation on the WAN link? IPX is an especially talkative
    protocol (I've seen hundreds of packets required for client logon 
    operations), and may be more sensitive to packet loss due to WAN errors 
    than less obstreperous protocols....
    
    		Good luck,
    
    -Chuck O.
797.2PRSPSU::JACQUOTI'm a poor lonesome boyFri Mar 14 1997 08:2121
Thanks for your reply,

It guides me across the good way to fix my problem.
In fact I began, in section NETWARE DOS REQUESTER, with 
	PB BUFFERS = 0 ( packet burst) does not solve the primary pb.

Second time I try  
	LARGE INTERNET PACKET = OFF
At this time my primary pb was resolved, but now I loose, very often,
connections with server.
To fix it I do in the same section following:
	PB BUFFERS = 0
	SIGNATURE LEVEL = 0
Now it's ok but response time is very very long and I have some trouble to copy 
big files. But at this time that's a test platform with a Modem Emulator, so
I don't know what is the speed of the line so I wait monday for final
configuration with 2 different sites and modems.

Thanks again

Eric
797.3FOUNDR::OUIMETTEZat was Zen, Dis is Dao...Fri Mar 14 1997 14:4812
    	Eric,
    
    From your description, it sounds like there still may be a WAN link
    problem, perhaps sensitive to packet size, at least in your test
    config. When you get it installed on a real telco link, if you still
    see the problems, be sure to check the RA WAN links on both sides for
    datalink errors.
    
    		Good luck,
    
    -Chuck O.
797.4See also NOTE 320 in this conferenceIROCZ::STETSONMon Mar 17 1997 09:230
797.5fix nowPRSPSU::JACQUOTI'm a poor lonesome boyWed Apr 23 1997 10:555
    After a while it's working now.
    In fact that's was the ethernet module of the NOVELL server which had an 
    interrupted problem It's special thing to do with these PC pentium 
    GATEWAY 2000. My trying which working was not on the GATEWAY  2000.
    Eric