@JaredBusch said in Port 25 E-Mail Sending Has Stopped Working:

@garak0410 said in Port 25 E-Mail Sending Has Stopped Working:

No, no prior connector made, so guessing it was just luck. I did get the alert that on June 2020, TLS 1.0, and 1.1 were being retired for 1.2+ but it should still be working now, correct? And oddly, it was about the time of that "Office 365 Alert" that this stopped working.

Yes, if you have no connector setup, then it was pure luck that this was ever working.

Basically as far as O365 was concerned, your copier was an entire email server somewhere sending email in to your domain like any other public email server.

Do you have your office IP address in your SPF TXT record for your domain?

I wonder why the Dell VTRX also stopped sending alerts...has to be related.

Yes...I have two TXT records...one for a 192 address and the other for that SFP domain name. Nothing has changed there...

@JaredBusch said in Port 25 E-Mail Sending Has Stopped Working:

@garak0410 said in Port 25 E-Mail Sending Has Stopped Working:

We use Exchange Online with our Office 365 account and it is 100% cloud based.

On the Toshiba copiers, these are the settings that have been untouched for 4 years and nothing changed here:

TLS 1.2 is now required for authenticated sending. Does your unit support that? If not, that is why that failed.

But for basic SMTP, everything should still be accepted. Did you ever make a receive connector in O365 so it knows this is your email? Or was it just luck that this was coming in?

No, no prior connector made, so guessing it was just luck. I did get the alert that on June 2020, TLS 1.0, and 1.1 were being retired for 1.2+ but it should still be working now, correct? And oddly, it was about the time of that "Office 365 Alert" that this stopped working.

We have three Toshiba Copiers and a Dell VTRX system that use Port 25 to send SCAN TO EMAIL and alerts respectively and last week, it just stopped working. We use Exchange Online with our Office 365 account and it is 100% cloud based.

On the Toshiba copiers, these are the settings that have been untouched for 4 years and nothing changed here:

Nothing has changed here or on our network. And for kicks, I did try Port 587 with authentication on the Toshiba's and it won't work. Our copier vendor said the Port 25 option is best practice. It will say sending email and then nothing. In the logs, it just shows "Failed to connect to SMTP server."

On the Dell VTRX, it only has a single, bare bones option with no way to change to Port 587...

Here are the troubleshooting steps and notes so far:

• No Port 25 blocking by ISP

• Hardware Firewall and the Windows Firewall on the Domain Controller and DHCP/DNS server do not show any kind if Port 25 anomaly.

• I worked thoroughly with our copier partner, Dell and Microsoft and all have thrown this back on me as an environmental issue.

• I've rebooted the servers and switches (we have unmanaged switches).

• Just for note, Veeam, Backup Assist and Spiceworks all use Port 587 and have no issues.

• I used a telnet connection to our Exchange Server on port 25 and tried some basic tests and they call come back fine...

ehlo ourdomain.com                                                                                             
250-DM5PR0401CA0040.outlook.office365.com Hello [2600:100b:b108:4964:e819:1ce4:a3df:40ff]                               250-SIZE 157286400
250-PIPELINING
250-DSN
250-ENHANCEDSTATUSCODES
250-STARTTLS
250-8BITMIME
250-BINARYMIME
250-CHUNKING
250 SMTPUTF8

helo ourdomain.com
250 DM5PR0401CA0040.outlook.office365.com Hello [2600:100b:b108:4964:e819:1ce4:a3df:40ff]

We have workarounds in place to scan to network folder but our office VP wants his fixed.

Any suggestions?

About 12:20PM today, all of our Enterprise Level HP Printers went down with Security Error 33.05.13. They have not recovered.

I've researched that error and here's the troubleshooting so far:

Tried firmware reload via USB drive. Boots to same error
Booting printers disconnected from network results in a complete boot. If I plug them back in, they lock up and if you reboot while connected, same security alert.
This is only affecting Enterprise Level Printers and not standard laserjet and deskjets. I assume it is due to added security in those class of printers.

And as I type this, our Toshiba Copiers are very sluggish when using the on device buttons. The software on them is very slow.

Other observations:

My PC lost internet only around 12:20PM and I did a release/renew and about that time, the HP's when down. I don't think this is the cause but it is interesting.
No other adverse effects on workstations or servers.
I've worked with a local HP rep who came here and HP on the phone and they don't know what the cause is.

I am about to head to an even for a few hours but will be back here at 7PM central time to continue to troubleshoot. The first thing I may do is reboot all my servers, which includes Domain Controller, DHCP and DNS.

But I am worried we have had some kind of attack and with the focus on cyber-security, management wants to be reassured.

I have WireShark but I admit I am not good at reading the results.

I'll update more in a few hours.

I'm a huge RUSH fan and since they retired, I've taken an interest in their tribute bands. This group called YYNOT is amazing and has some great original songs too...

Youtube Video

Timely topic for me. I've been using SpiceWorks help desk for many years to monitor my network/workstations/servers and to track my issues. No one here uses it to OPEN TICKETS and as Scott mentioned earlier, I believe the desktop version of the Help Desk is dead. I looked at going to the cloud version but I didn't want to have to load an agent on all devices.

We are firmly into Office 365 (E1 and E3) and I've considered using Microsoft To-Do/Planner (and Maybe a SharePoint Teams List) for my day to day stuff and to also look up historical records. But I don't want to lose my sever/workstation/network scanner as it has provided good info when I needed it. So, I'm looking for something to scan my entire network, similar to SpiceWorks help desk and just keep my to-do list separate.

Trying to plan out our next Flag Football practice...love these kids...Go Colts!

Despite it's reputation and as busy as I am, I do manage at least 30 minutes a day with Fallout 76. I'm truly enjoying the heck out of it.

@scottalanmiller said in New Server Migration Adventure:

@garak0410 said in New Server Migration Adventure:

...not that makes it easier to migrate off of that one day but very glad to have it.

Your glad to have a VRTX inverted pyramid? Why? I'd think you'd be livid that someone bought that for your environment. Why are you not upset?

http://www.smbitjournal.com/2015/11/understanding-the-role-of-the-dell-vrtx/

I'd have to be upset at myself. I made the final decision after months of negotiating on cost and features. I really tried for a good R730 with Azure as our DR but they didn't want to pay the yearly license. Add this to the Dev projects they push me on, I had had to juggle many things but also try to make the best decision I could.

@scottalanmiller said in New Server Migration Adventure:

@garak0410 said in New Server Migration Adventure:

Thanks for all of the tips thus far. I may have to rush this migration now...

I came into the office today with the oldest of the two physical servers sounding like jet airplanes taking off..before, it just sounded like a sick car. It could be days our hours before it may give it up. Not sure why the fans are running so high today but add that to some bad memory, failed drives (but still working RAID set)...it simply can't wait too much longer. I asked for this upgrade 6 months ago. But I digress.

I'd still like to take time and do the migration to 2016 rather than just moving the VM's...luckily the weekend is here (though I have to coach a few ball games this weekend.) But for sure don't want to rush this.

Moving from two physical machines down to one, seems like an odd move. When this one starts to die, a migration off of it will be even more dramatic.

Moving to a Dell VRTX with 2 nodes...not that makes it easier to migrate off of that one day but very glad to have it.

Thanks for all of the tips thus far. I may have to rush this migration now...

I came into the office today with the oldest of the two physical servers sounding like jet airplanes taking off..before, it just sounded like a sick car. It could be days our hours before it may give it up. Not sure why the fans are running so high today but add that to some bad memory, failed drives (but still working RAID set)...it simply can't wait too much longer. I asked for this upgrade 6 months ago. But I digress.

I'd still like to take time and do the migration to 2016 rather than just moving the VM's...luckily the weekend is here (though I have to coach a few ball games this weekend.) But for sure don't want to rush this.

@coliver said in Miscellaneous Tech News:

@dustinb3403 said in Miscellaneous Tech News:

@coliver Are people still actively using IE? Even on servers if I required a web browser I would never use IE.

Unfortunately yes... we still have some applications that require IE and won't work with a modern browser.

Yep...we have a few Amcrest IP Camera DVR's and they ONLY work on IE. Same for a Dynamic's GP plugin called Project Cost.

@coliver I'm that "Contact Person" and I think the frames these days are hideous...!!!

@scottalanmiller said in New Server Migration Adventure:

@garak0410 said in New Server Migration Adventure:

VM1: Active Directory / DNS / DHCP

Easy. Make a 2016 AD DC, add it to the pool, move roles, shut the old one(s) down.

Excellent...note - my file server also has an alias so it will help. There are a few things in our network (copiers and Docuware) that would only work with the primary DNS name, so will need to be aware of that.

@scottalanmiller

And I agree with that. So if I head in that direction, for sure looking for tips/tricks to make it go smoothly...

@reid-cooper said in New Server Migration Adventure:

What kind of workloads will you be upgrading?

VM1: Active Directory / DNS / DHCP
VM2: File Server / VPN
VM3: Backup Server (just runs backup software and copies to NAS...runs Veeam / Backup Assist)
VM4: SQL Server 2014
VM5: Applications Server (locally hostes applications and some metered billing programs for our copiers)
VM6: Docuware

I'm thinking of a 1 by 1 migration to 2016, starting at VM6 and moving up and then retire the old server when VM1 is complete.

Several years ago on ML, I documented my adventure of a server upgrade and Windows Server migration. Primarily, the challenge was upgrading the AD server from Small Business Server 2003 to Server 2012 R2. That was a challenge but ML was instrumental in helping me find the best documentation and methods to do so. I'll never forget the night that I pressed enter on the AD migration script but it went 100% perfect.

Since then, via Hyper-V, we run our AD, File Server and Backup Server (Veeam and BackupAssist) on that one physical server. I also re-purposed and purchased licenses for the old server and it also runs 3 virtual servers. All 6 virtuals are 2012 R2.

So today, our new Dell VRTX arrived and it will replace both of those physical servers. It is a two node system based upon PowerEdge M630 with plenty of storage and a ton of drive bays left for future use.

The purchase comes with Remote Consulting Service so I'll use that as much as I can, especially in configuring the nodes.

I also believe that migrating the VM's won't be so bad though I am looking for best practices on that.

We purchased the appropriate licenses for Server 2016 with Software Assurance. As mentioned, everything is currently on 2012 R2.

The easiest plan would be to migrate the VM's over as they are and upgrade them to 2016 later (we have the license to do so.) But I'm thinking it might be best to go ahead and knock that out now...

So looking for some opinions, suggestion and best practices...thanks...

@dbeato said in Windows 10 (Store) Remote Desktop App Errors:

@garak0410 said in Windows 10 (Store) Remote Desktop App Errors:

nges. I did change one users password to test this, put it back in his remote desktop program and same error. Dropping down to the older RD works.

I assume the user is trying to connect by DNS name correct? Have they tried by IP address?

Yes...fully qualified DNS name. I can have them try IP...this has been a very strange one...

@dbeato said in Windows 10 (Store) Remote Desktop App Errors:

@garak0410 said in Windows 10 (Store) Remote Desktop App Errors:

he store Remote Desktop has always worked until now. Both machines are up to date with the same updates and versions. It has been baffling for sure. Like I said, the traditional Remote Desktop works fine and is the workaround.

I know you have a thread on this, for anyone to know the context and background.

Yes, normally don't like to cross-post but can't seem to find an answer...

@black3dynamite

No...no password changes. I did change one users password to test this, put it back in his remote desktop program and same error. Dropping down to the older RD works.