shadow1ng/fscan · error

netbios_info_not_found

Error message

netbios_info_not_found

What it means

Guard in NetBIOSPlugin.Scan: the query completed but the returned NetBIOSInfo has Valid=false, meaning the response could not be parsed into usable names (empty or unparseable payload). The scan reports the lookup as unsuccessful rather than partial data.

Source

Thrown at plugins/services/netbios.go:71

		netbiosInfo, err = p.queryNetBIOSNames(info.Host, config, state)
	} else {
		// TCP端口139 - NetBIOS会话服务
		netbiosInfo, err = p.queryNetBIOSSession(ctx, info.Host, session)
	}

	if err != nil {
		return &ScanResult{
			Success: false,
			Service: "netbios",
			Error:   err,
		}
	}

	if !netbiosInfo.Valid {
		return &ScanResult{
			Success: false,
			Service: "netbios",
			Error:   fmt.Errorf("%s", i18n.GetText("netbios_info_not_found")),
		}
	}

	// 记录NetBIOS发现信息
	msg := fmt.Sprintf("NetBios %s", target)
	if netbiosInfo.Summary() != "" {
		msg += fmt.Sprintf(" %s", netbiosInfo.Summary())
	}
	session.LogSuccess(msg)

	return &ScanResult{
		Success: true,
		Type:    plugins.ResultTypeService,
		Service: "netbios",
		Banner:  netbiosInfo.Summary(),
	}
}

View on GitHub (pinned to 95cc12e753)

Solutions

  1. Verify the host actually runs NetBIOS services
  2. Capture the raw UDP/TCP response to see why parsing marked it invalid
  3. Retry: name-service responses are occasionally lost or truncated over UDP
Defensive patterns

Strategy: retry

When it happens

Trigger: Thrown at plugins/services/netbios.go:71 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of shadow1ng/fscan@95cc12e753 (2026-09-06). Data as JSON: /api/errors/a885ae1afac1602d. Report an issue: GitHub.