@DustinB3403 said in New ISP Issues at CEO's Home:
@marcinozga said in New ISP Issues at CEO's Home:
And can't your CEO get Verizon or whoever is in the area to run fiber to his house? Judging by the size of the house it looks like he could afford that.
Sure it might only cost a few hundred thousand. . .
I tried using our clout...all they said it "might be end of September" when they get it fixed. He couldn't wait that long...
@JasGot said in New ISP Issues at CEO's Home:
Unless I am missing something, you need a router with DHCP on the WAN side and set the LAN side to 192.168.1.1/24
Consider adding some firewall protections too. Most firewalls are also routers, so you can do both with one piece of gear.
That is an option I will consider... thank you.
Anyone going to be at SpiceWorld 2019? I'm going to be there...driving down from Little Rock on Sunday and leaving Thursday Morning.
I'm not only the IT Director for my company but for the CEO's home and it seems like when it comes to his home, I run into quirks all the time.
He lives in a huge home in a rural area:
The "X" on the far left is what we call the "boot room" and that is where the internet comes into the home. The other X's are where the other two Ubiquity switches are.
He best option the last year or so has been a Pepwave modem with a Verizon signal from a cell tower. We simply plugged in this Pepwave Modem, set a few things on it and plugged it into the switch in the boot room and the internet would propagate down to the other switches and WiFi devices, all Ubiquity devices. 3 Months ago, that tower went down and Verizon has no ETA so broadband has been horrible, 1meg or less.
So, the CEO tasked me with finding a new solution. I hesitated on Satellite Internet but weighing the only options we had, I decided ViaSat was the best option.
Well, the modem that came with Viasat has no granular control over the network, meaning no way to set or change IP, DNS, DHCP, etc, as the Pepwave had. So simply plugging in the ViaSat modem to the network resulted in no internet. I plugged my laptop directly to the ViaSat modem, and this is what it pulls (with much of the info masked for security:
Description . . . . . . . . . . . : ASIX AX88178 USB2.0 to Gigabit Ethernet Adapter
Physical Address. . . . . . . . . : ****
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : ****
IPv4 Address. . . . . . . . . . . : 67.**.**.***(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, September 5, 2019 3:19:37 PM
Lease Expires . . . . . . . . . . : Thursday, September 5, 2019 4:19:36 PM
Default Gateway . . . . . . . . . : 67.**.***.*
DHCP Server . . . . . . . . . . . : 10.**.**.***
DHCPv6 IAID . . . . . . . . . . . : ***
DHCPv6 Client DUID. . . . . . . . : ***
DNS Servers . . . . . . . . . . . : 99.196.**.**
99.197.**.**
NetBIOS over Tcpip. . . . . . . . : Enabled
It pulls a 67. IP, from a 10. DHCP and DNS is a 99.
Our local network on the current modem is on a 192.168.1.1/24 range.
The ViaSat's default IP is 192.168.100.1
I did have someone say I could link up the Pepwave to handle LAN to WAN routing and DHCP like this:
I humbly will admit not sure how to get started on this...the Pepwave does offer a lot of customization but not sure where to start since the ViaSat pulls all kinds of IP's outside the 192.168.1.1/24 range...
Any suggestions?
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 That means your copier should now work.
Plain SMTP, no authentication, or anything.
The only requirement is that it has to use a from address of [email protected]
Sadly, same on both Toshiba Copiers, HP Printers and Dell VTRX:
Failed to connect to SMTP server
SMTP protocol error
Do you ever have those IT moments where a fix to something makes you feel foolish but those in your field, especially in a SOLO IT SHOP can totally relate...
Well, this is working now...and almost too embarrassed to say why...but I will...
IP Address was wrong...mind you, we used the same one for years...YEARS...and I've spoken with Microsoft Office 365 support 3 times and they know which IP address I was using...why couldn't they have simply said "Oh, this is the problem..."
It was going to a direct IP address and stopped working...
I tried the DNS name and no go.
Finally, though @JaredBusch's awesome help, it exposed the real IP address to use...and it is fully working now...I do wonder why it just stopped working...but grateful for the help. Hope to see a few of you at SpiceWorld...
Oh, you were using an old O365 IP address? Yeah - that's what sucks about using IPs instead of DNS entries. If you change the IP, you have to change everything that points to it... but if you use a DNS entry instead... they change where it points and all remains good.
The sad thing is. I used the DNS entry during all of this troubleshooting and it would never take it. 
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 That means your copier should now work.
Plain SMTP, no authentication, or anything.
The only requirement is that it has to use a from address of [email protected]
Sadly, same on both Toshiba Copiers, HP Printers and Dell VTRX:
Failed to connect to SMTP server
SMTP protocol error
Do you ever have those IT moments where a fix to something makes you feel foolish but those in your field, especially in a SOLO IT SHOP can totally relate...
Well, this is working now...and almost too embarrassed to say why...but I will...
IP Address was wrong...mind you, we used the same one for years...YEARS...and I've spoken with Microsoft Office 365 support 3 times and they know which IP address I was using...why couldn't they have simply said "Oh, this is the problem..."
It was going to a direct IP address and stopped working...
I tried the DNS name and no go.
Finally, though @JaredBusch's awesome help, it exposed the real IP address to use...and it is fully working now...
I do wonder why it just stopped working...but grateful for the help. Hope to see a few of you at SpiceWorld... 
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 That means your copier should now work.
Plain SMTP, no authentication, or anything.
The only requirement is that it has to use a from address of [email protected]
Sadly, same on both Toshiba Copiers, HP Printers and Dell VTRX:
Failed to connect to SMTP server
SMTP protocol error
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
data
354 Start mail input; end with <CRLF>.<CRLF>
Subject: Test SMTPTest Message
.
Here are my results...
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
Thank you...that was helpful...it looks like I did set it up correctly...that said, I do not have options like in this photo below...
@JasGot said in E-Mail Sending Has Stopped Working On Hardware Devices:
What's the security on your connector?
Should include anonymous
That may be part of the problem...I do not see these options for my connector...is it on a different screen? I also didn't see these options when setting up the connector.
@Pete-S said in E-Mail Sending Has Stopped Working On Hardware Devices:
@scottalanmiller said in E-Mail Sending Has Stopped Working On Hardware Devices:
In most cases like this, we run a Postfix server on Fedora that accepts unauthenticated port 25 from the devices and then sends out authenticated through O365 or whatever. Often that's the only way.
Feels like a smtp relay for sure is the best way to handle networks where you have devices sending email.
Just imagine changing ISP or whatever and then have to go through all email capable devices to make sure they now have the proper outgoing email settings.
I believe this is going to be in my near future...just weird for it to BAM! and stop...makes me wonder if I have a network issue...I had a feedback loop a few months ago that drove me crazy until I could finally locate it...
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
OK, that's what the connector is supposed to fix. authentication is IP based instead of username/password based.
did you confirm that your PC's external IP is the same as the IP you provided in the connector? (google - what's my IP?)
Yessir...shows correct IP Address.
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@scottalanmiller said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
I set up SCAN TO EMAIL on some Enterprise HP printers we have and it also fails: General send to email error
It's very rare that devices of that ilk can send to office 365. The assumption is that normally a relay will be necessary. but is a cheap and simple thing to do.
They can talk perfectly when just using straight up SMTP with no auth and you have a connector set up. That is the point of connectors.
@garak0410 have you made a connector on O365 as @JaredBusch suggested earlier in the thread? I agree with him that that should fix the issue.
Why it worked before? I haven't a clue - really seems like it should not have because what you were doing was basic relaying.. which MS shouldn't allow.
Sure thing...what needs to go in this connector? By Domain Name or by IP? And if by IP, will that be our internet gateway IP rather then our local 10. addresses? Finally, how long does it take to propagate?
I've never set one up, but in just thinking about - it seems that you would put the external IP address of your gateway. MS has no way of seeing your 10. address on a SMTP connection.
Propagation should be instant. When your machine attempts to connect, it should look to see if you have any connectors setup, if yes - check against them. Done.
I used my External Gateway...email still failing to send...(General send to email error) may have to try the other suggestions in this thread...
With the connector in place, something I would try is - try telneting to port 25 from your PC and see if you can go through an entire send process from your PC (On the same network as the printer/AIO device).
This is what I got when telnet with port 25..didn't get past the Mail From:
mail from: [email protected]
530 5.7.57 SMTP; Client was not authenticated to send anonymous mail during MAIL FROM [DM5PR05CA0003.namprd05.prod.outlook.com]
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@scottalanmiller said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
I set up SCAN TO EMAIL on some Enterprise HP printers we have and it also fails: General send to email error
It's very rare that devices of that ilk can send to office 365. The assumption is that normally a relay will be necessary. but is a cheap and simple thing to do.
They can talk perfectly when just using straight up SMTP with no auth and you have a connector set up. That is the point of connectors.
@garak0410 have you made a connector on O365 as @JaredBusch suggested earlier in the thread? I agree with him that that should fix the issue.
Why it worked before? I haven't a clue - really seems like it should not have because what you were doing was basic relaying.. which MS shouldn't allow.
Sure thing...what needs to go in this connector? By Domain Name or by IP? And if by IP, will that be our internet gateway IP rather then our local 10. addresses? Finally, how long does it take to propagate?
I've never set one up, but in just thinking about - it seems that you would put the external IP address of your gateway. MS has no way of seeing your 10. address on a SMTP connection.
Propagation should be instant. When your machine attempts to connect, it should look to see if you have any connectors setup, if yes - check against them. Done.
I used my External Gateway...email still failing to send...(General send to email error) may have to try the other suggestions in this thread...
@Dashrender said in E-Mail Sending Has Stopped Working On Hardware Devices:
@JaredBusch said in E-Mail Sending Has Stopped Working On Hardware Devices:
@scottalanmiller said in E-Mail Sending Has Stopped Working On Hardware Devices:
@garak0410 said in E-Mail Sending Has Stopped Working On Hardware Devices:
I set up SCAN TO EMAIL on some Enterprise HP printers we have and it also fails: General send to email error
It's very rare that devices of that ilk can send to office 365. The assumption is that normally a relay will be necessary. but is a cheap and simple thing to do.
They can talk perfectly when just using straight up SMTP with no auth and you have a connector set up. That is the point of connectors.
@garak0410 have you made a connector on O365 as @JaredBusch suggested earlier in the thread? I agree with him that that should fix the issue.
Why it worked before? I haven't a clue - really seems like it should not have because what you were doing was basic relaying.. which MS shouldn't allow.
Sure thing...what needs to go in this connector? By Domain Name or by IP? And if by IP, will that be our internet gateway IP rather then our local 10. addresses? Finally, how long does it take to propagate?
@Dashrender said in Port 25 E-Mail Sending Has Stopped Working:
@Dashrender said in Port 25 E-Mail Sending Has Stopped Working:
There is no mention that unencrypted port 25 was going to change, so currently TLS 1.0 should still work until June 2020
What I meant to say was -
Are your devices attempting to use opportunistic TLS? or are they going purely unencrypted?
If purely unencrypted - then I wouldn't expect that MS's killing of TLS 1.0 and 1.1 would ever make any difference.
But if it is using opportunistic TLS, then it should still work today even if your equipment is stuck on TLS 1.0 or 1.1
That is a good question. On the Dell VTRX (screen shot above) it is just Plain Jane. Oh the Toshiba, I have options to adjust some SSL / TLS settings but even that won't work.
If there is any correlation between the copiers and Dell VTRX is that they are both non-windows/non-web browser based devices.
I've spent way too much time on this but it will have to be resolved.
I set up SCAN TO EMAIL on some Enterprise HP printers we have and it also fails: General send to email error
It was set to Port 25 and no authentication needed.
I then set it up to 587 and authentication...same generic error: General send to email error
@kamidon said in Gaming - What's everyone playing / hosting / looking to play:
@garak0410 Whoa, there's a non-combat mode? Ok that sounds intriguing.
Nothing like getting ganked over and over to make you hate MMOs.
Heh or being the bored ganker...
Yep...I think it is OFF by default but you can turn PvP on or off in "Adventure Mode"...and it is the most friendly game I've ever played online...I had a surplus of Power Armor suits and I just felt generous and had a level 7 person follow me to my stash and I just gave him one.
@scottalanmiller said in Gaming - What's everyone playing / hosting / looking to play:
@garak0410 said in Gaming - What's everyone playing / hosting / looking to play:
I'm still playing Fallout 76 on the XBOX. Despite the bad press, I've been patient with the bugs and I'm really enjoying the experience of the game. Up to Level 44 with just occasional playing when I have time.
I love the idea of a prequel, but I'm so not into online gaming, I stick to single player experiences because I just can't commit the time.
The most interesting thing about Fallout 76 being an Online game is there is no pressure to play "online"...The "online" aspect seems to be more content related, map expansions, etc. For me, it feels like a never ending single player game. I play in non-combat mode meaning when I see others online, most of the time, we stop and wave at each other, trade or help complete an event...and you can use other peoples camp's for repair and rest...it is the most "relaxed" online game I've played...
I'm still playing Fallout 76 on the XBOX. Despite the bad press, I've been patient with the bugs and I'm really enjoying the experience of the game. Up to Level 44 with just occasional playing when I have time.