Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
All Ports are in Stealth Mode...
- Thread starter Menx
- Start date
Rather vague question but:
A port will not be acsessable unless there is a service utilizing it, or you have a firewall in place. XP has a firewall in-built you may wish to check, under network properties,
Don't put too much faith in Shields Up either, I have had varying results from the same computer within only a few minutes. It also only checks about 8 ports out of the thousands you're computer is running, so if you want peace of mind make use of a firewall on your machine.
A port will not be acsessable unless there is a service utilizing it, or you have a firewall in place. XP has a firewall in-built you may wish to check, under network properties,
Don't put too much faith in Shields Up either, I have had varying results from the same computer within only a few minutes. It also only checks about 8 ports out of the thousands you're computer is running, so if you want peace of mind make use of a firewall on your machine.
All ports Stealth just means that Shields Up did not get a response from the requests that were sent your ports. This can happen for numerous reasons, but is very common when you are using NAT.
If you are having trouble with XP, and not NT, it is likely that you have the XP firewall running on that interface. Try taking it down and then see what happens. If you can then access what you need, you will have to customize your XP firewall rules.
pansophic
If you are having trouble with XP, and not NT, it is likely that you have the XP firewall running on that interface. Try taking it down and then see what happens. If you can then access what you need, you will have to customize your XP firewall rules.
pansophic
- Thread starter
- #4
Silly me...I should have mentioned that ICF in XP is turned off too.
i 4get, but i've used another service b4, and it also says all my ports are on stealth.
only firewall i'm running is McAfee Firewall, and i've told it to have all those ports TCIP and UDP opened..
i 4get, but i've used another service b4, and it also says all my ports are on stealth.
only firewall i'm running is McAfee Firewall, and i've told it to have all those ports TCIP and UDP opened..
Menx,
Aight bud.. Never trust any product 100% even if u spend couple grand into it. I have no experience with the product your using but this advise may help you..
Go and get a piece of port scanning software (stay off the "questionable" sites) as you dont know what may have done with it. I personnally use Nmap, and nmap for NT on my laptop. Now scan your box. I suggest from a different machine, or ask a friend to scan it for you.. If in doubt hit me up and i will help.
Take a look at which ports are open and this is where the learning begins =) Nmap for example will out put open ports and their common usage.. But to make sure go to the command prompt and type the following
"telnet localhost <port number>"
With out the "<>". What your doing is connecting to your own box and it will blurt out what that port is being used by. If you see something like "h4xx0rd <insert lame script kid crap> " Then you got issues my friend... =D
Aight bud.. Never trust any product 100% even if u spend couple grand into it. I have no experience with the product your using but this advise may help you..
Go and get a piece of port scanning software (stay off the "questionable" sites) as you dont know what may have done with it. I personnally use Nmap, and nmap for NT on my laptop. Now scan your box. I suggest from a different machine, or ask a friend to scan it for you.. If in doubt hit me up and i will help.
Take a look at which ports are open and this is where the learning begins =) Nmap for example will out put open ports and their common usage.. But to make sure go to the command prompt and type the following
"telnet localhost <port number>"
With out the "<>". What your doing is connecting to your own box and it will blurt out what that port is being used by. If you see something like "h4xx0rd <insert lame script kid crap> " Then you got issues my friend... =D
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question