Hi,

I'm trying to implement MBSA and SUS into my current environment. Here are
my issues that are causing problem. What I'm trying to do is scan remote
computers w/ MBSA and update them w/ approved updates through SUS. What is
making this hard is that the computers are behind a router. So they don't
get individual ip address. I normally access a specific computer w/ port
forwarding. So what I'm wondering is if I'm able to scan those computers w/
MBSA and how? Normally MBSA uses ports 139 & 445, but because I'm using port
forwarding, how can I scan each individual computer and get a report back?

And after I get that figured out, then I'm going to tackle integrating SUS
with MBSA as well. But I figured that I'd just get MBSA working first...but
using SUS in conjunction is the overall goal.

Any help or suggestions is greatly appreciated.

Aloha,
Steven

Re: Scanning remote pc's w/ MBSA & SUS... by David

David
Sun Oct 03 21:49:11 CDT 2004

This is an IIS newsgroup. My first suggestion would be to post this to a
newsgroup related to your issue.

The computers behind the router should still have IP addresses. The question
is whether they have private IPs or public IPs that are visible beyond the
router. I think I can assume they're not visible. NAT maybe?

Is there a reason you cannot scan the computers from the private side of the
router? I supposed you could also configure the port forwarding so the ports
needed by MBSA get directed to whatever server you're scanning.


"Steven808" <Steven808@discussions.microsoft.com> wrote in message
news:19EA3707-A105-4E8A-B3A9-11518F68F082@microsoft.com...
> Hi,
>
> I'm trying to implement MBSA and SUS into my current environment. Here
> are
> my issues that are causing problem. What I'm trying to do is scan remote
> computers w/ MBSA and update them w/ approved updates through SUS. What
> is
> making this hard is that the computers are behind a router. So they don't
> get individual ip address. I normally access a specific computer w/ port
> forwarding. So what I'm wondering is if I'm able to scan those computers
> w/
> MBSA and how? Normally MBSA uses ports 139 & 445, but because I'm using
> port
> forwarding, how can I scan each individual computer and get a report back?
>
> And after I get that figured out, then I'm going to tackle integrating SUS
> with MBSA as well. But I figured that I'd just get MBSA working
> first...but
> using SUS in conjunction is the overall goal.
>
> Any help or suggestions is greatly appreciated.
>
> Aloha,
> Steven



Re: Scanning remote pc's w/ MBSA & SUS... by Steven808

Steven808
Sun Oct 03 22:03:01 CDT 2004

Sorry about the post in the IIS, I was orginally posting in regards to SUS,
so I appologize for that. But in response to your post, Yes the computers do
have ip addresses, however they're private, like you pointed out.

I could scan the computers from the private side, but that would negate what
I'm trying to do....which is scan computers that are behind a router from one
pc.

The problem w/ port forwarding is that MBSA scans through ports 139 & 445,
but if their are multiple computers behind the router, the router doesn't
know what computer to forward port 139/445 to. :(

Thanks for your info...

"David Boyer" wrote:

> This is an IIS newsgroup. My first suggestion would be to post this to a
> newsgroup related to your issue.
>
> The computers behind the router should still have IP addresses. The question
> is whether they have private IPs or public IPs that are visible beyond the
> router. I think I can assume they're not visible. NAT maybe?
>
> Is there a reason you cannot scan the computers from the private side of the
> router? I supposed you could also configure the port forwarding so the ports
> needed by MBSA get directed to whatever server you're scanning.
>
>
> "Steven808" <Steven808@discussions.microsoft.com> wrote in message
> news:19EA3707-A105-4E8A-B3A9-11518F68F082@microsoft.com...
> > Hi,
> >
> > I'm trying to implement MBSA and SUS into my current environment. Here
> > are
> > my issues that are causing problem. What I'm trying to do is scan remote
> > computers w/ MBSA and update them w/ approved updates through SUS. What
> > is
> > making this hard is that the computers are behind a router. So they don't
> > get individual ip address. I normally access a specific computer w/ port
> > forwarding. So what I'm wondering is if I'm able to scan those computers
> > w/
> > MBSA and how? Normally MBSA uses ports 139 & 445, but because I'm using
> > port
> > forwarding, how can I scan each individual computer and get a report back?
> >
> > And after I get that figured out, then I'm going to tackle integrating SUS
> > with MBSA as well. But I figured that I'd just get MBSA working
> > first...but
> > using SUS in conjunction is the overall goal.
> >
> > Any help or suggestions is greatly appreciated.
> >
> > Aloha,
> > Steven
>
>
>

Re: Scanning remote pc's w/ MBSA & SUS... by Bojidar

Bojidar
Mon Oct 04 04:39:20 CDT 2004

You can switch the sides for this computer only. Put one reversed NAT on the
router and set it as default gateway for your external computer from where
you will scan. Configuration must be to set these private IP adresses as
external ones.

Bojidar Alexandrov


"Steven808" <Steven808@discussions.microsoft.com> wrote in message
news:646239F5-94E3-4539-93B2-0BBBBB7DE108@microsoft.com...
> Sorry about the post in the IIS, I was orginally posting in regards to
SUS,
> so I appologize for that. But in response to your post, Yes the computers
do
> have ip addresses, however they're private, like you pointed out.
>
> I could scan the computers from the private side, but that would negate
what
> I'm trying to do....which is scan computers that are behind a router from
one
> pc.
>
> The problem w/ port forwarding is that MBSA scans through ports 139 & 445,
> but if their are multiple computers behind the router, the router doesn't
> know what computer to forward port 139/445 to. :(
>
> Thanks for your info...
>
> "David Boyer" wrote:
>
> > This is an IIS newsgroup. My first suggestion would be to post this to a
> > newsgroup related to your issue.
> >
> > The computers behind the router should still have IP addresses. The
question
> > is whether they have private IPs or public IPs that are visible beyond
the
> > router. I think I can assume they're not visible. NAT maybe?
> >
> > Is there a reason you cannot scan the computers from the private side of
the
> > router? I supposed you could also configure the port forwarding so the
ports
> > needed by MBSA get directed to whatever server you're scanning.
> >
> >
> > "Steven808" <Steven808@discussions.microsoft.com> wrote in message
> > news:19EA3707-A105-4E8A-B3A9-11518F68F082@microsoft.com...
> > > Hi,
> > >
> > > I'm trying to implement MBSA and SUS into my current environment.
Here
> > > are
> > > my issues that are causing problem. What I'm trying to do is scan
remote
> > > computers w/ MBSA and update them w/ approved updates through SUS.
What
> > > is
> > > making this hard is that the computers are behind a router. So they
don't
> > > get individual ip address. I normally access a specific computer w/
port
> > > forwarding. So what I'm wondering is if I'm able to scan those
computers
> > > w/
> > > MBSA and how? Normally MBSA uses ports 139 & 445, but because I'm
using
> > > port
> > > forwarding, how can I scan each individual computer and get a report
back?
> > >
> > > And after I get that figured out, then I'm going to tackle integrating
SUS
> > > with MBSA as well. But I figured that I'd just get MBSA working
> > > first...but
> > > using SUS in conjunction is the overall goal.
> > >
> > > Any help or suggestions is greatly appreciated.
> > >
> > > Aloha,
> > > Steven
> >
> >
> >



Re: Scanning remote pc's w/ MBSA & SUS... by Steven808

Steven808
Wed Oct 06 06:45:01 CDT 2004

Thanks for that suggestion. I am not familar with NAT, but I think I
understand the concept and it sounds like something that might work. :) If
youv'e got any good NAT sites that I could read up on, that would be great.

Thanks,
Steven

"Bojidar Alexandrov" wrote:

> You can switch the sides for this computer only. Put one reversed NAT on the
> router and set it as default gateway for your external computer from where
> you will scan. Configuration must be to set these private IP adresses as
> external ones.
>
> Bojidar Alexandrov
>
>
> "Steven808" <Steven808@discussions.microsoft.com> wrote in message
> news:646239F5-94E3-4539-93B2-0BBBBB7DE108@microsoft.com...
> > Sorry about the post in the IIS, I was orginally posting in regards to
> SUS,
> > so I appologize for that. But in response to your post, Yes the computers
> do
> > have ip addresses, however they're private, like you pointed out.
> >
> > I could scan the computers from the private side, but that would negate
> what
> > I'm trying to do....which is scan computers that are behind a router from
> one
> > pc.
> >
> > The problem w/ port forwarding is that MBSA scans through ports 139 & 445,
> > but if their are multiple computers behind the router, the router doesn't
> > know what computer to forward port 139/445 to. :(
> >
> > Thanks for your info...
> >
> > "David Boyer" wrote:
> >
> > > This is an IIS newsgroup. My first suggestion would be to post this to a
> > > newsgroup related to your issue.
> > >
> > > The computers behind the router should still have IP addresses. The
> question
> > > is whether they have private IPs or public IPs that are visible beyond
> the
> > > router. I think I can assume they're not visible. NAT maybe?
> > >
> > > Is there a reason you cannot scan the computers from the private side of
> the
> > > router? I supposed you could also configure the port forwarding so the
> ports
> > > needed by MBSA get directed to whatever server you're scanning.
> > >
> > >
> > > "Steven808" <Steven808@discussions.microsoft.com> wrote in message
> > > news:19EA3707-A105-4E8A-B3A9-11518F68F082@microsoft.com...
> > > > Hi,
> > > >
> > > > I'm trying to implement MBSA and SUS into my current environment.
> Here
> > > > are
> > > > my issues that are causing problem. What I'm trying to do is scan
> remote
> > > > computers w/ MBSA and update them w/ approved updates through SUS.
> What
> > > > is
> > > > making this hard is that the computers are behind a router. So they
> don't
> > > > get individual ip address. I normally access a specific computer w/
> port
> > > > forwarding. So what I'm wondering is if I'm able to scan those
> computers
> > > > w/
> > > > MBSA and how? Normally MBSA uses ports 139 & 445, but because I'm
> using
> > > > port
> > > > forwarding, how can I scan each individual computer and get a report
> back?
> > > >
> > > > And after I get that figured out, then I'm going to tackle integrating
> SUS
> > > > with MBSA as well. But I figured that I'd just get MBSA working
> > > > first...but
> > > > using SUS in conjunction is the overall goal.
> > > >
> > > > Any help or suggestions is greatly appreciated.
> > > >
> > > > Aloha,
> > > > Steven
> > >
> > >
> > >
>
>
>