Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 21 replies
  • Subscribers 3 subscribers
  • Views 7601 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

8.203 update: now cannot access my company's external domain

Marshall Excelsior
Heya, all. 

About 12 hours after my Astaro installed the 8.203 firmware on Tuesday, I find that the entire corporate network is entirely unable to access our company domain name. We can't access our corporate website, can't get our externally-hosted email, can't even PING the associated domain names OR IP addresses.

I've checked with the webhost - nothing is wrong with them. In fact, all of the services I just mentioned are available when I connect via my Verizon wireless card.

I've checked with my ISP - they tell me they're not blocking anything; other businesses in the area with the same provider can access our stuff just fine.

All signs point back to some sort of problem with the Astaro. The company that sold it to us is at a loss, and I've yet to hear back from Sophos on the ticket he opened on our behalf. 

We're going on 48 hours without email. Does anyone have any suggestions while I'm waiting on Sophos support?


This thread was automatically locked due to age.
Parents
  • 0
    SMTP (outbound) isn't the problem. It's inbound (POP) where the email is breaking down. POP3 log lists the following set of entries for each connection:

    2011:12:15-07:17:45 astaro pop3proxy[4350]: Accepted client connection from 192.160.120.52 for 67.225.237.104
    2011:12:15-07:18:06 astaro pop3proxy[4350]: Connect to 67.225.237.104 failed: Connection timed out
    2011:12:15-07:18:06 astaro pop3proxy[4350]: Connection to remote server failed: Can't connect to server
    2011:12:15-07:18:06 astaro pop3proxy[4350]: Client 192.160.120.52 has closed the connection

    This is consistent with our inability to access the domain name from inside the corporate network.
Reply
  • 0
    SMTP (outbound) isn't the problem. It's inbound (POP) where the email is breaking down. POP3 log lists the following set of entries for each connection:

    2011:12:15-07:17:45 astaro pop3proxy[4350]: Accepted client connection from 192.160.120.52 for 67.225.237.104
    2011:12:15-07:18:06 astaro pop3proxy[4350]: Connect to 67.225.237.104 failed: Connection timed out
    2011:12:15-07:18:06 astaro pop3proxy[4350]: Connection to remote server failed: Can't connect to server
    2011:12:15-07:18:06 astaro pop3proxy[4350]: Client 192.160.120.52 has closed the connection

    This is consistent with our inability to access the domain name from inside the corporate network.
Children
No Data