+ 0 Votes exchange rediresction problems to but have a good ideal on how to solve learoy.ellismoore 6 years ago This is what iam trying to do will keep you updated on my progress. I have a win 2003 server ent and a linksys 300n router. i used dyndsn.org as it was suggested by linksys. check list. is the domain name on the server, the same as the one you registered with DYNDNS e.g. yourdnslink.co.uk (domain registered)and server.yourdnslink.co.uk FQDN of server) domain in server list yourdnslink.co.uk Right click my computer and propertise, computer name and check here. also is you server static IP'ed which you done by taking an IP address from you DHCP range on you router? this gives you a static IP for your server from a range already excisting on your router, also is you ISP IP static? check price as i might be cheap enough to purchase. mine is i paid ?5 to bulldog is you domain name with dyndns as your dns records are held be another domain name registrar and makes things a little complicated as dyndns have to contact them and get the dns records to add to there dns servers. just a few thing to think about. I installed server with all dns setting e.g. NS, SOA, MX, etc all fine. exchange works fine internally (have you check OWA internally (http://your exch server ip address or domain name/exchange and have you configured all your outlook 2003 with exchange account for testing) I setup an account with dyndns with custom dns, mailhop relay and domain name registration, making sure all thing link back to dyndns and there dns servers. got mine confirmation email yeasterday so i know there dns servers and doing there job but on my end something is missing and i am stuck like you. i know the router setting need to be configured for port-forwarding to port 25 as as this links any request coming into the DG and then gets redirects to the IP and Port as specified. ISP DG = 22.214.171.124 Srver = 192.168.10.10 DG = 126.96.36.199 router forwarding = 192.168.10.10 port 25 tick box next to option to confirm i hope this help keep me post and i'll do the same + 0 Votes IS/IT Management (CIO, CTO) ? The Listed 'G MAN' 6 years ago Say no more - I am glad you solved your problem. + 0 Votes Maybe another MX record simplebob 6 years ago Putting another MX record to point to 192.168.1.105 or what ever the exchange server's ip is. Just a thought. + 0 Votes don't use the router's DDNS utility CG IT 6 years ago download the client utility from dyndns.org and use that. see FAQ on dyndns.org web site for their recommendations, which is to not use the router's DDNS utility. + 0 Votes Trainsignal.com earlscott3 6 years ago Thedy have a two CD video training that shows you how to setup Exchange from beginning to end. + 0 Votes Your Elorean Technology Right? The Listed 'G MAN' 6 years ago So you tell me? + 0 Votes contacting my ISP resolved it. learoy.ellismoore 6 years ago I managed to get is all sort. Needed to contact my ISP and inform them of my ip for exchange server. Thank everyone for there help and understanding. That reply was a bit crazy with the spelling lol. On the fly typing and rushing into meeting and crazy deadines don?t help but that's the price of IT for you. P.S. always use word for spell checking.