Wrong port used when remote deployment is connecting.
Bug #434472 reported by
nickolas66
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | ||
|---|---|---|---|---|---|---|
| OCS Inventory: Agent Deployment Tool | Status tracked in Trunk | |||||
| Trunk |
Fix Released
|
Low
|
Didier Liroulet | |||
Bug Description
Windows firewall have an exception for filesharing. Without this exception it is not possible
to connect to an admin share like C$ that you use for installing OCSAgent remotely.
But Windows default exception rule enable this ports:
TCP 139
TCP 445
UDP 137
UDP 138
Your software also require TCP port 135. Why ?
All my computers in the organisation only have Windows default rule enabled for filesharing
and then your deployment tool doesn't work.
Is it possible to change this ?
Related branches
| Changed in ocsinventory-deploy-tool: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| assignee: | nobody → Didier Liroulet (dliroulet) |
Revision history for this message
| Didier Liroulet (dliroulet) wrote | #1 |
To post a comment you must log in.
Hy,
We were checking TCP 135 because of old NT 4.0 and previous OS.
We've updated the tool to check TCP 445, because we only support now windows 2000 and higher OS.
Fix committed on revision 36 for 2.0.0.4 release.
Cheers