|
exchange
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
domain/ip adreswe used to connect OWA through our https://domianname.org/exchange. Our
website was hosted in our own server, but we moved it out with another company. Now when we enter https://domainname.org/exchange it doesn't work. If I enter https://ipaddress/exchange it works, but I don't want to use the IP address. Where exactly I have to make changes? In our exchange server?? Or the compnay that's hosting our website now? If I have to make a change in our server, please be specific exactly where... Thank you. Sounds like you have a DNS problem.
-- Show quoteHide quoteEd Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "nl" <n*@discussions.microsoft.com> wrote in message news:10C5073C-F268-457D-8E7A-27C34E98A865@microsoft.com... > we used to connect OWA through our https://domianname.org/exchange. Our > website was hosted in our own server, but we moved it out with another > company. > Now when we enter https://domainname.org/exchange it doesn't work. If I > enter https://ipaddress/exchange it works, but I don't want to use the IP > address. Where exactly I have to make changes? In our exchange server?? > Or > the compnay that's hosting our website now? If I have to make a change in > our > server, please be specific exactly where... > > Thank you. Hi there, sounds like you need to change your dns record of domainname.org to
th new ip address that you an use to connect to your new OWA site. Presumably you have a dns A record along the lines or mail.domainname.org that you use when connecting to OWA with the added /exchange component on the end (the /exchange is nothing to do with dns, dns purele resolves names to ip's , or vice versa). Hope that helps James. Show quoteHide quote "nl" wrote: > we used to connect OWA through our https://domianname.org/exchange. Our > website was hosted in our own server, but we moved it out with another > company. > Now when we enter https://domainname.org/exchange it doesn't work. If I > enter https://ipaddress/exchange it works, but I don't want to use the IP > address. Where exactly I have to make changes? In our exchange server?? Or > the compnay that's hosting our website now? If I have to make a change in our > server, please be specific exactly where... > > Thank you. nl wrote:
> we used to connect OWA through our https://domianname.org/exchange. Our You likely need to update the DNS on your nameservers to point > website was hosted in our own server, but we moved it out with another > company. > Now when we enter https://domainname.org/exchange it doesn't work. If I > enter https://ipaddress/exchange it works, but I don't want to use the IP > address. Where exactly I have to make changes? In our exchange server?? Or > the compnay that's hosting our website now? If I have to make a change in our > server, please be specific exactly where... > > Thank you. domainname.org to the new IP address. If you ping domainname.org at a command prompt and get a different IP address than the one you are using for OWA access, that's the problem. Venger I did ping domainname.org and got a very different IP address than the one
that we are using now; where did that come from? The website was in our old server; our exchange was and still is in our current server. All we did was move the website, but the exchange server is still in the same place in our server... Show quoteHide quote "Venger" wrote: > nl wrote: > > we used to connect OWA through our https://domianname.org/exchange. Our > > website was hosted in our own server, but we moved it out with another > > company. > > Now when we enter https://domainname.org/exchange it doesn't work. If I > > enter https://ipaddress/exchange it works, but I don't want to use the IP > > address. Where exactly I have to make changes? In our exchange server?? Or > > the compnay that's hosting our website now? If I have to make a change in our > > server, please be specific exactly where... > > > > Thank you. > > You likely need to update the DNS on your nameservers to point > domainname.org to the new IP address. > > If you ping domainname.org at a command prompt and get a different IP > address than the one you are using for OWA access, that's the problem. > > Venger > NSLOOKUP is your friend.
-- Show quoteHide quoteEd Crowley MVP "There are seldom good technological solutions to behavioral problems." .. "nl" <n*@discussions.microsoft.com> wrote in message news:56CF3269-56EA-45FF-818E-4ACB5D3E3310@microsoft.com... >I did ping domainname.org and got a very different IP address than the one > that we are using now; where did that come from? The website was in our > old > server; our exchange was and still is in our current server. All we did > was > move the website, but the exchange server is still in the same place in > our > server... > > "Venger" wrote: > >> nl wrote: >> > we used to connect OWA through our https://domianname.org/exchange. Our >> > website was hosted in our own server, but we moved it out with another >> > company. >> > Now when we enter https://domainname.org/exchange it doesn't work. If >> > I >> > enter https://ipaddress/exchange it works, but I don't want to use the >> > IP >> > address. Where exactly I have to make changes? In our exchange >> > server?? Or >> > the compnay that's hosting our website now? If I have to make a change >> > in our >> > server, please be specific exactly where... >> > >> > Thank you. >> >> You likely need to update the DNS on your nameservers to point >> domainname.org to the new IP address. >> >> If you ping domainname.org at a command prompt and get a different IP >> address than the one you are using for OWA access, that's the problem. >> >> Venger >> Thank to all and speciallly this last one. I got what I needed and it's
working fine.:) Show quoteHide quote "Ed Crowley [MVP]" wrote: > NSLOOKUP is your friend. > -- > Ed Crowley MVP > "There are seldom good technological solutions to behavioral problems." > .. > > "nl" <n*@discussions.microsoft.com> wrote in message > news:56CF3269-56EA-45FF-818E-4ACB5D3E3310@microsoft.com... > >I did ping domainname.org and got a very different IP address than the one > > that we are using now; where did that come from? The website was in our > > old > > server; our exchange was and still is in our current server. All we did > > was > > move the website, but the exchange server is still in the same place in > > our > > server... > > > > "Venger" wrote: > > > >> nl wrote: > >> > we used to connect OWA through our https://domianname.org/exchange. Our > >> > website was hosted in our own server, but we moved it out with another > >> > company. > >> > Now when we enter https://domainname.org/exchange it doesn't work. If > >> > I > >> > enter https://ipaddress/exchange it works, but I don't want to use the > >> > IP > >> > address. Where exactly I have to make changes? In our exchange > >> > server?? Or > >> > the compnay that's hosting our website now? If I have to make a change > >> > in our > >> > server, please be specific exactly where... > >> > > >> > Thank you. > >> > >> You likely need to update the DNS on your nameservers to point > >> domainname.org to the new IP address. > >> > >> If you ping domainname.org at a command prompt and get a different IP > >> address than the one you are using for OWA access, that's the problem. > >> > >> Venger > >> > > nl <n*@discussions.microsoft.com> wrote:
> we used to connect OWA through our https://domianname.org/exchange. Hi - I believe I replied to your identical post in another newsgroup. In the > Our website was hosted in our own server, but we moved it out with > another company. > Now when we enter https://domainname.org/exchange it doesn't work. > If I enter https://ipaddress/exchange it works, but I don't want to > use the IP address. Where exactly I have to make changes? In our > exchange server?? Or the compnay that's hosting our website now? If > I have to make a change in our server, please be specific exactly > where... > > Thank you. future, please don't multipost - if you need to post to multiple groups, it's best to crosspost instead, by posting a single message to a handful of relevant groups (separate the NG names with commas) so that everyone can follow the thread. Multiposting wastes everyone's time, including yours, and may lead to your actually getting *less* help rather than more. See http://www.blakjak.demon.co.uk/mul_crss.htm
Spam from me to me?
Exchange accept mail from two domain names Disclaimer EventSink Trigger How to enable active sync with ssl feature in Exchnage 2003 #550 5.2.0 STOREDRV.Deliver Error Calendar items can't be forwarded Event 1221 Exchange 2003 DR Testing Force a 2007 CA to use a particular GC fail to move Exchange databases to a Windows Storage server 2003 |
|||||||||||||||||||||||