| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Hello,
Are there any known problems with the DECswitch 900EF and netbios
emulation?
A customer has 2 alphas on a FDDI ring out of the front ports of a
decswitch 900ef. The other ports are switched internally to seperate
vertual lans. Connections go to PCs via a Decrepeater 900FP from these
vertual LANs.
The customer has problems loading pathworks licenses from the alphas to
the PCs (which I understand uses netbios emulation) across the
Decswitch. If he connects a PC directly to the alpha via its thin wire
port it loads the licenses correctly.
Are there any known problems along these lines?
There are no filters set up on the Decswitch and I am currently waiting
for the Versions of the Decswitch & Hub900 firmware.
All other protocols (LAT, Decnet etc) are passed successfully accross
the Decswitch.
Any help appreciated.
Regards,
Jon ward
UK CSC
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3631.1 | Wag | KEIKI::WHITE | MIN(2�,FWIW) | Tue Jun 18 1996 23:29 | 5 |
NETBIOS on PATHWORKS will only use one interface, sounds like the
one it chooses is the Ethernet Interface.
Bill
| |||||
| 3631.2 | How is the choice made? | KERNEL::WARDJO | Tue Jun 25 1996 11:15 | 13 | |
Thanks for the response Bill.
I've been out of the office and only just got a chance to check this
entry.
Do you know how the decission is made as to which interface is chosen?
Thanks,
Jon
| |||||
| 3631.3 | CSC32::D_PERRIN | Wed Jun 26 1996 11:05 | 49 | ||
I think Pathworks just uses the first controller it comes to at
startup time, which usually turns out to be the ethernet adapter. This
can be controlled by logicals. See the following article:
[PW-VMS]V5 Updated Server From Ethernet to FDDI... Clients Unable To Connect
Any party granted access to the following copyrighted information
(protected under Federal Copyright Laws), pursuant to a duly executed
Digital Service Agreement may, under the terms of such agreement copy
all or selected portions of this information for internal use and
distribution only. No other copying or distribution for any other
purpose is authorized.
Copyright (c) Digital Equipment Corporation 1995. All rights reserved.
PRODUCT: PATHWORKS V5 for OpenVMS (LAN Manager), Version 5.0
OP/SYS: OpenVMS VAX, Version 5.5-2, 6.0, 6.1
OpenVMS AXP, Version 1.5, 6.1
SOURCE: Digital Equipment Corporation
PROBLEM:
A user upgraded their server from ethernet to FDDI. Since doing so his clients
are unable to connect.
SOLUTION:
To correct the problem do the following:
Edit SYS$STARTUP:PWRK$LOGICALS.COM and add the lines:
DEFINE/SYSTEM NETBIOS$DEVICE FQA0:
DEFINE/SYSTEM PWRK$NETBEUI_DEVICE FQA0:
DEFINE/SYSTEM PWRK$KNBDAEMON_DEVICE FQA0:
Next do
@SYS$STARTUP:PWRK$LOGICALS.COM
to set new logicals and then restart PATHWORKS on the server.
OR
Put these logicals into SYSTARTUP_VMS.COM before PATHWORKS starts.
@SYS$STARTUP:PWRK$STARTUP
| |||||
| 3631.4 | or... | CPEEDY::CONWAY | Mon Jul 01 1996 19:55 | 19 | |
If defining the logicals does not work, or (as I suspect) they are
already defined, you may want to check out PATHWORKS note 2409:
<<< NOTED::DISK$NOTES9:[NOTES$LIBRARY_9OF4]PWV50IFT.NOTE;1 >>>
-< PATHWORKS V5.0x for OpenVMS (LAN Manager) >-
================================================================================
Note 2409.18 ?'S About Licenses Over WAN
18 of 18
TOHOPE::WSA104::VORE_S "Nothin but 'Net" 5 lines
15-MAY-1995 09:19
-< Looks good, Lew, thanks. >-
--------------------------------------------------------------------------------
[PW-DOS]V5 FastD: Obtaining a License From a Cluster Over a WAN
This article provides detailed information on the FASTLANE MASTER
article:
FASTM: V5 License Issues Master xFM0046
| |||||