home.social

#netbios — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #netbios, aggregated by home.social.

  1. #ISP​s die aktiv #NetBIOS und #SMB (aber nur auf IPv4) blockieren können gerne verrecken. *hust*O2*hust*

    Und #AVM, die das standardmäßig in der #FritzBox aktivieren, kann gleich hinterher.

  2. #ISP​s die aktiv #NetBIOS und #SMB (aber nur auf IPv4) blockieren können gerne verrecken. *hust*O2*hust*

    Und #AVM, die das standardmäßig in der #FritzBox aktivieren, kann gleich hinterher.

  3. Microsoft confirmed WINS will be removed from Windows Server releases following Server 2025, with support ending in November 2034. Organizations relying on NetBIOS name resolution are advised to audit dependencies and migrate to DNS/DNSSEC, conditional forwarders, or split-brain DNS.

    This is an important long-term planning moment for IT and security teams maintaining older environments.

    Source: bleepingcomputer.com/news/micr

    Follow @technadu for more clear, unbiased coverage.

    #WindowsServer #DNS #WINS #NetBIOS #CyberSecurity #NetworkSecurity #ITAdmin #ServerOps #Microsoft #DNSSEC #TechUpdates

  4. Microsoft confirmed WINS will be removed from Windows Server releases following Server 2025, with support ending in November 2034. Organizations relying on NetBIOS name resolution are advised to audit dependencies and migrate to DNS/DNSSEC, conditional forwarders, or split-brain DNS.

    This is an important long-term planning moment for IT and security teams maintaining older environments.

    Source: bleepingcomputer.com/news/micr

    Follow @technadu for more clear, unbiased coverage.

    #WindowsServer #DNS #WINS #NetBIOS #CyberSecurity #NetworkSecurity #ITAdmin #ServerOps #Microsoft #DNSSEC #TechUpdates

  5. Microsoft confirmed WINS will be removed from Windows Server releases following Server 2025, with support ending in November 2034. Organizations relying on NetBIOS name resolution are advised to audit dependencies and migrate to DNS/DNSSEC, conditional forwarders, or split-brain DNS.

    This is an important long-term planning moment for IT and security teams maintaining older environments.

    Source: bleepingcomputer.com/news/micr

    Follow @technadu for more clear, unbiased coverage.

    #WindowsServer #DNS #WINS #NetBIOS #CyberSecurity #NetworkSecurity #ITAdmin #ServerOps #Microsoft #DNSSEC #TechUpdates

  6. I've commented before how these two #Microsoft #Win11 machines can see everything on my lan ... except each other 🤦‍♂️

    #CoPilot tells me this is a known issue and I can either activate #smb1 protocol 😱 or perform a simple 7-step work around, 🤔 basically enabling #netbios over #TCP

    Wrapping a non-error-correcting protocol inside an error-correcting protocol, for you non-nerds 🤓 instead of using an error-correcting protocol alone, b/c someone just can't say goodbye to #novel #netware🦕💩🧟‍♂️

    #1995

  7. I've commented before how these two #Microsoft #Win11 machines can see everything on my lan ... except each other 🤦‍♂️

    #CoPilot tells me this is a known issue and I can either activate #smb1 protocol 😱 or perform a simple 7-step work around, 🤔 basically enabling #netbios over #TCP

    Wrapping a non-error-correcting protocol inside an error-correcting protocol, for you non-nerds 🤓 instead of using an error-correcting protocol alone, b/c someone just can't say goodbye to #novel #netware🦕💩🧟‍♂️

    #1995

  8. I've commented before how these two #Microsoft #Win11 machines can see everything on my lan ... except each other 🤦‍♂️

    #CoPilot tells me this is a known issue and I can either activate #smb1 protocol 😱 or perform a simple 7-step work around, 🤔 basically enabling #netbios over #TCP

    Wrapping a non-error-correcting protocol inside an error-correcting protocol, for you non-nerds 🤓 instead of using an error-correcting protocol alone, b/c someone just can't say goodbye to #novel #netware🦕💩🧟‍♂️

    #1995

  9. #NetBIOS, #Windows LAN-Manager ist eine Technologie aus dem Jahr 1983, die in modernisierter Form immer noch zum Einsatz kommt, wenn man auf freigegebene Windows-Laufwerke zugreift.

    Werde einfach nicht verstehen und akzeptieren, dass diese Technologie auch heute noch unerträglich langsam und unzuverlässig ist, obwohl inzwischen selbst einfachste DSL-Verbindungen von zu Hause absolut besser und schneller sind, als jedes High-End-Netzwerk von 1983.

  10. #NetBIOS, #Windows LAN-Manager ist eine Technologie aus dem Jahr 1983, die in modernisierter Form immer noch zum Einsatz kommt, wenn man auf freigegebene Windows-Laufwerke zugreift.

    Werde einfach nicht verstehen und akzeptieren, dass diese Technologie auch heute noch unerträglich langsam und unzuverlässig ist, obwohl inzwischen selbst einfachste DSL-Verbindungen von zu Hause absolut besser und schneller sind, als jedes High-End-Netzwerk von 1983.

  11. #NetBIOS, #Windows LAN-Manager ist eine Technologie aus dem Jahr 1983, die in modernisierter Form immer noch zum Einsatz kommt, wenn man auf freigegebene Windows-Laufwerke zugreift.

    Werde einfach nicht verstehen und akzeptieren, dass diese Technologie auch heute noch unerträglich langsam und unzuverlässig ist, obwohl inzwischen selbst einfachste DSL-Verbindungen von zu Hause absolut besser und schneller sind, als jedes High-End-Netzwerk von 1983.

  12. #NetBIOS, #Windows LAN-Manager ist eine Technologie aus dem Jahr 1983, die in modernisierter Form immer noch zum Einsatz kommt, wenn man auf freigegebene Windows-Laufwerke zugreift.

    Werde einfach nicht verstehen und akzeptieren, dass diese Technologie auch heute noch unerträglich langsam und unzuverlässig ist, obwohl inzwischen selbst einfachste DSL-Verbindungen von zu Hause absolut besser und schneller sind, als jedes High-End-Netzwerk von 1983.

  13. When #windows decides it's had enough of you blocking it's update/telemetry processes (going to wd-prod-cp-us-west-2-fe\.westus.cloudapp.azure.com) and just yeats out the lookup over #netbios 🤷

  14. When #windows decides it's had enough of you blocking it's update/telemetry processes (going to wd-prod-cp-us-west-2-fe\.westus.cloudapp.azure.com) and just yeats out the lookup over #netbios 🤷

  15. When #windows decides it's had enough of you blocking it's update/telemetry processes (going to wd-prod-cp-us-west-2-fe\.westus.cloudapp.azure.com) and just yeats out the lookup over #netbios 🤷

  16. When #windows decides it's had enough of you blocking it's update/telemetry processes (going to wd-prod-cp-us-west-2-fe\.westus.cloudapp.azure.com) and just yeats out the lookup over #netbios 🤷

  17. When #windows decides it's had enough of you blocking it's update/telemetry processes (going to wd-prod-cp-us-west-2-fe\.westus.cloudapp.azure.com) and just yeats out the lookup over #netbios 🤷

  18. After discovering that NetBIOS settings aren’t available in #intune #settings - and therefore require disablement by script (or GPO) I raised the query with #microsoft - adding the support natively in intune would allow us to use config refresh to ensure that this remains disabled.

    In the interim, I have created a #script (+ Detection) to disable this, and will have to look into a custom #compliance #policy to ensure that this is disabled across the estate.

    If this sounds useful to you, I have open sourced my #netbios and #llmnr disablement script here:

    github.com/Marshyp/Security-Sc

  19. After discovering that NetBIOS settings aren’t available in #intune #settings - and therefore require disablement by script (or GPO) I raised the query with #microsoft - adding the support natively in intune would allow us to use config refresh to ensure that this remains disabled.

    In the interim, I have created a #script (+ Detection) to disable this, and will have to look into a custom #compliance #policy to ensure that this is disabled across the estate.

    If this sounds useful to you, I have open sourced my #netbios and #llmnr disablement script here:

    github.com/Marshyp/Security-Sc

  20. Anyway, I did what any underpaid college dropout would do:
    • ask #IT for a few extra PCs on the LAN
    • distribute the #cellular tower data across #Microsoft #Excel workbooks, one per machine
    • write some glue macros to exchange data (probably using Network #DDE or #OLEAutomation)
    • babysit the PCs as they inevitably crashed every few hours due to #Windows' flaky cooperative multitasking and its #NetBIOS Frames (then called #NetBEUI) networking protocol (6/6)

  21. Anyway, I did what any underpaid college dropout would do:
    • ask #IT for a few extra PCs on the LAN
    • distribute the #cellular tower data across #Microsoft #Excel workbooks, one per machine
    • write some glue macros to exchange data (probably using Network #DDE or #OLEAutomation)
    • babysit the PCs as they inevitably crashed every few hours due to #Windows' flaky cooperative multitasking and its #NetBIOS Frames (then called #NetBEUI) networking protocol (6/6)

  22. Anyway, I did what any underpaid college dropout would do:
    • ask #IT for a few extra PCs on the LAN
    • distribute the #cellular tower data across #Microsoft #Excel workbooks, one per machine
    • write some glue macros to exchange data (probably using Network #DDE or #OLEAutomation)
    • babysit the PCs as they inevitably crashed every few hours due to #Windows' flaky cooperative multitasking and its #NetBIOS Frames (then called #NetBEUI) networking protocol (6/6)

  23. Anyway, I did what any underpaid college dropout would do:
    • ask #IT for a few extra PCs on the LAN
    • distribute the #cellular tower data across #Microsoft #Excel workbooks, one per machine
    • write some glue macros to exchange data (probably using Network #DDE or #OLEAutomation)
    • babysit the PCs as they inevitably crashed every few hours due to #Windows' flaky cooperative multitasking and its #NetBIOS Frames (then called #NetBEUI) networking protocol (6/6)

  24. Anyway, I did what any underpaid college dropout would do:
    • ask #IT for a few extra PCs on the LAN
    • distribute the #cellular tower data across #Microsoft #Excel workbooks, one per machine
    • write some glue macros to exchange data (probably using Network #DDE or #OLEAutomation)
    • babysit the PCs as they inevitably crashed every few hours due to #Windows' flaky cooperative multitasking and its #NetBIOS Frames (then called #NetBEUI) networking protocol (6/6)

  25. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 653cdcf28b0616bd82137cfd
    Pulse Link: otx.alienvault.com/pulse/653cd
    Pulse Author: BotnetExposer
    Created: 2023-10-28 10:05:38

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #Ios #Tcp #NETBIOS #BotnetExposer

  26. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 653c345e5ed3922166cc38fe
    Pulse Link: otx.alienvault.com/pulse/653c3
    Pulse Author: BotnetExposer
    Created: 2023-10-27 22:06:22

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #Ios #Tcp #NETBIOS #BotnetExposer

  27. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 653b8b782a6ea809d0d30160
    Pulse Link: otx.alienvault.com/pulse/653b8
    Pulse Author: BotnetExposer
    Created: 2023-10-27 10:05:44

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #Ios #Tcp #NETBIOS #BotnetExposer

  28. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 6538e874c8ea37bffc8e981f
    Pulse Link: otx.alienvault.com/pulse/6538e
    Pulse Author: BotnetExposer
    Created: 2023-10-25 10:05:40

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #Ios #Tcp #NETBIOS #BotnetExposer

  29. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 65383fb38a6fe753fc415666
    Pulse Link: otx.alienvault.com/pulse/65383
    Pulse Author: BotnetExposer
    Created: 2023-10-24 22:05:39

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #Ios #Tcp #NETBIOS #BotnetExposer

  30. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 653796e952a9e6f5fa07e953
    Pulse Link: otx.alienvault.com/pulse/65379
    Pulse Author: BotnetExposer
    Created: 2023-10-24 10:05:29

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #iOS #TCP #NETBIOS #BotnetExposer

  31. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 6536ee2465e0424aa16717a2
    Pulse Link: otx.alienvault.com/pulse/6536e
    Pulse Author: BotnetExposer
    Created: 2023-10-23 22:05:24

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #iOS #TCP #NETBIOS #BotnetExposer

  32. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 6536ee2465e0424aa16717a2
    Pulse Link: otx.alienvault.com/pulse/6536e
    Pulse Author: BotnetExposer
    Created: 2023-10-23 22:05:24

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #iOS #TCP #NETBIOS #BotnetExposer

  33. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 65364554fd7656f77b712892
    Pulse Link: otx.alienvault.com/pulse/65364
    Pulse Author: BotnetExposer
    Created: 2023-10-23 10:05:08

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #iOS #TCP #NETBIOS #BotnetExposer

  34. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 6533a2571b674fe17a362eae
    Pulse Link: otx.alienvault.com/pulse/6533a
    Pulse Author: BotnetExposer
    Created: 2023-10-21 10:05:11

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #iOS #TCP #NETBIOS #BotnetExposer

  35. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 65344b13ad26e2ebdf30b652
    Pulse Link: otx.alienvault.com/pulse/65344
    Pulse Author: BotnetExposer
    Created: 2023-10-21 22:05:07

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #iOS #TCP #NETBIOS #BotnetExposer

  36. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 6534f3c4f94db1f37724d54b
    Pulse Link: otx.alienvault.com/pulse/6534f
    Pulse Author: BotnetExposer
    Created: 2023-10-22 10:04:52

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #iOS #TCP #NETBIOS #BotnetExposer

  37. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 65359c98cb33b1a84d58cfe1
    Pulse Link: otx.alienvault.com/pulse/65359
    Pulse Author: BotnetExposer
    Created: 2023-10-22 22:05:12

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #iOS #TCP #NETBIOS #BotnetExposer

  38. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 6534f3c4f94db1f37724d54b
    Pulse Link: otx.alienvault.com/pulse/6534f
    Pulse Author: BotnetExposer
    Reference(s):
    Created: 2023-10-22 10:04:52

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #iOS #TCP #NETBIOS #BotnetExposer

  39. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 6534f3c4f94db1f37724d54b
    Pulse Link: otx.alienvault.com/pulse/6534f
    Pulse Author: BotnetExposer
    Reference(s):
    Created: 2023-10-22 10:04:52

    Be advised, this data is unverified and should be considered preliminary. Always do further verification.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #iOS #TCP #NETBIOS #BotnetExposer

  40. Scan port 139 NETBIOS (S3#)

    Scans hitting the server at TCP port 139 NETBIOS. Same IP should not appear more than once in 96 hours in our lists S3#.

    Pulse ID: 65344b13ad26e2ebdf30b652
    Pulse Link: otx.alienvault.com/pulse/65344
    Created: 2023-10-21 22:05:07

    Be advised, this data is unverified and should be considered preliminary. Do not make any decisions based on information posted by this bot. Always verify information coming from OTX.

    #OTX #OpenThreatExchange #InfoSec #bot #CyberSecurity #iOS #TCP #NETBIOS