I have a SBS2003 and use the outlook web access. All has been working well.
I changed my ISP and now I cant connect to the to outlook web access. Using
the new IP address for my new ISP my vpn still works.
Any ideas whats happening?
Thanks
I have a SBS2003 and use the outlook web access. All has been working well.
I changed my ISP and now I cant connect to the to outlook web access. Using
the new IP address for my new ISP my vpn still works.
Any ideas whats happening?
Thanks
Hi Mark:
The answer may be in the way you address OWA? When you changed the ISP did
you also change the Public DNS records to reflect the new public IP address
of your network edge device?
--
Larry
Please post the resolution to your
issue so that others may benefit.
Get a Health Check for SBS at:
www.sbsbpa.com
"Mark" <nop@newsgroup> wrote in message
news:KUslm.650412$jp1.346260@newsgroup-nntp-06.dc1.easynews.com...
>I have a SBS2003 and use the outlook web access. All has been working well.
>I changed my ISP and now I cant connect to the to outlook web access. Using
>the new IP address for my new ISP my vpn still works.
>
> Any ideas whats happening?
>
> Thanks
>
Hi larry,
I have only ever used the IP address. Normally when I was outside the office
I would go to http://210.23.149.235/exchange and the outlook web access
login page would come up. But now if I change the old IP address with the
new IP address I get a message "The requested URL'/exchange' was not found
on this server.
"Larry Struckmeyer [SBS-MVP]" <lstruckmeyer@newsgroup-wizards.com> wrote in
message news:%23%234Q8SwJKHA.5772@newsgroup
> Hi Mark:
>
> The answer may be in the way you address OWA? When you changed the ISP
> did you also change the Public DNS records to reflect the new public IP
> address of your network edge device?
>
> --
> Larry
> Please post the resolution to your
> issue so that others may benefit.
>
> Get a Health Check for SBS at:
> www.sbsbpa.com
>
>
> "Mark" <nop@newsgroup> wrote in message
> news:KUslm.650412$jp1.346260@newsgroup-nntp-06.dc1.easynews.com...>
>>I have a SBS2003 and use the outlook web access. All has been working
>>well. I changed my ISP and now I cant connect to the to outlook web
>>access. Using the new IP address for my new ISP my vpn still works.
>>
>> Any ideas whats happening?
>>
>> Thanks
>>
"Mark" <nop@newsgroup> wrote in message
news:uUDlm.673427$Tp1.253856@newsgroup-nntp-01.dc1.easynews.com...I am assuming that is the SBS website responding, which indicates IIS is
> Hi larry,
>
> I have only ever used the IP address. Normally when I was outside the
> office I would go to http://210.23.149.235/exchange and the outlook web
> access login page would come up. But now if I change the old IP address
> with the new IP address I get a message "The requested URL'/exchange' was
> not found on this server.
running and the firewall is port forwarding, but it may indicate Exchange
may not be. Have you confirmed the all the Exchange services are running? Go
to the Services console, check all interations of Microsoft Exchange...
services that are set to "Automatic" to insure they are Started.
In the Default Website properties, General tab, next to the IP address box,
there's an Advanced button. Click on it. What do you see in there for the
hostheader value?
Also, did you previously use https://210.23.149.235/exchange (with an 's' in
https)?
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Please reply back to the newsgroup or forum for collaboration benefit among
responding engineers, and to help others benefit from your resolution.
Ace Fekay, MCT, MCTS Exchange, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer
For urgent issues, please contact Microsoft PSS directly. Please check
http://support.microsoft.com for regional support phone numbers.
Hi Mark,
Thanks for your post and others' good suggestions.
In addition, please re-run CEICW with the new IP address your ISP provided and see if it changes the OWA external access. As Larry said, the ISP provider should also
change the Public DNS records to reflect the new public IP address to your SBS server like what the old ISP did in the past.
Hope it helps.
Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support
Thanks all for your help so far.
I dont remember asking my ISP to do anything in regards to the DNS records
in the past. The OWA just worked by its self. What do I ask them to do?
host header value is blank
All services are set to Auto
I did run the CEICW and added the new IP address etc.
""Robbin Meng [MSFT]"" <v-robmen@newsgroup> wrote in message
news:w7d62B8JKHA.7496@newsgroup
>
>
> Hi Mark,
>
> Thanks for your post and others' good suggestions.
>
> In addition, please re-run CEICW with the new IP address your ISP provided
> and see if it changes the OWA external access. As Larry said, the ISP
> provider should also
> change the Public DNS records to reflect the new public IP address to your
> SBS server like what the old ISP did in the past.
>
> Hope it helps.
>
>
>
> Best regards,
> Robbin Meng(MSFT)
> Microsoft Online Newsgroup Support
>
>
"Mark" <nop@newsgroup> wrote in message
news:9JDmm.594793$op1.119392@newsgroup-nntp-05.dc1.easynews.com...Not asking the ISP, or logging in to your domain Registrar account to change
> Thanks all for your help so far.
>
> I dont remember asking my ISP to do anything in regards to the DNS records
> in the past. The OWA just worked by its self. What do I ask them to do?
>
> host header value is blank
>
> All services are set to Auto
>
> I did run the CEICW and added the new IP address etc.
>
>
DNS to create a 'mail' record under your domain name, is probably why you've
only been using the IP address. Using the name is the norm, where using the
IP is the exception. It's a simple change.
Now you've got my curiousity. Does your Exchange server receive mail from
the internet and send mail to the internet? If so, you would have an MX and
A record created for your WAN IP. If your Exchange server isn't setup this
way, can you describe it's role?
As for the hostheader, don't worry about it for now. You're ok with a blank
record (leaving it default).
Ace
Let me start by saying I’m no expert. I set it up many years ago and haven’t
need to change it much. For years now I just typed in the external IP
address and put /exchange at the end and bang the OWA screen displayed. With
the new ISP it doesn’t. It seems to me that the old IP address is still the
default for the OWA. Some sort of port forwarding. I have a dlink DSL router
and there isn’t any port forwarding on it.
I use POP3 to receive the email and send the email out via DNS.
I will have another go tonight when everyone has left the office
"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message
news:%23DPhlGdKKHA.4820@newsgroup
> "Mark" <nop@newsgroup> wrote in message
> news:9JDmm.594793$op1.119392@newsgroup-nntp-05.dc1.easynews.com...>
>> Thanks all for your help so far.
>>
>> I dont remember asking my ISP to do anything in regards to the DNS
>> records in the past. The OWA just worked by its self. What do I ask them
>> to do?
>>
>> host header value is blank
>>
>> All services are set to Auto
>>
>> I did run the CEICW and added the new IP address etc.
>>
>>
> Not asking the ISP, or logging in to your domain Registrar account to
> change DNS to create a 'mail' record under your domain name, is probably
> why you've only been using the IP address. Using the name is the norm,
> where using the IP is the exception. It's a simple change.
>
> Now you've got my curiousity. Does your Exchange server receive mail from
> the internet and send mail to the internet? If so, you would have an MX
> and A record created for your WAN IP. If your Exchange server isn't setup
> this way, can you describe it's role?
>
> As for the hostheader, don't worry about it for now. You're ok with a
> blank record (leaving it default).
>
> Ace
>
>
"Mark" <nop@newsgroup> wrote in message
news:ReJmm.702844$Lo1.402597@newsgroup-nntp-04.dc1.easynews.com...Mark,
> Let me start by saying I’m no expert. I set it up many years ago and haven’t
> need to change it much. For years now I just typed in the external IP
> address and put /exchange at the end and bang the OWA screen displayed.
> With the new ISP it doesn’t. It seems to me that the old IP address is
> still the default for the OWA. Some sort of port forwarding. I have a
> dlink DSL router and there isn’t any port forwarding on it.
>
> I use POP3 to receive the email and send the email out via DNS.
>
> I will have another go tonight when everyone has left the office
FYI, POP3 and IMAP4 are client retrieval protocols (not a sending protocol),
such as if you were using Comcast, Verizon, and many others, and you would
setup Outlook or Outlook Express to receive mail using POP3. Many company
systems using Exchange normally don't allow POP3 or IMAP4 to retrieve their
mail. They would normally simply use OWA outside of the network, or
configure Outlook Anywhere (RPC/HTTPS).
I can understand not being an expert. No problem. However, I was simply
asking if your Exchange server receives and sends mail to the internet for
your company users.
Now if your Exchange server is truly receiving and sending mail for your
company on the internet, then you must already have an MX record created in
your public DNS zone. This record tells other mail servers on the internet
who your mail server is that receives mail for your company, otherwise no
one can send you mail. The MX record points to an "A" or "host" record, such
as mail.yourCompany.com.
Is this how it is setup?
If so, since the ISP change, are you still receiving mail from the internet
or not?
Ace
The server is setup this way.
We have a company that host our email. They control the MX record.
We have a differant company as our ISP
The server downloads email via pop3 and sends out email directly to the
Internet. The out going email does not go via the company that host our
email.
You would think that the server wouldnt know about the new ISP and the new
IP address. You would think that when the new IP address was used
(externally) the server would just act on the request and display the OWA
login screen as it did with the old IP address.
"Ace Fekay [MCT]" <aceman@newsgroup> wrote in message
news:urTNKmjKKHA.3424@newsgroup
> "Mark" <nop@newsgroup> wrote in message
> news:ReJmm.702844$Lo1.402597@newsgroup-nntp-04.dc1.easynews.com...>
>> Let me start by saying I’m no expert. I set it up many years ago and
>> haven’t need to change it much. For years now I just typed in the
>> external IP address and put /exchange at the end and bang the OWA screen
>> displayed. With the new ISP it doesn’t. It seems to me that the old IP
>> address is still the default for the OWA. Some sort of port forwarding. I
>> have a dlink DSL router and there isn’t any port forwarding on it.
>>
>> I use POP3 to receive the email and send the email out via DNS.
>>
>> I will have another go tonight when everyone has left the office
> Mark,
>
> FYI, POP3 and IMAP4 are client retrieval protocols (not a sending
> protocol), such as if you were using Comcast, Verizon, and many others,
> and you would setup Outlook or Outlook Express to receive mail using POP3.
> Many company systems using Exchange normally don't allow POP3 or IMAP4 to
> retrieve their mail. They would normally simply use OWA outside of the
> network, or configure Outlook Anywhere (RPC/HTTPS).
>
> I can understand not being an expert. No problem. However, I was simply
> asking if your Exchange server receives and sends mail to the internet for
> your company users.
>
> Now if your Exchange server is truly receiving and sending mail for your
> company on the internet, then you must already have an MX record created
> in your public DNS zone. This record tells other mail servers on the
> internet who your mail server is that receives mail for your company,
> otherwise no one can send you mail. The MX record points to an "A" or
> "host" record, such as mail.yourCompany.com.
>
> Is this how it is setup?
>
> If so, since the ISP change, are you still receiving mail from the
> internet or not?
>
> Ace
>
>
>
>
| Similar Threads | ||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| access Outlook autocomplete | James | VB Script | 1 | 21 Sep 2009 |
| Outlook Web Access is a clunker! | Fotogra4 | .NET General | 2 | 22 Apr 2009 |
| Outlook Web Access in IE7 | Photubias | Vista mail | 24 | 21 Dec 2007 |
| Outlook Web Access | KISD Ray | Vista security | 8 | 30 Jul 2007 |
| Re: Outlook web access | Frank Saunders, MS-MVP OE | Vista General | 0 | 14 Jun 2006 |