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

Conference jamin::pathworks32

Title:Digital PATHWORKS 32
Moderator:SPELNK::curless
Created:Fri Nov 01 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:337
Total number of notes:1612

130.0. "DDCMP / DE205 SSB Kit" by GIDDAY::argus.stl.dec.com::Harkness () Wed Feb 19 1997 22:40

Hello all,

Just a couple of questions with the new SSB kit and possibly the old kits(?) as well...

1) I am seeing an error in the PW Event Logger with a
DEC XL 4100 with an etherworks 3 (DE205). The errors 
are as follows...

  13:45:28    IOCB0003N:    DECnet support is enabled.
  13:45:28    DNP0055E:     Cannot start DECnet: adapter's network address is not set to 
AA-00-04-00-29-C8
  13:45:28    DNP0056E:     Datalink's current address is 08-00-2B-93-5C-04
  13:45:28    DNP0006S:     DECnet Installed successfully

I have used V2.35 and V2.52 driver disks with no changes, any ideas?
I am running NT 4.0 ( a fresh install ..no SP's at the moment ) and Netbui as the only
other protocol.

2) Trying to configure DDCMP by using back to back machines I have noticed

	a) If you do not load a TAPI device driver and start the Connection Manager
	then try to exit, you get a Dr Watson

		PWCM32.exe
		Exception: Access violation (0x00000005), Address 0x77f64bc3

	b) It seems very difficult to setup to connect DDCMP machine to machine
	ie Using the 'Dialup Networking Serial Cable between 2 PC's' tapi drivers.

	Is this a valid config?
	Am I missing something?
	Any other comments
	
	c) Do you have to enter a phone number in this config, or is there some
	other way. Is it possible to set it up to auto dial, or dial on demand
	etc?


Thanks again,


Greg Harkness
Sydney CSC.
T.RTitleUserPersonal
Name		DateLines
130.1nova05.vbo.dec.com::BERGERThu Feb 20 1997 08:1229
	Greg

1) Check your registry: go to 
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services
You should see (among others) a key "EWRK3" and a key "EWRK31". Go to 
the key EWRK31\Parameters. Do you see a value named "NetworkAddress" 
with the value AA0004... as in the Event Log message ? If it's there, 
the driver is bad, ask the EtherWORKS folks. If it's not there, try 
to re-install PATHWORKS 32 (with DECnet). If it's still not there, 
well, we have a problem. Create it manually as a workaround.

2) a) Known problem. Fixed in a post-SSB version (the "TIMA kit") to 
be released in a few weeks. Disappears after you have configured a 
modem (through Control Panel -> Modems).

b) and c) No it's not a valid configuration. You cannot dial in a 
PATHWORKS 32 machine using DDCMP (even if you could, you couldn't get 
access to anything beyond that machine since the DECnet stack in 
PATHWORKS 32 has no forwarding capabilities). DDCMP is made to dial 
out from a PATHWORKS 32 system to a VAX or DEC router.
As for the null-modem part, it's not "really" supported (read: we 
haven't tested it). It might work, provided you have a VAX or router 
on the other side as I said. The connection manager will indeed force 
you to enter a phone number and to "dial", but no dialing will 
actually happen. And no, there's no provision for auto-dial or dial 
on demand.

Hope this helps
	Vincent
130.2JAMIN::MAJEWSKIThu Feb 20 1997 08:1612
    1)  check the info in the README file also.... (excerpt below)
    
        Note for Windows NT V4.0 and Windows 95 systems
        ==============================================
    
        Ethernet and FDDI adapters must support a
        software-configurable network address using the
        NetworkAddress keyword, or you will be unable to use DECnet. 
        Please refer to the "NOTES, PROBLEMS AND LIMITATIONS" section
        in this file for information about the DNP0055 error message
        (and workaround recommendations).
130.3JAMIN::WASSERJohn A. WasserThu Feb 20 1997 10:3011
> 1) I am seeing an error in the PW Event Logger with a DEC XL 4100 with an
> etherworks 3 (DE205). The errors are as follows...
> DNP0055E:     Cannot start DECnet: adapter's network address is not 
>		set to AA-00-04-00-29-C8

	I got the same symptom when I re-installed my network adapter
	driver.  A quick re-install of PATHWORKS 32 fixed it.

	I suspect that removing and installing the adapter driver
	wiped out the settings that PATHWORKS 32 has put in the
	registry to set the address.
130.4GIDDAY::argus.stl.dec.com::HarknessMon Feb 24 1997 20:1232
Thanks,

Re -1;

I have found the same thing. After installing the new driver, I 
needed to reinstall PW32. After this and a reboot, the DE205 worked 
happily.

Re .1;

Thank you Vincent for your input, what i am trying to do is get DDCMP 
working in the simplest config possible. I am still having some 
problems making it work (and so is our customer). 

Is there a fault finding procedure that you would suggest to use, or 
any logfiles that can be generated?

My latest config is

PW32 serial -- Modem-Modem -- VAX serial port
   9600                             9600

Can you place the connection manager in the startup folder, or is it 
possible to make a service of this application ( I keep being asked 
this or some other option??? )



Regards,


Greg Harkness.
130.5nova05.vbo.dec.com::BERGERTue Feb 25 1997 04:4017
> Can you place the connection manager in the startup folder, or is it 
> possible to make a service of this application ( I keep being asked 
> this or some other option??? )

No. You need to press the button.
As for troubleshooting, here is a small checklist:
Does the modem get connected (Carrier Detect) ?
Do you see data transmitted (if the modem has an Xmit LED) ?
Do you see data received (if the modem has an Rcv LED) ?
Is the PC DECnet address in the same area as the VAX (or router) on the 
other side ?
Do you see an event "DECnet adjacency up" in PW Event Log ?

Once you've answered yes to all questions, DDCMP is running.

Hope this helps
	Vincent