No go. Open to other ideas.....

@dbeato said in My complex Windows Copy command stopped working.....:

@jasgot said in My complex Windows Copy command stopped working.....:

It said Syntax Error. 0 Files Copied.

But..... now it is working.......

Well, maybe a reboot happened or it couldn't read the data and then now it can.

Possibly. I'm glad is doesn't need any more head-scratching!

It said Syntax Error. 0 Files Copied.

But..... now it is working.......

Windows Server 2012 installed these updates on Thursday:
KB5007300
KB890830
KB5007260

My copy command ran fine on Friday.
The server rebooted on Saturday and my copy command started failing with Syntax error.

Here is my copy command:

copy \\bsastore\BSA\WSReaderData\METEREXPORT.TXT \\bsastore\BSA\WSReaderData\ExportHistory\METEREXPORT_%time:~0,2%%time:~3,2%%time:~6,2%_%date:~-10,2%%date:~-7,2%%date:~-4,4%.txt

The results of the copy should be METEREXPORT_HHMMSS_MMDDYYYY.txt
Actual successful result from before:

METEREXPORT_173001_11122021.txt

Any thoughts? I don't see anything in those three updates that would affect this.

@obsolesce said in HTML Editing:

For me using a good IDE can be much more efficient for most languages over Notepad.

I like UltraEdit.
There are macros written by the user group to remove all HTML code.

Hehehe... In the old days we used to write TSRs to monitor apps and restart them!

@dbeato said in Exchange 2013 / IIS / Certificate / EMS Gurus?:

@jasgot Also take a look here.
https://support.microsoft.com/en-us/topic/you-can-t-access-owa-or-ecp-after-you-install-exchange-server-2016-cu6-88b3fe67-5f97-a8a2-8ed8-70034ff15761

Thanks. This looks helpful, I'll give it a try!

@dbeato said in Exchange 2013 / IIS / Certificate / EMS Gurus?:

@dbeato Check this article

https://docs.microsoft.com/en-us/exchange/troubleshoot/client-connectivity/owa-ecp-ems-cannot-connect-after-self-signed-certificate-removed

Thank you. I found that article a few days ago and followed it without success.

@scottalanmiller said in Understanding STUN???:

Yeah, very ignorable. But... why not just open the port and make it go away?

That was a good idea. It worked. Now I won't stress because something is less than perfect.

@scottalanmiller said in Understanding STUN???:

They noted that they only added the warning recently so it might have always had the issue without reporting it previously.

Okay. Sounds like I can just ignore it. I would like to be able to turn off the warning, though!

@jaredbusch Thanks! Hopefully he'll drop in.....

@scottalanmiller said in Understanding STUN???:

I don't think Unifi offers STUN services anyway.

@scottalanmiller said in Understanding STUN???:

You have a Unifi controller that does not have ports forwarded to it?

It does, just not the STUN port.

@scottalanmiller said in Understanding STUN???:

The APs themselves have STUN errors? I've never seen that. Can you show the error?

The errors are listed in the controller.

https://www.backblaze.com/blog/backblaze-is-now-a-public-company/

ETA: Direct Stock link if interested

Backblaze (BLZE)

@travisdh1 said in Understanding STUN???:

Then that makes no sense to me. If the setup is as you describe in your initial post, then there has to be some way they are communicating through both firewalls.

Four APs -> Comcast Cable Modem -> Internet -> Comcast Cable Modem -> Firewall/Router -> Network Controller

The Four APs have a 10.1.10.x address behind the cable modem
The Network Controller has a 192.168.1.x address behind a router with a public IP.

Anyone around with over-the-top knowledge of Exchange Server 2013, IIS, Certs, and Exchange Management Shell?

I need some help and am willing to pay for a successful outcome.

This is what I am fighting with:

VERBOSE: Connecting to EXCHANGE.mydomain.Local.
New-PSSession : [exchange.mydomain.local] Connecting to remote server
exchange.mydomain.local failed with the following error message : The client
cannot connect to the destination specified in the request. Verify that the
service on the destination is running and is accepting requests. Consult the
logs and documentation for the WS-Management service running on the
destination, most commonly IIS or WinRM. If the destination is the WinRM
service, run the following command on the destination to analyze and configure
the WinRM service: "winrm quickconfig". For more information, see the
about_Remote_Troubleshooting Help topic.

At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Micr ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : OpenError: (System.Manageme....
    RemoteRunspace:RemoteRunspace) [New-PSSession], 
    PSRemotingTransportException
+ FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed

Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:

This all started after deleting an old outdated cert called: Microsoft Exchange
I believe it is the cert that allows encrypted communication between the Default Web site and the Exchange Back End.

@travisdh1 said in Understanding STUN???:

@jasgot said in Understanding STUN???:

@travisdh1 said in Understanding STUN???:

You'll need to open network ports to the UniFi controller on the firewall it sits behind.

Except I'm not certain I even want STUN. If it does not provide a required component for these APS to work (they are working without it now) , I'll likely to leave those ports closed on the controller side.

That's the thing, they'll work in the current configuration, but you can't update any settings.

How so? I can make all kinds of changes and even open a debug terminal to it without STUN working.

@travisdh1 said in Understanding STUN???:

You'll need to open network ports to the UniFi controller on the firewall it sits behind.

Except I'm not certain I even want STUN. If it does not provide a required component for these APS to work (they are working without it now) , I'll likely to leave those ports closed on the controller side.

I am trying to understand what STUN does. I have some UniFi APs out in the wild behind a NAT device, and I have a Network Controller in an office behind a NAT device.

I am getting STUN errors on the APs, but I'm not sure if I need to worry about it.

when I look at this statement in the UI documentation:

In simple terms, STUN provides a way for devices to securely communicate with
 other devices when they're located behind a router.

It's unclear if they are discussion my scenario, where the APs and the Controller are not behind the same NAT device. Also, is STUN so APs behind NAT can talk to other APs behind the SAME NAT?

The problem is I have a configuration they do not specifically address, and I don't know if their statements apply to my secenario.

Thanks.