Webaccess stopped working

[9iron]

Not sure what happened, but nobody can access webmail from the Internet anymore. I just get the standard "The page cannot be displayed" on my browser.

The only thing that's happened recently is that we started using an outside company to do spam filtering. I contacted the folks who host our domains, and had them update the MX records so that the mail gets sent to these new guys first. They then send the mail to us once the garbage has been removed. It's been working great, but now my webmail has crept to a halt.

Could updating those MX records have caused my webmail to stop working? I tried entering our firewall's IP address on my browser, to see if DNS was having anything to do with this, but even that didn't work.

 

[sstoppel]

Well, webaccess is just a way of looking at mail - it has nothing to do with delivery of mail to your system via smtp. I doubt that is related directly.

However, you say "from the internet" - can you access it from a host on the same net as your webmail server? if so, you have a firewall/routing problem. If no, you have a problem with webaccess itself. If your webaccess host is windows make sure the service is started. Log into that machine and see if you can ping your POA and MTA.

If your connectivity is fine, I personally would just uninstall and reinstall webaccess. It is only a portal after all, you can whack it and reinstall without affecting actual mail.

 

[goombawaho]

You need to check to see if you can access the WebAccess internally by the IP address running the WebAccess to see if it's responding then worry about external access. My guess is that it's a DNS issue, but first we have to make sure the serivice is up and functional and you're able to login.

Try it internally with the port number like
192.168.100.15:7205 or whatever port your have it on if not default.

 

[9iron]

Thanks, guys. I had to bring in the big guns on this one. It was indeed a problem w/ webaccess itself, as was verified by our inability to access it internally. Turned out to be some horribly embedded stuff that took my tech about 2 1/2 hours to find, but he did find it. It would've taken me a week. Uggh...makes me wonder what happened in the first place. Oh, well. Thanks for the replies.

Incidentally, how would I uninstall/reinstall webaccess on the server?

 

[sstoppel]

Was it running on Windows? just use Add/remove programs IIRC. Then relaunch the installer from your software directory.

 

[marvhuffaker]

With WebAccess, a rule of thumb is this... If it gets hosed, just remove and reinstall it. Or sometimes you can just reinstall it. It's much harder to troubleshoot that to just reinstall it.

WebAccess uses Apache, Tomcat (Java App), and then there is the agent itself, the doc viewer, and some other config files. Unless you deal with these issues every day (like we typically do), it's just not worth the pain and frustration to troubleshoot.

This assumes the problem is within webaccess itself. If you have problems with Apache or Tomcat, well then those have to be dealt with either way.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[terry712]

yep that's true

all i would ever do - if apache and tomcat is fine
then it gets a 2 minute look at conf files

then it's reinstall it

although webacc is normally pretty rock solid