search for: interfacealia

...------------------------------------------------------------------ Set-PSDebug -Trace 1 # Wait for the netkvm (virtio-net) driver to become active. $adapters = @() While (-Not $adapters) { Start-Sleep -Seconds 5 $adapters = (Get-NetAdapter | Where DriverFileName -eq "netkvm.sys").InterfaceAlias | Sort-Object Write-Host "adapters = '$adapters'" } New-NetIPAddress -InterfaceAlias $adapters[0] -IPAddress "10.0.2.15" -DefaultGateway "10.0.2.2" -PrefixLength 8 Set-DnsClientServerAddress -InterfaceAlias $adapters[0] -ServerAddresses ("10.0.2.3&qu...

...ws 2019 and a new samba-ad-dc - and get the same issues. Which ports need to be accessable via network? Till now I checked (on the Win2019 system) by using Powershell: Test-netconnection 192.168.178.5 -port 53 ComputerName : 192.168.178.5 RemoteAddress : 192.168.178.5 RemotePort : 53 InterfaceAlias : Ethernet SourceAddress : 192.168.178.40 TcpTestSucceeded : True Test-netconnection 192.168.178.5 -port 88 - success (like above) Test-netconnection 192.168.178.5 -port 135 - success Test-netconnection 192.168.178.5 -port 138 - FAILS Test-netconnection 192.168.178.5 -port 139 - success Test...

On Fri, 5 Jan 2024 08:30:15 +0100 lists--- via samba <samba at lists.samba.org> wrote: > Good morning Rowland, > > is it ok for you to send you the complete, not sanitized installation > description? > ... I'm lost in getting the samba-ad-dc running ... I think you mean, Can I send you my unsanitised files ? If so, then yes, just send them to rpenny at samba dot org

...d-dc - and get the same issues. > > Which ports need to be accessable via network? > Till now I checked (on the Win2019 system) by using Powershell: > Test-netconnection 192.168.178.5 -port 53 > ComputerName : 192.168.178.5 > RemoteAddress : 192.168.178.5 > RemotePort : 53 > InterfaceAlias : Ethernet > SourceAddress : 192.168.178.40 > TcpTestSucceeded : True > > Test-netconnection 192.168.178.5 -port 88 - success (like above) > Test-netconnection 192.168.178.5 -port 135 - success > Test-netconnection 192.168.178.5 -port 138 - FAILS > Test-netconnection 192.168.1...

This patch is just for discussion. There are still a couple of issues that I'm trying to fix. One is that all of the test guests I have, even ones with static IPs, have multiple interfaces, some using DHCP, so the conditions for adding the Powershell script don't kick in. This makes testing very awkward. However a bigger issue is that I think the premise is wrong. In some registries