Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 456
  • Last Modified:

Processed an NCP with a bad subfunction length

In Netware Monitor, I see the following message:
"Processed an NCP with a bad subfunction length ,
Station xx (NCP 23 121"

By using the Sniffer, the packet that triggers the error is  
displayed as a :"Finishing Servicing Queue Job Request", and
there is no indication of an error.

What is the problem, and how can I remedy it?
0
courd
Asked:
courd
  • 2
1 Solution
 
brosenb0Commented:
The packet is definitely bad.  What version of NetWare on the server ?  This was a known problem with NetWare v4.11 an if that's what you're running, you should patch the server with IWSP5B from support.novell.com.  Try and upgrade the server's LAN driver and/or swap the NIC for another brand/model.
0
 
jwillekeCommented:
Need more inf. Does not imply that the packet is bad, just that the server does not understand the subfunction.
What Client?
What Servers?
Here are two issues I have seen:
1. Rights.exe with the /i parameter builds the NCP packet (NCP 22 50) incorrectly.
2. Older VLM's are known to cause bad NCP messages.
-jim
0
 
courdAuthor Commented:
This problem was solved by updating the code in the print servers.


0
 
brosenb0Commented:
So the print server was sending bad packets then
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now