"NBXPkt2k.sys" vs. "XP SP2"

[Smithead]

Hello folks,

Longtime reader first time poster... ok I've only been reading this forum for 30 minutes but for someone with ADD, that's a long time.

The pcXset software works fine (granted my expectations for quality in software have diminished over the years...). It uses "NBXPkt2k.sys" (bound to your NIC) to communicate with the NBX. So far, so-so good.

XP SP2 is a step forward in many ways for Microsoft... at least in philosophy if not in actual implementation. Hmmm... secure by default instead of "bare-naked to the world" by default...it might just catch on! So this is ok to, I guess.

But then they round the corner and bump into one another and all of a sudden it's "Hey, you got "NBXPkt2k.sys" in my "SP2". "Well you got "SP2" in my "NBXPkt2k.sys"! Only the result is not quite as tasty as a peanut-butter cup. It turns everything a beautiful blueberry color (for those of you not following me... "Blue(berry) Screen of Death").

BAD_POOL_HEADER
Stop Error 0x00000019

I can boot in safe mode but when I try to run pcXset I get:

Error code: [80042002H]
Error message: Error beginning stream (leave your personal problems at the door, buddy)
Context: Initializing - EngineWrapperClass.bStart
This error has occurred in the multimedia subsystem.
Please contact....yada-yada-yada.

If I try to start the pcXset setup wizard:

Error code: [80046000H]
Error message: H3GetAdapterNames failed 2
Context: Initializing - EngineWrapperClass.varNetworkAdapters
This error occurred in the Communications object.
Please contact....etc.

Now the 2 most recently noted errors above may be a result of being in safe mode and therefore may not have anything to do with the real issue....remember, the Reese's problem?

My NIC is 3COM 3C920 (3C905 compat). I re-installed the latest drivers today... no love.

MS error reporting proudly tells me that the problem is with "NBXPkt2k.sys"..."Please contact....". Sheesh!

I tried disabling all the new "security features" I could find in SP2 (sure I missed some)... no dice. If I uninstall SP2, the phone works. If I uninstall the phone, Windows is happy again. I disabled the NBX packet driver…sigh.

I uninstalled the driver and rebooted, NO BLUE SCREEN! Yeah, but the friggin' phone doesn't work even though you've told it to force Layer 3.

Someone...anyone....?

Help a brutha out!

 

[Smithead]

One more thing...

The packet driver does not have a digital "Microsoft says it's ok" signature.

 

[GoTellBigDaddy]

what NBX OS are you running and which version of pcXset do you have ?

 

[Smithead]

NBX 100: R4_1_21
pcXset: 4.1.2

thx for reply

I just downloaded microsoft's guide to app compatibility testing with SP2. If anything useful turns up I will post it.

 

[GoTellBigDaddy]

I think you will find two things:

Yesterday, I was onsite with IT staff and they were raking the recent XP SP2 and how bad the release is.

Secondly, update the NBX OS to 4.1.77 and get the updated pxXset client for the matching 4.1.77 NBX OS release.

Not that it will resolve the problem !

My gut tells me XP SP2 is blocking some port or worse.

 

[Cozzman]

I have XP SP2 and PCXSet version 4.3 and NBX SS3 with r4.3.3 and have no issues.

I have however recieved those messages before. You have to play with the Force layer 3 and force your network adapter to the 3Com and don't let it autodetect. It needs to be said that you should always troubleshoot these problems on the same subnet as your NBX. If you still have problems try getting your hands on the latest rev of PCXset. I've tested v4.3 of PCXSet to work with 4.1.77.

FYI if you use SMTP mail to your system it was disabled in 4.1.66 and I and one other user b*tched and yelled until they made 4.1.77 as a one up with a secret page to turn it back on again. You may need to know it. It's

http://10.15.15.190/sec_cont/system/systask.htm

Just replace my ip with yours.

 

[techguru69]

I'm running both nbx 4.2.7 with the delivered version of PcXset and nbx 4.3.3 on XP2 without issue. According to the tech doc's, there were no chnages to any of the utils between 4.2.7 (or .9) to 4.3.3.

Not that it helps your issue, but you may want to spend the $$ and upgrade to 4.2.x or 4.3.x.

Tallyho,
Mike

"Any society that needs disclaimers has too many lawyers."

 

[Smithead]

Thanks Guys

So, no one has pcXset 4.1.x running on XP SP2?

Is there any way to purchase the software by itself without first signing a maintenance contract with a reseller? I'm new to the 3COM world, but from what I can tell so far, I can't get the software except through a reseller and I can't even do that without a contract. Currently my company does not have a contract with a reseller and frankly they do not want to spend the money right now. But they DO want the software phones... AND they DO want SP2.

No contract... no upgrade. Whatza po' Sys Admin ta do?

 

[techguru69]

I would suggest that that is specific to the reseller as we purchase a site license through a reseller but have a seperate contract with another 3rd party for support and maintenance. We have no direct contract with either 3Com nor the reseller for the NBX's. They just take your $300 for the upgrade and sell it.

If the reseller says that 3Com requires it, they are either misinformed or just not telling the truth.

A good example of a 3rd party is NBX Helpdesk - a fine organization who provides all the support you need. I believe I saw NBXBob posting in this forum - he works for them.

I would suggest maybe that one of the vendors that is posting in this area respond to this as maybe they can sell you the upgrade without the contract.


Tallyho,
Mike

"Any society that needs disclaimers has too many lawyers."

 

[GoTellBigDaddy]

Smithead- absolutely. The Dealers charging you for the UPGRADE ? The charge to upgrade to 4.2 is a chargeable item from 3Com but not for the previous releases and application updates.

I get my updated software from the website

http://www.nbxgroup.com

and I also got a discount for the Site License for 4.2 software from them. Their FTP service is great and no DEALER ever shows up to charge me for upgrading my NBX or NBX applications.