I am migrating my users to a new Netware 6.5 server. I have recreated all of my printers (I wanted a more standard name, and wanted to get rid of queues). I have about 85 users and right now 5 of them are having the same problem. After installing the printers they try to print and get an error message stating that xxx has caused an exception in msvcrt.dll. All but one workstation I have track down if I turn off Windows Firewall the problem will go away. I have remove NDPS from the exception list and restart the computer and told the firewall to allow NDPS through. With the firewall on the users can not print with the firewall off they can. I really do not want to turn off the firewall because some of the users are laptops and take them to places I am not in control of.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
NDPS Printing problem
- Thread starter phart
- Start date
You might need to allow the PCs to accept and reply to ICMP packets.
You can make the change in the Firewall settings under the ethernet interface, last tab I believe.
Lorenzo Wacondo (System Administrator)
## Just because you can do something doesn't mean you should.
You can make the change in the Firewall settings under the ethernet interface, last tab I believe.
Lorenzo Wacondo (System Administrator)
## Just because you can do something doesn't mean you should.
- Thread starter
- #3
IRudebwoy, Thanks, that help on 2 of the PCs the others I am still having trouble with. The problem now is that this time they work, next time they do not. I am checking the dirvers and anyother settings I can think of. If you have any other suggestions I would apprecaite them.
Do the firewall settings keep after a reboot?
If they don't keep you might have to reflect the change in the policy you might be enforcing. Make sure you are logging all dropped packets on the client firewall to verify.
You might have to check all the ICMP settings in the execption list for the LAN interface.
Good luck.
Lorenzo Wacondo (System Administrator)
## Just because you can do something doesn't mean you should.
If they don't keep you might have to reflect the change in the policy you might be enforcing. Make sure you are logging all dropped packets on the client firewall to verify.
You might have to check all the ICMP settings in the execption list for the LAN interface.
Good luck.
Lorenzo Wacondo (System Administrator)
## Just because you can do something doesn't mean you should.
- Thread starter
- #6
- Status