October 22, 2020, 07:57:57 AM

Author Topic: Ports & Protocols  (Read 4468 times)

pwharton

  • Member
  • *
  • Posts: 1
Ports & Protocols
« on: August 20, 2015, 03:33:46 PM »
I'm trying to scan another network with Newt that is connected through an established router-to-router IPsec VPN Tunnel. I can see all of the properties on my local side of the VPN but can only see limited information on the remote side.

What Ports and Protocols does Newt use when it scans the network?  I suspect that these Ports & Protocols need to be opened in the Firewall to allow Newt to function correctly.

Thank you.


Pete.

Komodo Support

  • Administrator
  • Member
  • *****
  • Posts: 2698
  • Dayton, Ohio, USA
    • Komodo Laboratories LLC
Re: Ports & Protocols
« Reply #1 on: August 20, 2015, 07:00:02 PM »
Hi there.  NEWT currently uses basic Windows ports and protocols.  So you'd at least want 137 UDP, 139 and/or 445 TCP open.  You also want the remote PC to be pingable.  If we're talking Windows Firewall, you should just be able to enable the "File & Printer Sharing" exception to enable those ports.  In addition, to get a full scan, you'll need ADMIN$ share access.  Those are the only requirements.

So if you can get to the remote PC using "\\PCName" or "\\IPAddress" from Windows Explorer, that's the first step.  Then if you can get to "\\PCName (or IP)\ADMIN$", you should be able to get a full scan.