Can't remotely manage some W2K systems

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

I have 3 or 4 systems in my domain that I can't remotely manage. When I look
at them, I see that port 445 is not open. Why wouldn't port 445 be open on a
W2K system joined to a W2K domain? All the appropriate services for remote
management are running.

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

When you say you can't manage them, what does that mean? Can't attach with
RDP? MMCs? Computer Manager?

445 could be blocked for a number of reasons both on the server and your
internetwork... Let us know what you're doing and what error messages you
are getting and we can go from there.

--
Ryan Hanisco
MCSE, MCDBA
FlagShip Integration Services
Chicago, IL

"Chip Burkitt" <Chip Burkitt@discussions.microsoft.com> wrote in message
news632E5C4-FD3E-440D-9F85-96E64B4B054C@microsoft.com...
>I have 3 or 4 systems in my domain that I can't remotely manage. When I
>look
> at them, I see that port 445 is not open. Why wouldn't port 445 be open on
> a
> W2K system joined to a W2K domain? All the appropriate services for remote
> management are running.

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Also, blocking 445 by itself shouldn't cause many issues. Windows NT 5.x
will try to use 445 and the 137, 138, and 139 trio simultaneously. If one
doesn't answer, no big deal it'll use the other. In this case, that would
mean it drops down to SMB over NetBT.


--

Paul Williams

http://www.msresource.net/
http://forums.msresource.net/