NDIS Usermode I/O Protocol

Similac

Hit some new ground today when the Wireless Zero Configuration service wouldnt start because a dependent wasnt running.

The RPC is listed in services as started so I am assuming that it is the NDIS usermode I/O Protocol that is the failing dependent....but I'm not sure how to start it, reload it, or possibly update it. Anyone have experience with this problem?
_________________
MCITP:Enterprise Administrator, MCITP:Enterprise Support

avon1982 · Moderator Joined: 23 Apr 2005 Posts: 722 Location: india

Are you using any third party application using EAP authentication ?
Check the driver for the wireless adaptor is windows compatible and supports wireless zero configuration Try unistalling the driver and reinstalling it
_________________
MCSE 2003

Similac · **Post subject:** **Posted:** Sun Jan 07, 2007 5:11 am

It's a Linksys WMP54GS and IM pretty sure it's WZC compatible. There weren't any wireless utilities on it at first, but I was able to put the linksys utility on the computer and control the card. Would like to fix this problem if it is indeed a problem and not a compatibility issue though.
_________________
MCITP:Enterprise Administrator, MCITP:Enterprise Support

masterchi · **Post subject:** **Posted:** Sun Jan 07, 2007 3:24 pm

So are you able to get connection with this Linksys utility?

If not then just uninstall the utility (windows xp has its own utility and when you install another utility over it, it kills the wireless zero utility which is windows utility). Uninstall the linksys utility but keep the driver and then reboot and use the windows utility to connect.
_________________
Current - A+, Network +, 70-210(MCP), 70-270, 70-290, MCDST
Working - 70-291 to get MCSA 2003 status (I think I took the long way to MCSA lol )

Similac · **Post subject:** **Posted:** Sun Jan 07, 2007 3:31 pm

When the Linksys utility is uninstalled the WZC still wont run because a "dependent wasnt able to start" and therefore the WZC service itself can't start up. Seems like something pretty obscure is messed up somewhere, I jsut cant find what it is.
_________________
MCITP:Enterprise Administrator, MCITP:Enterprise Support

masterchi · **Post subject:** **Posted:** Sun Jan 07, 2007 4:51 pm

have you tried right clicking on the service and going to the dependencies tab and see what dependencies it needs to run and then ensure all those services are started ?
_________________
Current - A+, Network +, 70-210(MCP), 70-270, 70-290, MCDST
Working - 70-291 to get MCSA 2003 status (I think I took the long way to MCSA lol )

Similac · **Post subject:** **Posted:** Sun Jan 07, 2007 7:10 pm

yes I have, the RPC service and the NDIS usermode I/O Protocols are the only ones listed. The RPC service is listed as started and is also able to stop and start, so I'm assuming it's working fine. Which would also lead me to believe it's the NDIS that is messed up somehow.

It does work however with the utility, but this is something that I would kind of like to know how to fix in case I run into it in the future in a situation where a utility is not an acceptable fix.
_________________
MCITP:Enterprise Administrator, MCITP:Enterprise Support

masterchi · **Post subject:** **Posted:** Sun Jan 07, 2007 9:09 pm

Now this is just an assumption but i read somewhere that Linksys actually uses the Windows NDIS driver while other programmers/wireless card makers use their own version of NDIS so the Linksys utility that you put on that probably corrupted it. I think from now on your only choice is to do a system restore to before you installed that utility/driver and just install the driver itself no Linksys utility.
_________________
Current - A+, Network +, 70-210(MCP), 70-270, 70-290, MCDST
Working - 70-291 to get MCSA 2003 status (I think I took the long way to MCSA lol )

Similac · **Post subject:** **Posted:** Tue Jan 09, 2007 1:23 pm

Will give it a try, appreciate the help.
_________________
MCITP:Enterprise Administrator, MCITP:Enterprise Support