Clarify Communication Ports for Patch Management pack

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

Clarify Communication Ports for Patch Management pack

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Vendor Forums] >> 1E Products >> Clarify Communication Ports for Patch Management pack

Page: [1]

Message

<< Older Topic Newer Topic >>

Clarify Communication Ports for Patch Management pack - 4/8/2008 9:56:03 AM

kev147

Posts: 138
Score: 2
Joined: 1/28/2007
Status: offline

Hi I just want to clarify that for our remote VPN sites protected by firewalls, do we need to allow the following ports access to our primary configmgr server?

TCP 1776
TCP 1777
UDP 1776
UDP 1777

The port numbers shown are obviously the default numbers, we will change the port numbers accordingly.

Does the communication channels have to remain open from

The Primary ConfigMgr Server to the Client
The Client to the Primary ConfigMgr Server

This is for the following products:

SMSWakeup
NightWatchman

Post #: 1

RE: Clarify Communication Ports for Patch Management pack - 4/8/2008 9:11:15 PM

pfreestun

Posts: 32
Score: 1
Joined: 5/9/2006
Status: offline

SMSWakeUp

TCP 1776 is used by the SMSWakeUp service on the server to communicate to the Agent service on the client machines. (wakeup lists)
TCP 1777 is used by the Agent service to communicate back to the SMSWakeUp service. (wakeup statistics)

UDP is used for traffic at the local subnet level, to send the WakeUp Magic Packets and for subnet broadcast communication between the client Agent services. This will not require any WAN firewall exceptions.

NightWatchman is client based and does not communicate with the management server.

If you are using Agility Framework Reporting then both products will send data to the AFR IIS server over HTTP Port 80.

(in reply to kev147)

Post #: 2

RE: Clarify Communication Ports for Patch Management pack - 4/9/2008 5:16:50 PM

kev147

Posts: 138
Score: 2
Joined: 1/28/2007
Status: offline

Thanks for the reply.

I have the SMSWakeUp and the Agility Framework Reporting installed on the Primary ConfigMgr server.

Just to confirm then, I need to arrange the following:

Allow port TCP 1776 to communicate to all of the clients from the SMSWakeUp Service on the Primary ConfigMgr Server.
Allow port TCP 1777 to communicate with the SMSWakeUp Service on the Primary ConfigMgr Server from all the clients.
Allow HTTP port 80 to communicate with the AFR on the Primary ConfigMgr Server from all the clients.

(in reply to pfreestun)

Post #: 3

RE: Clarify Communication Ports for Patch Management pack - 5/6/2008 5:28:12 AM

kev147

Posts: 138
Score: 2
Joined: 1/28/2007
Status: offline

Polite Bump. I have reread my last update and have reworded as it didn't make much sense to me when I re-read it.

I have the SMSWakeUp and the Agility Framework Reporting installed on the Primary ConfigMgr server.

Just to confirm then, I need to arrange the following:

Allow SMSWakeUp Service on the Primary ConfigMgr Server to communicate to All Clients over port TCP 1776.
Allow All Clients to communicate with the SMSWakeUp Service on the Primary ConfigMgr over port TCP 1777.
Allow All Clients to communicate with the AFR on the Primary ConfigMgr Server over HTTP port 80.

< Message edited by kev147 -- 5/6/2008 5:33:19 AM >

(in reply to kev147)

Post #: 4

RE: Clarify Communication Ports for Patch Management pack - 5/6/2008 11:04:57 AM

ealdrich

Posts: 459
Score: 9
Joined: 6/1/2001
Status: offline

Sorry for the delay... MMS week and all... most are still in recovery mode! :-)

Hope this helps. It comes from a nice Visio block diagram that I apparently cannot paste here, but here's the text:

(1) Port 80 or whatever port is being used for HTTP traffic is used by NightWatchman and WakeUp to send client status data back to the agility reporting server.
(2) Port 80 or whatever port is being used for HTTP traffic is used by the client to shop for packages.
(3) Port 69 is used for TFTP traffic from the local PxeLite server.
(4) Port 67 and 4011 is used to trap DHCP calls to ensure PxeLite traps any data for itself.
(5) 17470 is used local subnet discovery packets on port 17470.
(6) 2535 is required by the DHCP MADCAP scope to allow Nomad Multicast

_____________________________

Ed Aldrich | Solutions Engineer | 1E Inc
Mobile: (401) 924-2293
US/Canada Toll Free: (866) 592 4214
Ed.Aldrich@1e.com | www.1e.com
SMS MVP (2003-2007)
myITforum Advisory Council and Columnist
New England Area SMS User Group Facilitator

(in reply to kev147)

Post #: 5