Computing.Net > Forums > Windows Server 2003 > Internal Port Scan

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Internal Port Scan

Reply to Message Icon

Name: MicrosoftMAN
Date: October 22, 2004 at 11:09:40 Pacific
OS: Windows Server 2003 for S
CPU/Ram: 1.13GHZ/512MB
Comment:

Is there a way or a program to scan for ports that are blocked or not blocked internally. Like if you wanted to see if port 80 was unblocked and if port 110 was blocked. Not blocked from the outside but blocked from the user from using it. I think the use of a program like this can help make a network safe.

Live by God, and by God only.



Sponsored Link
Ads by Google

Response Number 1
Name: Curt R
Date: October 22, 2004 at 15:05:40 Pacific
Reply:

Yes, there are lots of port scanners available. Just search "port scanner" at www.google.ca and see what you come up with.


0

Response Number 2
Name: iamc
Date: October 22, 2004 at 16:55:52 Pacific
Reply:

I'll go with my usual recommendation: nmap.


0

Response Number 3
Name: MicrosoftMAN
Date: October 22, 2004 at 20:32:50 Pacific
Reply:

So that will work if I was on a machine and I wanted to found out what ports are disabled from me using? For example 6667 is blocked from use on the current machine but 80 is not.

Live by God, and by God only.


0

Response Number 4
Name: iamc
Date: October 22, 2004 at 21:55:51 Pacific
Reply:

What do you mean by "disabled from me using"?

I'm guessing by your example of port 6667 that you're trying to figure out if ports used by P2P filesharing apps are blocked on your network? Those ports might be closed for both incoming and outgoing traffic. They might be closed to incoming setup connections, but open for existing connections. They might be open for outgoing traffic, but closed for incoming traffic. Knowing whether a port is "disable from [you] using" it depends largely on how you intend to use it.

Why don't you post back with exactly what you're trying to accomplish, and I or someone else may be able to help you. The questions you have asked so far don't really mean anything.


0

Response Number 5
Name: MicrosoftMAN
Date: October 23, 2004 at 07:01:11 Pacific
Reply:

I mean similar to what you said.
If I want to check that port 6667 is blocked from users using it on the network. I know its blocked from connections on the outside, but is it blocked say from a single computer on the network just going and connecting to say an IRC server?

Live by God, and by God only.


0

Related Posts

See More



Response Number 6
Name: iamc
Date: October 23, 2004 at 08:44:26 Pacific
Reply:

Like I said, "blocked from users using it" can mean a number of different things. So I ask again, what exactly are you trying to do?


0

Response Number 7
Name: MicrosoftMAN
Date: October 23, 2004 at 08:53:57 Pacific
Reply:

What I mean is, if I open up mIRC and try to connect to say irc.dal.net 6667 it will tell me connection refused even though Dalnet is currently up. So in other words no computer on the network can make a connection on 6667. Now if they open a web browser or anything using port 80 they can get traffic in and out.

Live by God, and by God only.


0

Response Number 8
Name: iamc
Date: October 23, 2004 at 09:10:16 Pacific
Reply:

Now we're getting somewhere :)

You want to know if outgoing connections on port 6667 are blocked. I'd say the easiest way is just to try it. Open up your irc client and try connecting to a few servers. If you can't connect, the port is probably blocked for outgoing traffic. Pretty simple, huh?

Telnet and/or SSH are probably not going to be blocked. You can use either of those to connect to irc via a shell account. Just a tip.


0

Response Number 9
Name: MicrosoftMAN
Date: October 23, 2004 at 10:23:07 Pacific
Reply:

I know how to check 6667. I just wanted to know if you could easily check port 1-65535 for which block outgoing connections.


0

Response Number 10
Name: iamc
Date: October 23, 2004 at 14:39:01 Pacific
Reply:

sigh

why couldn't you just ask that question in the first place?

There isn't really an easy way to do that, no. What you're talking about is basically firewall penetration testing. There are some links to tools here that might be of use to you.


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Windows Server 2003 Forum Home


Sponsored links

Ads by Google


Results for: Internal Port Scan

NAT and Port Forwarding www.computing.net/answers/windows-2003/nat-and-port-forwarding/8723.html

working with firewalls www.computing.net/answers/windows-2003/working-with-firewalls/3733.html

Service Unavailable www.computing.net/answers/windows-2003/service-unavailable/2991.html