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

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

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

1012.0. "PROBEwatch Windows Questions?" by WOTVAX::64021::Tim_Banks (Network Mercenary) Fri May 20 1994 09:10

The customer I work with who has the Windows FT kit, has come back with some 
questions and wishes,

1.	Are we or Frontier doing any work to improve the OSI protocol decode, 
as currently it only decodes the MAC layer, and gives everything else as HEX. 
 As we are debugging 3rd party OSI connectivity problems over a DECNIS OSI 
network, we could really use this feature.  IRIS gives a better OSI decode 
currently.

2.	How do you get IP names displayed instead of addresses?  Jack 
mentioned you could suck in the host host file for the UNIX version, but how 
about Windows? Can the same thing be done for DECnet nodes?

There are more questions coming,

	Thanks for the help

		Tim

T.R Title User Personal
Name Date Lines

1012.1 gettting better NAC::FORREST Wed Jul 06 1994 22:47 17

T.R	Title	User	Personal Name	Date	Lines
1012.1	gettting better	NAC::FORREST		`Wed Jul 06 1994 22:47`	17
	1. Are we or Frontier doing any work to improve the OSI protocol decode, as currently it only decodes the MAC layer, and gives everything else as HEX. As we are debugging 3rd party OSI connectivity problems over a DECNIS OSI network, we could really use this feature. IRIS gives a better OSI decode currently. JF> I will check to see where Frontier is with this; they wanted to release JF> Windows as soon as they could, so they left out some things. The other JF> thing they are doing is a translation to Sniffer format, so that you JF> can capture the file using a probe and read it using a Sniffer, with JF> its rich protocol decode functionality. 2. How do you get IP names displayed instead of addresses? Jack mentioned you could suck in the host host file for the UNIX version, but how about Windows? Can the same thing be done for DECnet nodes? JF> You can use Tools/Discovery from the menu bar to learn IP names and JF> addresses. The name may have to be in the hosts file too. Unfortunately JF> this version of Windows does not have DECnet name or address tranlation.

1.	Are we or Frontier doing any work to improve the OSI protocol decode, 
as currently it only decodes the MAC layer, and gives everything else as HEX. 
 As we are debugging 3rd party OSI connectivity problems over a DECNIS OSI 
network, we could really use this feature.  IRIS gives a better OSI decode 
currently.
JF> I will check to see where Frontier is with this; they wanted to release
JF> Windows as soon as they could, so they left out some things. The other 
JF> thing they are doing is a translation to Sniffer format, so that you 
JF> can capture the file using a probe and read it using a Sniffer, with 
JF> its rich protocol decode functionality.

2.	How do you get IP names displayed instead of addresses?  Jack 
mentioned you could suck in the host host file for the UNIX version, but how 
about Windows? Can the same thing be done for DECnet nodes?
JF> You can use Tools/Discovery from the menu bar to learn IP names and 
JF> addresses. The name may have to be in the hosts file too. Unfortunately 
JF> this version of Windows does not have DECnet name or address tranlation.