net_tech's profile - activity

It's impossible to confirm or deny your suspicion if you don't share your capture. Your description of what it looks lik

what is slowing down the restore? Hi, Here is the first 15 seconds of a SQL database (500GB) restore from a physical Ru

what is slowing down the restore? Hi, Here is the first 15 seconds of the SQL database (500GB) restore from a physical

https://youtu.be/bo88q4JPOR0?si=5IhOOa0plkj_pIzA

it's needed for private endpoints, at least that is what was i was able to find here. https://learn.microsoft.com/en-us

Hi

Looks like our internal DNS servers (W2019) are robbing clients of 257 bytes in DNS traffic. As a result, clients can't get to some of the websites where DNS answers exceed 176 bytes.

Is there a Windows server setting that limits DNS traffic to 176 bytes? We are not seeing this 176 bytes limit on other protocols.

Thank you!

privatelink.azure-api.net zone was present on the internal DNS server for other reasons, but didn't have the CNAME recor

Is this a CNAME chaining issue or CNAME chaining limit configured on the 172.21.59.11 windows server?

@SYN-bit, No, Truncated flag is 0. = : Message is not truncated Someone asked for this behavior here -> https://s

Someone asked for this behavior here -> https://serverfault.com/questions/1160057/bind9-limit-the-answer-rrs-in-a-sta

Capture has been wranglered 97.205.219.232 is 1.1.1.1, 172.16.96.78 - Client, 172.21.59.11 - Server https://drive.go

Capture has been wranglered 97.205.219.232 is 1.1.1.1 172.16.96.78 - Client 172.21.59.11 - Server https://drive.goog

Here is a pcap from a good working environment. Server (192.168.20.5) gets a 433 byte response from 1.1.1.1 and responds

Here is a pcap from a good working environment. Server (192.168.20.5) gets a 433 response from 1.1.1.1 and responds to t

highway robbery Hi Looks like our internal DNS servers (W2019) are robbing clients of 257 bytes in DNS traffic. As a re

NTLM decryption Hi, I have a capture of an ansible playbook running against a Windows server in a LAB. Ansible is confi

NTLM decryption Hi, I have a capture of an ansible playbook running against a Windows server in a LAB. Ansible is confi

no, without dns name resolution policy in place on the client computers, there is no record security info in dns headers

DNSSEC question Hi, We are using DNSSEC on the internal network (Windows 2022 DNS server / 172.16.4.10). Recently I cam

DNSSEC question Hi, We are using DNSSEC on the internal network (Windows 2022 DNS server / 172.16.4.10). Recently I cam

the chrome extension is irrelevant, i only mentioned it to show that DNSSEC is enabled. I may have figured it out, AD t

it's ourdomain.local truncated to hide the identity

DNSSEC question Hi, We are using DNSSEC on the internal network (Windows 2022 DNS server / 172.16.4.10). Recently I cam

DNSSEC question Hi, We are using DNSSEC on the internal network (Windows 2022 DNS server / 172.16.4.10). Recently I cam

is MTU set to 9000 on both A and B hosts?

you don't need to capture the payload, limit your capture buffer to be slightly larger than the packet header.

You are getting almost wirespeed when you are testing A->C (984Mbps) A Hardware: 11th Gen Intel(R) Core(TM) i5-113

this would give you a general idea where it's from, but will not pinpoint the exact location https://wiki.wireshark.org/

yes, defaults are fine. -s for server -c for client

What Windows OS is being used on a server where HFS is installed / running? Can you also run iperf between hosts A and B

Upload_from_10.10.10.2-Capture_from_10.10.10.2.pcapng - 3 way handshake isn't captured Looks like this is the HTTP ser

hi If you plug in Host C in to the same switch where Host A is connected are you able to reproduce the problem? can you

Windows 11. Microsoft Surface Laptops

arm64 and Wireshark Hi, Looking at some new laptops with a Snapdragon CPU, is ARM64 installer a native Wireshark app fo

arm64 and Wireshark Hi, Looking at some new laptops with a Snapdragon CPU, is ARM64 installer a native Wireshark app fo

this was the case where wireshark was showing the results of OS tweaks but not pinpointing to what exactly was changed.