UDP Port 1863 Problem

[Guest]

We are rolling out Windows XP to a number of sites. At certain sites, users
are unable to logon. We have troubleshot the problem for 3 days and
discovered two solutions to the problem.
One solution is to remove the rule on the Access Control List (ACL) on our
site routers that block UDP port 1863.
The second solution is to add the user to a global group that we have
setup to allow users to manage network print queues.

We would like to know why UDP port 1863 is required to be open for a user to
logon to the domain and also how this could be related to a printer admin
global group. These solutions don't make any sense to us and we would like
to get to the root of the problem.

 

[David Matson]

1863 is MSN Messenger... strange.
(I'm not any authority; just a regular end-user)

-matson

We are rolling out Windows XP to a number of sites. At certain sites, users
are unable to logon. We have troubleshot the problem for 3 days and
discovered two solutions to the problem.
One solution is to remove the rule on the Access Control List (ACL) on our
site routers that block UDP port 1863.
The second solution is to add the user to a global group that we have
setup to allow users to manage network print queues.

We would like to know why UDP port 1863 is required to be open for a user to
logon to the domain and also how this could be related to a printer admin
global group. These solutions don't make any sense to us and we would like
to get to the root of the problem.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB1Igy1PuK4U5KdioRAhhpAJ9KXzO38kXV79RJKyLQz6vOAsWZ4gCglnly
ZmcMWgwGecDSCrqUyGRhrZM=
=V5Xw
-----END PGP SIGNATURE-----

 

[Guest]

I realize that 1863 is for Messenger, which is why we were blocking it on the
router. Apparently it is also used for something else which is preventing
the user from logging in without having that port open.