Brand new Exchange Server

[birddseedd]

to end the topic.


Everything works the way it is supposed to work. i can change ports on the protocols and they work. jsut need to use separate ports.
i cannot send or receive email because of ports being blocked. this is not hard to get around. my mail being recieved and sent can be easially ported through my cousins server.

unovercomable problem. smtp, pop3, imap protocols can have custom ports. Exchange cannot. this sucks, no server for me.

pointed mx records to cousins server. he hosts.

 

[Nocturnal]

I am a student and I have Windows 2003 Enterprise Edition free from the Microsoft Software Alliance through my school.

 

[birddseedd]

What is your point?

 

[RebateMonger]

Microsoft: How to change SMTP port 25 to another port on Exchange 2003
You can change both the SMTP listening port and the outgoing port.

It obviously gets complicated, though, since everybody else's mail servers are talking on Port 25. You have to have another, external, server listening on Port 25 and relaying email for you on a non-standard Port.

 

[birddseedd]

Ill read it over just to know everything exactly. but changing the smtp port doesent change the port that exchange works on. i believe its 443 and 80.

exchange uses the http protocol to transfer data. not like pop3, imap at all.

they could have made it so the same data can go across another port number, same as other protocols. but they didnt.

 

[RebateMonger]

You are mixing the SMTP (server) protocol with the client protocol.

Exchange can use several methods to communicate with the email client (Outlook or Outlook Mobile). In the local network, Outlook will begin communication over TCP Port 135 (RPC) and then change to a higher number port. It can also use TCP Port 443 using Outlook Web Access.

From the Internet, it can use OWA, a VPN connection using RPC on Port 135, or RPC over HTTPS on Port 443.

It's uncommon for an ISP to block TCP Port 443 communication or VPN communication. Blocking of TCP Port 135 is almost universal nowadays, a result of the MSBlaster worm.

Under optimum conditions (a business Internet account with static IP), it's pretty easy to get Exchange fully functional. Adding Port limitations and dynamic IPs makes it much tougher.

If I was in your shoes, I'd get a hosted Exchange account. Those are available for as little as $6-$7 dollars a month and $10-$13 a month for high-end hosts. That's cheaper than powering a 24/7 Server and maintaining a business Internet account.

 

[birddseedd]

when i try to telnet server address 135 or 443 it will not connect.
ports are forwarded correctly

i could get a business account for 15 a month more. but dont want to do it.

my cousin is just going to host my email. so i still get exchange. though im not doing it myself. if i need to do the other stuff i wanted, ill just use ftp.

 

[Tarrant64]

On a few of the posts where people had a "legal" discussion about how one obtains Exchange Server at a low price or through student discount...

My community college that I go to offers Exchange Server 2000(enterprise), 2003(enterprise), 2007(standard) editions free for download(or $shipping for actually media). It also has all versions of SQL Server available as well. The usual Windows XP and Windows Vista for free like at amost colleges(or at least no more than $20).

When I was at the University I didn't have to pay more than $200 for pretty much anything.

 

[Nothinman]

but changing the smtp port doesent change the port that exchange works on. i believe its 443 and 80.

80 and 443 are HTTP and HTTPS, respectively. Whether they're used for more than OWA I really don't know, but it's likely that your ISP blocks them.

 

[birddseedd]

yep, their as blocked as a pet crow. unfortunately because you are not able to change the ports that exchange works on. it wont work for less than 15 a month(commercial isp account). i got other protocols to work, imap and pop3. once it was configured correctly they worked seamlessly.

my cousin is hosting my email for me. i still get exchange, though i would still like to host it myself. ah well.
i tried