Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.
Issue with HTTP/RPC after network disconnect failure
My setup is ISA SERVER 2006 >>> Exchange 2003. The isa server is also the dhcp server and the exchange server is also the internal, dns and active directory server. I have no front end server.
The issue is that after a network disconnect with my ISP, the exchange server publshing rule (OWA and HTTP/RPC) will not work. Internet works fine and I can even access other published sites from the isa server. however, http/rpc connections from window mobile phones, external outlook clients and OWA access will not work until I restart the ISA Firewall service.
The issue is that after a network disconnect with my ISP, the exchange server publshing rule (OWA and HTTP/RPC) will not work. Internet works fine and I can even access other published sites from the isa server. however, http/rpc connections from window mobile phones, external outlook clients and OWA access will not work until I restart the ISA Firewall service.
Who is Participating?
Hi,
What happens from outside when you go to:
https://server.domain.com/exchange
Can you telnet to this:
telnet server.domain.com 443
Thanks,
Alan.
What happens from outside when you go to:
https://server.domain.com/exchange
Can you telnet to this:
telnet server.domain.com 443
Thanks,
Alan.
I have not tried to telnet, but on the browser if i type https://server.domain.com/
Please can you try the telnet, and see what happens (I am guessing you'll get no response, but let's try anyway).
If that is the case, then it seems most likely either the perimiter firewall / router - what do you have on the perimeter?
Or, if not that, then either the ISA server itself or the exchange server.
Depending on your LAN layout, is there any machine or device that is outside the ISA server, but inside the perimeter? If so, can you try telnet (or browser) from there?
Also, can you connect to OWA from inside the ISA server (I am guessing about your network config, but perhaps your own workstation is inside the ISA server and on the same subnet as the exchange server?) If so, try connecting to OWA from your workstation:
https://server/exchange
where server is either the internal hostname or IP of the exchange server.
Thanks,
Alan.
If that is the case, then it seems most likely either the perimiter firewall / router - what do you have on the perimeter?
Or, if not that, then either the ISA server itself or the exchange server.
Depending on your LAN layout, is there any machine or device that is outside the ISA server, but inside the perimeter? If so, can you try telnet (or browser) from there?
Also, can you connect to OWA from inside the ISA server (I am guessing about your network config, but perhaps your own workstation is inside the ISA server and on the same subnet as the exchange server?) If so, try connecting to OWA from your workstation:
https://server/exchange
where server is either the internal hostname or IP of the exchange server.
Thanks,
Alan.
telnet does not work from the outside. however, it does work from the inside. Meaninig that from within the local lan the services are up on the exchange. They just do not work form the outside. This happens everytime that the isp phyiscal connection on the external wan card of the isa server gets reset. meaning that the netowrk card sees a disconnect and a reconnect. the isp rebooting thier router.
Is your ISA server's WAN-side NIC connected to an ADSL modem or a fibre termination or something?
If so, I wonder if there is some interaction there causing a problem?
Not sure how easy this will be for you (depends on whether you have a spare router lying around), but you could try putting an additional NAT router between the 'modem' (whatever is there) and the ISA server.
You'll need to setup the router to pass through outbound (might as well be everything initially at least since this is not a security measure), and make sure you port-forward whatever you need to come in (443, 25, etc etc)
That way, the ISA Server won't see a network disconnect (it will be the new router that sees the disconnect)
Nothing inside changes as the ISA Server is still the main firewall and DHCP.
Does that make any difference?
Alan.
If so, I wonder if there is some interaction there causing a problem?
Not sure how easy this will be for you (depends on whether you have a spare router lying around), but you could try putting an additional NAT router between the 'modem' (whatever is there) and the ISA server.
You'll need to setup the router to pass through outbound (might as well be everything initially at least since this is not a security measure), and make sure you port-forward whatever you need to come in (443, 25, etc etc)
That way, the ISA Server won't see a network disconnect (it will be the new router that sees the disconnect)
Nothing inside changes as the ISA Server is still the main firewall and DHCP.
Does that make any difference?
Alan.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
Do you mean you tried the additional router suggestion?
If so, your ISA server should not be seeing any disconnects now?
Alan.