Hello all.
I used "AutoScan Network" tool for Map all my network and it worked very nice but when I change my network and define VLAN for each department, "AutoScan Network" can't worked properly. I know that Nmap "Ping Sweep" can do it very well but it need more time to detect OS and other useful information. I found "netdiscover" but it not worked properly and have some errors. Can you show me other tools like "AutoScan Network" ?

I use Debian 7 x64.

Thank you.

AGAIN

• What do you mean by "can't worked properly"?
• Why is it a problem that nmap takes more time?
• What about netdiscover "not worked properly and have some errors"??? WHAT errors? When?

If you configured your network and VLANS, then why don't you run your autoscan from a span port on your central switch? Why is it a problem that nmap takes more time (you're not going to do this very often).

As you've been told many, MANY times, unless you're going to tell us what the error(s)/problem(s)/goal(s) actually ARE, there is no point in posting a question. We have to ask you things again and again, pretty much every time you ask a question. You have NEVER followed up in many threads AT ALL, and never post a solution.

I use "Autoscan Network" with default options and when I start it, It use 127.0.0.1 address and not find any Live host on my network.
Nmap can detect Live host very fast and good but for detect OS it need more time because of my client Antivirus and Firewall.
Netdiscover, Can't detect live hosts and when I ping an IP, it is live but Netdiscover not detect it and show me that scanning finished with 0 host live.

How can I solve it?

And in your first post, you said that you DID use it successfully, and it worked fine until you created VLANS. Now you're saying it doesn't find anything. Which is it??? Again, as with most of your threads, you are posting incomplete/conflicting information.
Right...and again, we go back to the question you were asked and that is "Why is that a problem???" If it does what you want, why is the time an issue?
Did you not read or understand the first reply?? AGAIN:

• If you configured your network and VLANS, then why don't you run your autoscan from a span port on your central switch?
• Why is it a problem that nmap takes a while?

And you don't mention any firewalls or what's between you and the mapping system, if you've checked them, or what you've done. AGAIN: you need to provide details. If you're the network administrator, you should easily know the answers to these things, and know how to check and modify them if you need to.

It is my question and I don't know why "AutoScan" can't work after VLAN.
As I said, Nmap need more time to detect OS because of Firewall and Antivirus.

How can I run autoscan from a span port on my central switch?

If you're the network adminstrator and don't know why this is happening, there's FAR too much for anyone here to try to explain to you. Please ask someone who has experience and knowledge of networking to work with you.
Right, so PAY ATTENTION: You were then asked WHY IS THIS A PROBLEM??? You STILL haven't answered that. If nmap is doing what you want, WHY IS IT A PROBLEM THAT IT TAKES LONGER???? What are you trying to accomplish that needs to be done in that length of time?? Do you not understand the question???
If you're the network administrator, then you should already KNOW how to set up a span port. And you run autoscan the same way you ALWAYS run it, but VERY OBVIOUSLY have that machine PLUGGED IN TO THE SPAN PORT.

I guess Span port is for Cisco and I have not any Cisco device.I'm a network administrator but I'm not in Hardware department thus I don't know anything about routers and switches configuration. As I said, Autoscan worked very nice and after upgrade the network configuration, it can't detect any host