PC client (Win 2000-SP4) - no connectivity (OK, not VMS, but at least Pathworks)

[Colin Butcher]

PC client with Windows 2000 SP4 (+ all current patches / fixes). Pathworks32 V7.4 network connectivity.

The PC has a real LAN adapter (built-in Intel Pro 100+) and a pseudo-LAN adapter called the "Microsoft TV/Video Connection" which is apparently there because the PC has a USB connected camera device (a Logitech webcam). Here's the informative and helpful Microsoft comment about it: http://support.microsoft.com/default.aspx?scid=kb;en-us;303302&Product=winxp

Pathworks32 tries to bind to both the real LAN adapter and this pseudo-LAN adapter. Regrettably the pseudo-LAN adapter is first in the list. I think that's the cause of the problem.

What happens is that the real LAN adapter doesn't talk LAT or DECnet and there's no connectivity, however the MAC address has changed to a Phase IV style MAC address. My LAN analyser shows no DECnet or LAT traffic from the real LAN adapter.

The pseudo-LAN adapter does not show up in the network connections, so I can't modify it's bindings there, or change the order. The pseudo-LAN adapter only shows up as a hidden device called "Microsoft TV/Video Connection" which it won't let me delete, claiming that it's needed to boot the system.


Here's the messages from Pathworks event viewer, the crucial one being the failure to bind to the pseudo-LAN adapter (unnamed), followed by apparently successfully binding to that pseudo-LAN adapter. I only found the name by ploughing through the Windows registry looking for the GUID.

13:16:10 LOG0002N: PATHWORKS 32 7.4 (build 83 10-Dec-2003)
starts
Logging at 12:16:10, on Monday September 05, 2005
12:16:10 LOG0015N: Message Logger Service (PWLOGSVC) V7.4.009
12:16:10 LOG0011N: NT Version 5.0, Build (2195)
12:16:10 LOG0012N: Hardware Platform: Intel Pentium Pro,
Pentium II
or above (801), Processor(s): 2
12:16:10 CORE0001S: DECCORE Version 7.2.5
12:16:10 CORE0002S: C 1995,2000 Compaq Computer Corporation
12:16:10 NDIS0001S: DECNDIS Version 7.3.36
12:16:10 NDIS0002S: C 2002 Compaq Information Technologies
Group,
L.P.
12:16:10 NDIS0012N: DECNDIS will bind to adapter
\Device\A34D15-5E6D-4D7F-9E28-556768918E4C
12:16:10 NDIS0012N: DECNDIS will bind to adapter
\Device\311E09-C1C9-4CD7-BA73-5D4806D0E305
***** Here's the problem (I think) ***** 12:16:10 NDIS0057E:
Opening
the adapter \Device\A34D15-5E6D-4D7F-9E28-556768918E4C failed. *****
***** Oh really? ***** 12:16:10 NDIS0006S: Datalink installed
successfully. *****
12:16:10 NDIS0008S: Datalink #2 bound to adapter
\DEVICE\311E09-C1C9-4CD7-BA73-5D4806D0E305 (Intel(R) 82559 Fast Ethernet LOM with Alert on LAN*).
12:16:10 SHOW0001S: DECSHOW Version 7.2.5
12:16:10 SHOW0002S: C 1995,2000 Compaq Computer Corporation
12:16:10 SHOW0006S: Installed successfully
***** And here's where it successfully binds to the pseudo-LAN adapter
which it couldn't open earlier ***** 12:16:10 DNP9000N: Bound To
adapter : \Device\DECDNP_DECNDIS_A34D15-5E6D-4D7F-9E28-556768918E4C
*****
12:16:10 DNP0001S: DECDNP Version 7.4.112
12:16:10 DNP0002S: C 2002 Compaq Information Technologies
Group,
L.P.
12:16:10 DNP0003S: Reading database file C:\PW32\PWENT.DAT
12:16:10 DNP0004S: DECnet node name XDPC01 (51.241)
12:16:10 DNP0001S: DECnet TDI interface initializing
12:16:10 DNP0006S: DECnet Installed successfully
12:16:10 IOCB0003N: DECnet support is enabled.
12:16:10 IOCB0006N: DECIOCB Installed successfully
12:16:10 LAT0001S: DECLAT Version 7.2.34
12:16:10 LAT0002S: C 1995,2000 Compaq Computer Corporation
12:16:10 IOCB0004N: DECITOT support is disabled.
12:16:10 IOCB0003N: DECnet support is enabled.
12:16:10 IOCB0003N: LAT support is enabled.
12:16:10 LAT0006S: DECLAT installed successfully.
12:16:11 PWIO0001S: IOCB/DSCB Interface Library (PWIOCB32)
Version
7.1.013 Loaded Successfully.
12:16:11 SPAW0001S: Job spawner (SPAWN32) Version 7.2.027
Loaded.
12:16:29 PRF0001S: (PERFDNP.DLL) Version 7.1.000 Loading
12:16:29 PRF0001N: DECDNP Performance Monitor Loaded
12:16:29 PRF0005N: DECDNP Performance Monitor DnpOpen() called
12:16:29 PRF0008N: DECDNP Performance Monitor DnpOpen()
completed
12:16:29 PRF0006N: DECDNP Performance Monitor DnpClose() called
12:16:29 PRF0002N: DECDNP Performance Monitor Unloaded
12:16:29 PRF0001S: (PERFNDIS.DLL) Version 7.1.000 Loading
12:16:29 PRF0001N: PERFNDIS attached
12:16:29 PRF0003N: PERFNDIS open
12:16:29 PRF0003N: PERFNDIS open
12:16:29 PRF0006N: PERFNDIS open completed
12:16:29 PRF0012N: PERFNDIS close
12:16:29 PRF0002N: PERFNDIS detached
12:18:10 PRF0001S: (PERFDNP.DLL) Version 7.1.000 Loading
12:18:10 PRF0001N: DECDNP Performance Monitor Loaded
12:18:10 PRF0005N: DECDNP Performance Monitor DnpOpen() called
12:18:10 PRF0008N: DECDNP Performance Monitor DnpOpen()
completed
12:18:10 PRF0001N: PERFNDIS attached
12:18:10 PRF0003N: PERFNDIS open
12:18:10 PRF0003N: PERFNDIS open
12:18:10 PRF0006N: PERFNDIS open completed
12:23:01 PRF0001S: (PERFDNP.DLL) Version 7.1.000 Loading
12:23:01 PRF0001N: DECDNP Performance Monitor Loaded
12:23:01 PRF0005N: DECDNP Performance Monitor DnpOpen() called
12:23:01 PRF0008N: DECDNP Performance Monitor DnpOpen()
completed
12:23:01 PRF0001N: PERFNDIS attached
12:23:01 PRF0003N: PERFNDIS open
12:23:01 PRF0003N: PERFNDIS open
12:23:01 PRF0006N: PERFNDIS open completed


Anyone else experienced this inconvenience and know what to do?

[Andy Bustamante]

When I install Pathworks 32 on a PC with multiple physical network adaptors it will ask which one to configure DECnet on. If you're not seeing this behavior then I'll toss out a few PC ideas.

1. Do you need to be running DECnet or will Pathworks over tcp/ip serve your requirements? This removes the need for any add on packages on the PC side.

2. Can you remove the Logitech drivers and software, intall PW 32 and reload the Logitech drivers?

Andy

[Colin Butcher]

Hello Andy,

It's not a physical adapter and doesn't appear in the list of adapters, so Pathworks doesn't ask which adapter to configure.

I do want to use DECnet (and LAT) for testing stuff, so I agree with you that plan B (2) looks like a sensible next step. As it's a Microsoft driver (not a Logitech on) that apparently comes into play whenever you add any USB webcam type device then I guess I might have to also remove the "Microsoft TV/Video Connection" driver after de-installing the Logitech webcam stuff.

Cheers, Colin.

What would be nice (assuming that my diagnosis of what's gone wrong is correct) is to have the Pathworks client fixed to only deal with physical adapters, or pseudo-adapters tied to physical adapters (or just avoid this particular pseudo-adapter).

[Andy Bustamante]

I've more than one configuration issue on a PC with more than 1 NIC. As a rule, I like to keep DECnet and LAT on a private LAN. This has been a good thing when wormed PC hits a a customer network. Lately I've been pushed to allow remote network access to the Wintel folks.

Andy

[Antoniov.]

Colin,
I understand you can's see TV network adapter in myNetwork (or Neighbourhood, I don't have english OS).
At first glance you can open device manager (right click on myComputer->Property ...) and see how change some property of device. You can change any, you can create a 2 hardware configuration with that device disable. This congiuration can solve but you must choice pathwork configuration or TV configuration at boot time.
I'm amazed tv conenction is network adapater whil you cannot see it in avaiable connection.

Antonio Vigliotti

[Colin Butcher]

I'm surprised by not being able to see the TV/Video pseudo-adapter either. Maybe it's a Windows 2000 thing and it would appear in Windows XP. Interestingly enough Pathworks is fine on a machine with a single NIC and no webcam. Adding the webcam (and thus this pseudo-LAN adapter from Microsoft) causes the error. I might try adding a second physical NIC and re-installing Pathworks to see if it then asks which adapter to configure when I have time.

The 'easy' workaround for the moment was to set up a spare PC for Pathworks / eXcursion / PowerTerm testing.

[Willem Grooters]

Conflicting PnP idents? I've seen that before.
Therefore I doubt a second NIC would help.