RE: Netlogon Port 445
- From: "Jay J. Mobley" <jmobley@xxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Tue, 12 Feb 2002 11:21:13 -0800
Perhaps stopping the server service????
Im betting there is a service you can stop that will achieve this for
you.
And stopping the service is prolly gonna be better than changing the
port anyway (because all your other servers are still going to try to
contact your netlogon service on the original port)
anybody .... anybody.
Bueler..... Bueler.....
-Jay
-----Original Message-----
From: Lippman, Michael [mailto:Michael.Lippman@xxxxxxxxxxxxxxxx]
Sent: Tuesday, February 12, 2002 10:57 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Netlogon Port 445
http://www.ISAserver.org
It scrolls so fast on my screen I can't tell. I think you are
definitely pointing me in the right direction. Where do you think I
could change the port that Netlogon is listening. (Registry?)
MRL
-----Original Message-----
From: Jay J. Mobley [mailto:jmobley@xxxxxxxxxx]
Sent: Tuesday, February 12, 2002 1:41 PM
To: [ISAserver.org Discussion List]
Subject: [isalist] RE: Netlogon Port 445
http://www.ISAserver.org
Yes.. I have an idea.
or rather a guess...
I think that your NETLOGON service on your ISA server must already be
listening on port 445 on all IP's for its self
(try a NETSTAT -na and look for something that says 0.0.0.0:445
LISTENING)
You prolly need to set that service to either not listen at all, or
listen on an alternate port, and then the publising rule will be able to
pick up that port and do what you want with it.
-Jay Mobley
-----Original Message-----
From: Michael Lippman [mailto:Michael.Lippman@xxxxxxxxxxxxxxxx]
Sent: Tuesday, February 12, 2002 10:08 AM
To: [ISAserver.org Discussion List]
Subject: [isalist] Netlogon Port 445
http://www.ISAserver.org
I am trying to setup a front end exchange server. I have all the custom
definitions completed except for Netlogon(TCP/445) Whenever I enable it
I
get a warning in the event log (14163) that the map failed because the
port on the external interface is being used by another application.
The
firewall service failed to bind etc. . . . .
Anyone have any ideas I would appreciate it.
Thanks,
MRL
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jmobley@xxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
Michael.Lippman@xxxxxxxxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
------------------------------------------------------
You are currently subscribed to this ISAserver.org Discussion List as:
jmobley@xxxxxxxxxx
To unsubscribe send a blank email to $subst('Email.Unsub')
Other related posts:
