I have my server set up with the smtp daemon running on port 125, and assp listening on ports 25 and 26, and forwarding to port 125 if the mail passes. This setup has been working for months and months. Already today I've received several emails.
I just attempted to send an email, however, and thunderbird could not connect to port 26. (I use an alternate port because my ISP blocks port 25 except to their mail servers)
So I thought that assp had stopped running. Attempted to go to myip:55555, but the page would not load. Now I really thought assp was broken. SSH'd into server and was able to telnet to localhost, port 26 without an issue. Was also able to lynx [url] without an issue.
Since I'm able to log in to all of these weird ports via SSH but not from my local computer, I'm apt to think that they are blocking the ports (for some reason).
Is there any way I can test this theory? Nothing has changed on my side firewall-wise, and the poor girl at the ISP company didn't even know what a port was. I would like to be 100% sure before I give them another call demanding to speak to someone higher up...
I'm behind the firewall on a public computer and all online port scan tests I've tried show that ALL ports on a computer I'm using are closed. Is this possible? I've been previously succesfully uploaded some files through cpanelproxy.net to get access to my site, for which opened port 80 was needed.
let's say I'm part of a LAN and i get my public IP through a PPPoE but i also have a wireless router and another station on which I wish to have linux. On that linux machine I will have anther public IP which is not from the same class.
What to do in order to world wide see my server machine(the one with linux and IP not from the same class)
Do SMTP servers by default use port 25 for receiving mail from another SMTP server? Are there any other receiving ports an SMTP server would be listening on by default?
My question is, a server I will be setting up is going to be behind a firewall that blocks outgoing connections *to* port 25. Is there going to be any way around this that is workable besides opening the port?
I am attempting to route traffic through some various open ports on my Win2k Server. I have ports 8001-8005 open for a few projects, and I would like to have the traffic from [url]site 1, localhost:8002 goto site 2, etc.
How can I set this up using IIS and the IIS Manager?
I have used a tool called Net Tools to scan ports on my various servers to determine ports are open in the firewall through my host.
For around a decade, this tool has been accurate to determine what ports are open/closed.
I have used this tool to accurately find issues with the firewall with current host (dedicated server). The network admin says that net tools should not be trusted and even though the software claims the ports are open, they are not open.
I explained that less than a month ago, this software reflected that these ports should closed were reflected accurately as closed by scanning the ports.
Code: Address Scanned: xx.xx.xx.xx
Scan Started at 10/27/2007 2:08:00 PM Scan Finished at 10/27/2007 2:18:03 PM
Ports Scanned: 1 To 4000
Total Ports Found Open: 3794
Current Ports Found Open: Port: 00004 Port: 00005 Port: 00009 Port: 00026 Port: 00044 Port: 00076 Port: 00083 Port: 00088 ... What are the ABSOLUTE best tools/ways that I can confirm that the ports are truly not accessible?
Knowing that Port 1433 is one of the most attacked ports, I am thinking whether I should just change the default port of my new MS SQL 2005 installation, but issue is, what will be the disadvantages to users if I do so?