[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | FDDI - The Next Generation |
|
| Moderator: | NETCAD::STEFANI |
|
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
1392.0. "DEC2300.DEFEA FDDI,V5.0a & DECnet NoGo" by FSSB::JOHNSON () Fri Jul 08 1994 10:24
A customer of mine has been trying to get a DEC 2000/300 to
work with Pathworks for OVMS v5.0a.
The server is configured with a DEFEA FDDI board and setup to
run both DECnet and NETBEUI in standalone domain mode.
The PC's sits on ethernet, and gets their licenses loaded OK
from another V5 server.
A PW V4 client running DECnet trying to connect to PWV50 share
gets a "Server not listening" error.
A PW V5 client running DECnet trying to connect to PWV50 share
gets a "Network path not found" error.
A PW V5 client running NETBEUI gets connected OK.
DECnet on the server works perfectly well as is, e.g. file copies
etc., and there are no NCP error counters. The Ethernet/FDDI bridge
between the server and the PC does not filter out any protocols.
When we moved the server to a private thinwire Ethernet segment
along with a PC, everything worked OK, indicating that there's
something wrong with the DEFEA FDDI I/F?
Is there something obvious with the setup we have missed here, or
are there problems with the DEFEA board?
Grateful for some help.
Mats J.
(posted in PWDOSWINV5, PWV50IFT & FDDI conferences)
| T.R | Title | User | Personal
Name | Date | Lines
|
|---|