It’s the stock RDP settings built into Pop. I am passing authentication info from my Windows client to Pop which is the authentication info defined in Pop’s RDP settings (username and password). I’m manually defining the auth info on the Windows Client so it’s not passing in the default current login information.
I’ll see if the logs mention anything. It doesn’t look like there’s an application specific log for the RDP function in Pop so maybe it’s just under syslog or journal?
EDIT: Figured it out…the username I defined in the Pop settings was all lowercase. I was sending a few uppercase letters via MS since that’s how the actual Pop login username is spelt.
Dang…ok thanks. I’ll keep working on it and I’ll update in case I find a solution.
You’re totally right, I forgot to add the picture and details when I posted. I updated the post with an image and expanded text. I did confirm that the time and timezone are consistent between the two devices.
Hey you leaf trees out of this.
Any idea how I could check? It doesn’t say anything any that I’m my carrier account…
Fair. I think I had previously uninstalled Gemini when I first got my phone so maybe that’s why the app isn’t present? But the way that they are talking about it in the article, since Gemini seems to be replacing Assistant, maybe new settings will appear for me to mess around with…
It’s rough…I still have another 13 months I think. But to the article, I don’t have the options in my phone that they’re talking about. Do you? Or has it just not rolled out to me yet?
I really really want to but I can’t for another year because I’m still paying off my pixel. It’s still carrier locked and I can’t unlock it till it’s paid off.
Ohhh that’s interesting, I forgot about those DAC cables. Although I don’t know if that would work in this case because the LAN ports in the Netgate are already RJ45 ports not a SFP port. Unless they make a DAC that is SFP+ on one side and RJ45 on the other…
Ah yeah I see. I didn’t design the diagram to a specific layer but if I had to choose one after the fact I guess this would be Layer 1 honestly. I’m really just looking for the physical interconnection of devices and making sure I don’t have a path out of the network that doesn’t go through the Netgate.
But more specifically, I was looking for information on if the C1300 and the Netgate can communicate on the ports I’ve put in the diagram or if the mistmatch in speed ratings for the ports would be a problem. As well as if the SFP+ port on the C1300 can even be used as a connection like that. In their documentation, Cisco has an example of use for those ports as stacking ports to other switches. I’ll only have the one and won’t need to stack any other so I was looking to see if the SFP+ ports can be used for non-stacking purposes.
So the UPS I was looking at is here: https://www.microcenter.com/product/506629/apc-smart-connect-ups-(smc1500-2uc)
It lists VA, W, and V.
Yeah so that’s kinda what I was getting at. If I put in three NUCs that pull 330 watts, that’s 990 watts to the NUCs by itself. If the UPS can only provide 900 watts, then pulling more than that just wouldn’t work right? The UPS would essentially discharge in seconds right?
I was looking at a ROG NUC like this one:
It states 330 watts under the power rating. And to be clear, this part of the build isn’t going to happen for a while so I was just looking up some NUC examples. I was also looking at full 1U servers too.
But to the maximum ratings portion of your response. Even if 330 is the max, don’t you want to base your predictions off of that to make sure it can handle things at max draw? Totally get that if you plan for less, chances are you won’t ever hit 330 but you’re banking on the possibility that you won’t instead of planning for if you do?
Yeah that’s kinda where I’m coming down too. They both also do IPv6 Multicast which I’ll use briefly later on when I start setting up the Nutanix CE section of the build but I mean…they look so similar I may as well save the $45.
Figured it out…capitalization…always lol. The username defined on Pop was all lowercase and I was sending the username via MS RDP with a few upper case letters since that’s how it’s spelt for the actual Pop sign on user.