|
- Which DLC do I use
for Win3.x, Win95, WinNT?
- How
do I find my Destination Adapter Address?
- Why
does my LU/PC Location Name have to be unique?
- NetSoft
Router won't connect after upgrading from Win3.x to Win95.
- Why
could I connect with PC Support using 802.2 but after loading
NetSoft on my computer The NetSoft Router won't connect?
- How
do I find a lost 802.2 controller on the AS/400?
- Why
could I connect on Friday but can't connect on Monday?
- NetSoft
Router will not connect when I use the Novell 32bit Client?
Which
DLC do I use for Win3.x, WFW, Win95, WinNT?
- Win3.1 you need to install
LAN Support from IBM. This will handle the 802.2 protocol.
- Windows for workgroups
you can use either LAN Support or you can get the Microsoft DLC
for WFW from Microsoft's web site. The file name is WFWDLC.exe.
- When you are using Win95
you need to use the 32 Bit DLC. This is available either on the
Portfolio CD-ROM or from Microsoft's web site. The file name on
the web site is MSDLC32.exe.
- NT 3.51 or 4.0 use the
native DLC that ships with these products.
How
do I find my destination Adapter Address.
At the command line of the
AS/400 type in WRKLIND. Look for your Ethernet or Token Ring line
description. Place a 5 next to the line description to display the
attributes. There you will look for the Local Adapter Address. It
should be a twelve digit number. Use that number as the Destination
Adapter Address.
Why
does my LU/PC Location Name have to be unique
When you are connecting to
the AS/400 using DLC the 400 uses your PC Location Name and the
PC Network card address to identify you. It gives the APPC controller
your PC Location Name and in the controller description it records
your Network card address. If you try to use a PC Location name
already used by someone else the 400 will not allow another controller
to be built using that PC Location Name. Also if there is a controller
on the 400 with your Network card address and you try to use a different
Remote control point name (PC Location name) it will not let you
connect and will not build another controller.
NetSoft
Router won't connect after upgrading from Win3.x to Win95
[In Win3.x LAN Support is
used for the 802.2 protocol, When you use Win95 you need to use
the 32 Bit DLC. This can be found on our Portfolio CD-ROM or search
Microsoft's web site for MSDLc32.exe.]
Why
could I connect with PC Support using 802.2 but after loading NetSoft
on my PC The NetSoft Router won't connect.
Usually this problem occurs
when there is a controller already on the AS/400 for this PC and
it has a different PC Location name. There are two ways to solve
this issue. If you know the name of the controller for this PC you
can put the same name in the NetSoft router. Or you can delete the
controller, set your 400 to autoconfig controllers and let it create
a new controller for this workstation. If you don't know the name
of the controller, please see How do I find a lost 802.2 controller
on the AS/400.
How
do I find a lost 802.2 controller on the AS/400
First you need to find your
PC's Network card address by whatever means available to you. If
the address is less than twelve digits long, pad it to the left
with zeroes. Then you will need to bit reverse the address. (sometimes
DLC will bit reverse your Card address on the 400 and you want to
look for either address) Now at the As/400 command line Type WRKCTLD.
Under OPT place a 5 next to every APPC type controller. After you
have done this press enter to display the first controller. Look
for the LAN Remote Adapter Address that matches either the
normal Card address or the Bit reversed number. If its not in the
first Controller discription press F3 and the next Controller will
be displayed. When you find the controller with your Card address
you can either delete it and let another one be created or you can
look at the Remote Control Point Name displayed in the controller
and use it as your PC Location Name.
Why
could I connect on Friday but can't connect on Monday.
If you were connecting previously
and then you can't, you need to check the state of your APPC controller
on the 400. Is it still vary on pending or does it still exist?
Sometimes they get deleted by mistake. Also make sure that the router
configuration has not been changed by someone.
NetSoft
Router will not connect when I use the Novell 32bit Client
When installing Novell Client32,
the install program will ask you if you want to install ODINSUP.
You will want to answer No to this option. One way to tell if this
is causing you a problem is to look at the bindings. Right click
Network Neighborhood and choose properties. If you see ODINSUP as
a protocol highlight it and choose Properties then Bindings. If
you see Microsoft 32 bit DLC bound to ODINSUP then NetSoft will
not work correctly. The correct configuration will have the DLC
bound to your Network Adapter not ODINSUP. Click on your Network
adapter choose Properties then choose Bindings. This is where you
should see Microsoft 32bit DLC bound to your card. If you choose
Microsoft 32bit DLC in the Network setup and choose Properties and
then choose Bindings you should not see anything there.
Top
|
