IP changed on exchange server, now inaccesible

[joe90bass]

Hope someone can help! Following the move to our new school I've finally managed to get our servers back up and running and I've changed them over to the new IP range we have. Now I'm not able to connect to exchange via OWA (this is on the Exchange server itself nd other PCs). (I don't now about Outlook as we have no clients setup yet!)

 

I've checked DNS to ensure the new IP for the exchange server is there. I've also checked IIS to ensure that it's not pointing at the old IP. Can anyone offer any other suggestions!?

 

To be honest I haven't had a huge dig around yet as a delivery of new Servers and laptops turned up, and I was also trying to resolve with the LA the fact that their ISA server won't allow us on the Internet at the same time (hence the post now not earlier and also rather than waiting until tomorrow in case I still can't get on the net!)......

 

edit: 2003 server SP2 with Exchange 2003 SP2

 

TIA!

Edited August 7, 2008 by joe90bass

[ChrisH]

Try things like this on the server

IPconfig /registerdns

 

and on the client you are trying from make sure

 

ipconfig /flushdns

 

and also make sure the MX records have updated as well.

[joe90bass]

Try things like this on the server

IPconfig /registerdns

 

and on the client you are trying from make sure

 

ipconfig /flushdns

 

and also make sure the MX records have updated as well.

 

Checking the MX was something I thought about, but my tech and I were kicked out of school as soon as our deliveries had arrived, and I didn't get a chance to check. The registering/flushing was something I hadn't thought of!

 

Who knows by tomorrow it may have magically fixed itself! Hope so, I've got 5 servers to install plus an exchange migration......... I think some more posts may be forthcoming soon!

[FN-GM]

can you access it internally?

[joe90bass]

can you access it internally?

 

No, tried on the actual server itself. I'm having a few thoughts as to other things to try, but wanted to post here for thoughts as well in case I still can't get on the net tomorrow!

 

I was also having trouble with accessing our website and intranet on the server it's hosted on, so it makes me think it maybe DNS or IIS.

[FN-GM]

when you try and access it have you tried the internal IP and going http://localhost/exchange on the server it self?

[joe90bass]

when you try and access it have you tried the internal IP and going http://localhost/exchange on the server it self?

 

Yep, no joy......... I've put the IP and url in the exceptions in Internet explorer as well.........

[FN-GM]

As you say it sounds like IIS, i am not expert with it so i can't help anymore.

[leco]

How long has the Exchange server been offline? We lost internet access for almost two weeks, which meant that the MX record was also lost. It took a while for it to reappear and I'm still not sure how it did. Sorry not really much help, just being empathetic.

[FN-GM]

but surely it would still wok internally?

[DMcCoy]

IIS isn't configured to listen to one ip only that now doesn't exist is it?

 

Edit. Hmm You say that this is checked.

 

1) Does IIS work (http://localhost) ?

 

2) Do you show port 80 as listening with netstat -an?

Edited August 7, 2008 by DMcCoy

[leco]

but surely it would still wok internally?

 

Well mine didn't, but that might be a totally different situation.

[joe90bass]

Thanks to all for your suggestions and sympathies!

 

It was an IIS problem, I needed to change the SSL IP to the new one as well. I'd done all the other IPs in IIS......

I had also not changed the SMTP address in Exchange to the new one...

 

Lesson learnt! Stiill changing IP wasn't as horrendous as some posts on the interweb suggested it may be!

 

The LA have also sorted out the ISA server problem which was preventing us getting onthe net. So, touch wood, today is turning out to be a good day. That's a cue for major problems..........