Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
4640 views

NDPS RPM & Notification Listener ports anyone?

Hi folks,
anyone know which ports are needed to exclude the NDPS RPM & Notification Listener from Windows Firewall. We've had to turn the firewall on for desktops as part of counter-measures for a virus outbreak. I just need to put in exclusions to allow the NDPS RPM & Notification Listener to run.
Thanks very much,
Scott Gordon
0 Likes
2 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=10065719&sliceId=&docTypeID=DT_TID_1_1&dialogID=38259406&stateId=0%200%2038257505

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

I also got this from someone who knows far more than I do about NDPS:

There is also
http://support.novell.com/docs/Tids/Solutions/10056598.html, which is
perhaps slightly more verbose than the raw port list.

Note that opening ports for the "NDPS RPM & Notification Listener"
(the description of the DPMW32.EXE process, as presented in firewall
pop-up warnings in the Windows firewall and others) is usually
optional and non-required for many customer configurations.

The firewall authorization is occurring specifically because the
DPMW32.EXE tries to open ports via Winsock for listening for NDPS
programmatic notification traffic (port 3017) inbound to the
workstation. This kind of communication is only used by the "directed
pop-up notification" method; as opposed to general "pop-up
notification", which uses normal NetWare-type end-user broadcast
messages.

If you're not using NDPS print job notification at all, or if you're
not using "directed pop-up notification", reducing your security
exposure by letting the firewall continue to block any attempts to
probe or send communication to this open listening port is a valid
option. Knowing that you can always open the port up if and when the
feature is actually required.

Note that no amount of port blocking for the DPMW32.EXE process stops
or interferes with NDPS Remote Printer Management (RPM) on Novell
Client for Windows XP/2003. There is no direct IP communication to or
from this DPMW32.EXE process that is required in order to support the
RPM feature; this process' role in RPM occurs in other ways, not by
direct IP listening or communication.

- Anders Gustafsson (Sysop)
The Aaland Islands (N60 E20)

Discover the Novell forums at http://forums.novell.com

Novell does not monitor these forums officially.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.