Faxmaker - updating Office 365 for Receiving
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
@Dashrender said in Faxmaker - updating Office 365 for Receiving:
So why did an IP address change this? Is there a rule in O365 that sent ###@faxmaker.com to a specific IP or Host that wasn't updated?
This is the 'guess' There is a connector in O365 for faxmaker.com and points to a pair of IPs... which are his IPs, Old and new. Last night going through the connector setup there was a step to Validate - and it was failing.
Today one is failing and one is succeeding. But I went through some of his DNS and added his updated IP to the ARecord.
Nice find. Of course the old IP is failing
Does O365 treat it round robin?
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
So - the problem is not the problem but a different problem that is the problem. Facepalm
In talking with the person today, the issue is this:
User Janice creates an email - but is a fax. Generates Email in Outlook and is sent. Office 365 gets it and sees that it is to <number>@faxmaker.com and kicks it out of O365 back to the onsite server FaxMaker where it has access to the modems.
From there, the email is converted to a fax and is sent using one of the four modems attached to the box.
Stinks when the user reports the problem wrong, you look for days, hours at least, go back and say - are you sure? and well of course they aren't.
-
@Dashrender said in Faxmaker - updating Office 365 for Receiving:
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
So - the problem is not the problem but a different problem that is the problem. Facepalm
In talking with the person today, the issue is this:
User Janice creates an email - but is a fax. Generates Email in Outlook and is sent. Office 365 gets it and sees that it is to <number>@faxmaker.com and kicks it out of O365 back to the onsite server FaxMaker where it has access to the modems.
From there, the email is converted to a fax and is sent using one of the four modems attached to the box.
Stinks when the user reports the problem wrong, you look for days, hours at least, go back and say - are you sure? and well of course they aren't.
Yes,.. makes my asking a question seem like I have no idea what I am talking about. True enough I wasn't familiar with the application or how it worked,.. but explained wrong,.. well Et on you..who made who?
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
Of note - this is totally different then that which was emailed or discussed via phone yesterday with the person.....
Well then.... ugh
-
@Dashrender said in Faxmaker - updating Office 365 for Receiving:
So why did an IP address change this? Is there a rule in O365 that sent ###@faxmaker.com to a specific IP or Host that wasn't updated?
Because MS is sending to the old IP address, of course!
-
@Dashrender said in Faxmaker - updating Office 365 for Receiving:
So why did an IP address change this? Is there a rule in O365 that sent ###@faxmaker.com to a specific IP or Host that wasn't updated?
Yeah, it's email forwarding and the MX records would point to the wrong place.
-
so poking around Google, points to the Firewall blocking from the IP / Port aspect.
so lets see if we can allow all port 25 traffic.
-
But this worked beforehand, why would you have to update your firewall?
Go ahead and test, but the firewall should already be working. An IP change doesn't change the port filtering...
-
@DustinB3403 said in Faxmaker - updating Office 365 for Receiving:
But this worked beforehand, why would you have to update your firewall?
Go ahead and test, but the firewall should already be working. An IP change doesn't change the port filtering...
I suppose that there could be new rules for the new connection.
-
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
@DustinB3403 said in Faxmaker - updating Office 365 for Receiving:
But this worked beforehand, why would you have to update your firewall?
Go ahead and test, but the firewall should already be working. An IP change doesn't change the port filtering...
I suppose that there could be new rules for the new connection.
I suppose that is possible, if the rules were specific for the original IP address.
-
@DustinB3403 said in Faxmaker - updating Office 365 for Receiving:
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
@DustinB3403 said in Faxmaker - updating Office 365 for Receiving:
But this worked beforehand, why would you have to update your firewall?
Go ahead and test, but the firewall should already be working. An IP change doesn't change the port filtering...
I suppose that there could be new rules for the new connection.
I suppose that is possible, if the rules were specific for the original IP address.
That's normal, that rules apply to a specific address or connection. I'm guessing, but likely the router has a new connection for the new line. So no rules would exist for it by default.
-
Just learned the duration of this issue,... It's not new,.. Not two or three days,... not even a week or two...
Try Twelve Weeks,....
sigh
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
Just learned the duration of this issue,... It's not new,.. Not two or three days,... not even a week or two...
Try Twelve Weeks,....
sigh
Yeah... I peed in the pool.
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
Just learned the duration of this issue,... It's not new,.. Not two or three days,... not even a week or two...
Try Twelve Weeks,....
sigh
OMG, LMAO. We've entered the ridiculous zone.
-
Did you tell @art_of_shred
-
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
Did you tell @art_of_shred
Was on a NTG conference call when it was brought up.
-
@gjacobse said in Faxmaker - updating Office 365 for Receiving:
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
Did you tell @art_of_shred
Was on a NTG conference call when it was brought up.
Oh okay. LOL
-
Was there swearing?
-
@scottalanmiller said in Faxmaker - updating Office 365 for Receiving:
Was there swearing?
No, we were all professional and the like.
-
Well mostly all of us,.. that guy @art_of_shred was sarcastic the entire call..
