Elijah Savage III wrote:
> this came about they are using this program to update the
> clients I
> suppose or at least I was told and clients on the same subnet
> they can
> go out and discover those clients, but any clients not on the
> same
> subnet that has to cross the router the discover util
directly with this rpc call.
What a mess, if anyone is interested I will keep you up to date on the
fix for this product.
-Original Message-
From: Priscilla Oppenheimer [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, August 21, 2002 12:17 AM
To: [EMAIL PROTECTED]
Subject: Re: Broadcast ports
Chuck's Long Road wrote:
>
> ""Priscilla Oppenheimer"" wrote in
> message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > No wonder you are a bit lost. They aren't using our
> networking terminology
> > quite correctly. There's no such thing as a broadcast port
> and hence you
> > can't open
""Priscilla Oppenheimer"" wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> No wonder you are a bit lost. They aren't using our networking terminology
> quite correctly. There's no such thing as a broadcast port and hence you
> can't open it. Perhaps what they mean is that you need
No wonder you are a bit lost. They aren't using our networking terminology
quite correctly. There's no such thing as a broadcast port and hence you
can't open it. Perhaps what they mean is that you need to get the router to
forward the IP broadcasts to UDP port 42508. Do this with an ip
helper-add
Ok I am a little lost here but our NT team has rolled out this product.
http://files.ruca.ua.ac.be/pub/security/virus/ca/rolloutig.pdf
Everything is working but the server can't see the clients because in
the document above it states that router ports need to be open to past
these broadcast,
6 matches
Mail list logo
