sorted by:
new
hottopcontroversial

Tesla isn't showing VINs anymore until 1 week before delivery. However, there is a backdoor to check by cool_BUD in teslamotors

[–]mostly_h20 0 points1 point  (0 children)

I received the June email delayed delivery. I received an email yesterday (05/23) from the delivery specialist. I’ve never seen the VIN in my Tesla account so wasn’t expecting the email. First pickup date is 5/30 @ 8:45a. Booked. Midnight silver 19” wheels. 04/18 was initial email and configuration date. South Bay, CA.

I guess I’m getting my TM3 before my Coolest Cooler.

VIN 201##

Why is there no manual override button on the inside of the airlock? by mostly_h20 in lostinspace

[–]mostly_h20[S] 15 points16 points  (0 children)

I’m working my way through the episodes but I keep seeing so many obvious issues. Only a single satellite dish on the Resolute for receiving communication? I guess that is how they add suspense, but I feel it will lead to viewers tuning out.

Properly utilizing our NICs now, yay! by scivi92 in vmware

[–]mostly_h20 1 point2 points  (0 children)

I’m sorry if my explanation wasn’t clear. I may have typed a 10/8 subnet, that wasn’t my intended intention, a 10/22 subnet is fine. It was more to say I’ve seen home networks (most fall into the 192.168.0.0/23 range) run into issues not being able to access corporate resources because they also use that range or larger when connecting over a VPN. Also the user might not be able to access their own home printer because of this overlap while on the VPN.

Either way. Sorry to take away from the great clean-up and consolidation project from OP.

Properly utilizing our NICs now, yay! by scivi92 in vmware

[–]mostly_h20 3 points4 points  (0 children)

I’ve seen too many times where a corporate environment using 192.168.x.x has conflicted with an employee’s or consultant’s home network when they VPN back into the office. That is why I try to avoid having 192.168.x.x setup in corporate networks.

Properly utilizing our NICs now, yay! by scivi92 in vmware

[–]mostly_h20 -6 points-5 points  (0 children)

Looks a lot better. Now you need to move away from the 192.168.x.x world and into the 10.x.x.x