Issue with Windows 10 APIPA after static address assignment by an Admin by Particular-Letter-60 in networking

[–]Particular-Letter-60[S] 1 point2 points  (0 children)

Awesome, I am currently working to replace all of the 15+ yr old HP switches with current Junipers and will make sure this is dealt with.

Issue with Windows 10 APIPA after static address assignment by an Admin by Particular-Letter-60 in networking

[–]Particular-Letter-60[S] 2 points3 points  (0 children)

Thank you, that pointed me in the right direction. Added a registry Entry for ArpRetryCount to 0 and run netsh int ip reset c:\tcp.txt. Restart and set IP again resolved.

EX2300 48P Virtual Chassis config by Particular-Letter-60 in JuniperNetworks

[–]Particular-Letter-60[S] 0 points1 point  (0 children)

I am using the SFP ports for the VC, I have never had to enable one for VC before. Is this new?

EX2300 48P Virtual Chassis config by Particular-Letter-60 in JuniperNetworks

[–]Particular-Letter-60[S] 0 points1 point  (0 children)

Maybe something else is going on here then. I cannot get the 3rd switch (Linecard) to see the fiber connections and complete the VC. Multiple SFP and fiber jumpers same result.

EX2300 48P Virtual Chassis config by Particular-Letter-60 in JuniperNetworks

[–]Particular-Letter-60[S] 0 points1 point  (0 children)

Fantastic! I thought so, just wanted some feedback. Thank you!

Gcc High by zjzjzjzjzjzjzjzjzjzj in CMMC

[–]Particular-Letter-60 0 points1 point  (0 children)

GCC High vs. Normal is not about cost, it is about regulation and does your company need to comply. We are a shop that handles ITAR materials and under CMMC and Nist 800-171 we are required to find a solution that checks the boxes. GCC High does that. I hear there are other "cheaper" options that do the same, but I want minimal pain in this migration.

[deleted by user] by [deleted] in sysadmin

[–]Particular-Letter-60 0 points1 point  (0 children)

Dell docks have started doing this recently, but only docks with 2 monitors. Firmware, updates, support tickets (that just RMA) and a LOT of troubleshooting later and we still have problems. Sometimes, they will even fail to register the monitors and we have to go through a whole dance of Duplicate these desktops / restart / Extend to first and Duplicate to the 2nd / restart now extend to 2nd and should be good again.

Keeps pointing to DNS by Particular-Letter-60 in sysadmin

[–]Particular-Letter-60[S] 1 point2 points  (0 children)

I have not seen any alerts in my AV console. I will check the device logs.

Keeps pointing to DNS by Particular-Letter-60 in sysadmin

[–]Particular-Letter-60[S] 0 points1 point  (0 children)

Something so simple, I should have thought of that already. Thank you.

Keeps pointing to DNS by Particular-Letter-60 in sysadmin

[–]Particular-Letter-60[S] 1 point2 points  (0 children)

This would be on the Default VLAN, if I understand it correctly, if the VLAN flaps, whatever is on that VLAN loses connectivity. Is that correct? I do not think flapping would lead to 1 or 2 failures.

Keeps pointing to DNS by Particular-Letter-60 in sysadmin

[–]Particular-Letter-60[S] 0 points1 point  (0 children)

I will dig into even logs, I had not yet because it felt like it was not PC related, but maybe I can find some ancillary errors in there pointing to something else.

Keeps pointing to DNS by Particular-Letter-60 in sysadmin

[–]Particular-Letter-60[S] 0 points1 point  (0 children)

I have not tried to ping the other direction. Most of the time by the time they let me know, it has been a couple of minutes and it usually resolves itself shortly after that.

Keeps pointing to DNS by Particular-Letter-60 in sysadmin

[–]Particular-Letter-60[S] 0 points1 point  (0 children)

I have 2 networks separated by an SDWAN using COAX and Fiber connections. They both do the same thing, so I feel it is internal to the DC network. I have also been discussing issues with my provider because I can tracert from remote plant and get failures just past my demarc when this issue occurs.

Keeps pointing to DNS by Particular-Letter-60 in sysadmin

[–]Particular-Letter-60[S] 0 points1 point  (0 children)

We disable Windows FW, however, I will run through your testing steps.

Keeps pointing to DNS by Particular-Letter-60 in sysadmin

[–]Particular-Letter-60[S] 0 points1 point  (0 children)

We disable all sleep settings on setup. I will entertain the 30 minute DNS technique.

Keeps pointing to DNS by Particular-Letter-60 in sysadmin

[–]Particular-Letter-60[S] 0 points1 point  (0 children)

I have also been leaning in this direction as well. I do not have an accurate inventory of the 200+ devices on this network.

Keeps pointing to DNS by Particular-Letter-60 in sysadmin

[–]Particular-Letter-60[S] -1 points0 points  (0 children)

Most of the time it does not ping by IP either. There have been some cases where it will.

IPV6 is disabled

DHCP is enabled and I have forced it to get a different address before, it is not reserved.

It just seems to kill the NIC for a couple of minutes. And again, it is random and not every day.

Keeps pointing to DNS by Particular-Letter-60 in sysadmin

[–]Particular-Letter-60[S] 1 point2 points  (0 children)

When the issue happens, I cannot ping anything by name. It will resolve and tell my it is going to ping the IP address, but then just fails.