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

Conference ranger::pathworks_netware

Title:PATHWORKS for OpenVMS (NetWare) Conf.
Notice:Shipping on OpenVMS/Alpha and OSF/1 - ECOs=314.* - Kits=21.*
Moderator:DELNI::GORCZYCA
Created:Wed Nov 04 1992
Last Modified:Tue Jun 03 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:805
Total number of notes:2930

793.0. "PW Packet Sizes" by NETRIX::"QuanRichard@mail.dec.com" (Richard Quan) Tue Mar 25 1997 11:20

I have fielded the following query:

----------------
We were looking at a slow response problem that some of our PC users had,
and found the following:

1. A user with a PC and Novell 3.12 client is accessing a volume that is
offered by an Alpha running VMS 6.2 and Pathworks for Netware.

If the Alpha is on the same LAN, the maximum packet size that is exchanged
 between the PC and the Alpha is ~1080.
If the Alpha is over the WAN, the packet size is no more then 562.

The same PC can access a volume offered by an Intel based server, will
use a packet size of 1498 for both cases (LAN or WAN).

We tested also access to an Alpha with WNT and NW (only on the LAN),
and the packet size was ~1498.

The above test was done with NETX on the client. The same test with VLM
gave similar results.

2. I can see a patern where the VAX or Alpha will use a much smaller packet
then a native Novell server. This will cause us performance problems, as
the time it take to perfrom file access over the WAN or LAN is longer.

Is there a way to force the VAX/Alpha to use the larger packet size?

---------------

Richard Quan
Tech Support CSF Melbourne

[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name
DateLines
793.1IPX-router = smaller packetsCPEEDY::COOKJust say NO to that AccViO! - Java!!!Tue Mar 25 1997 14:3110
    
    The behavior you describe (smaller packets) will happen when
    the packets pass thru an IPX-router...i.e. the router is necessitating
    shorter packets.  (An IPX router will even be involved if the frame-type
    set for a client does not match the frame-type being used at the
    server, as can be true on our LKG-lan, where there are frame-type
    IPX routers setup so that clients can be configured to use whatever
    IPX-frametype they choose.)