← All investigations
Network scanNmapWindowsSMB

Two end-of-life Windows machines and an exposed VNC login on a five-host lab network

I scanned 10.71.2.0/24 and found Windows XP and Windows 7 still answering on SMB and RDP.

Jack McCullough · 40 sec scan
Tools
  • Nmap7.99

What I found

IPs scanned 256
Hosts up 5
Scan time 40.48s
Nmap version 7.99

Five hosts answered: three Windows lab machines (10, XP and 7), one Cisco device with a web interface, and the Linux box I scanned from. Two of the Windows systems run operating systems that no longer get security updates, and all three expose SMB and RDP.

Hosts at a glance

IPRoleOS detectedOpen portsRisk
10.71.2.101Windows 10 lab hostWindows 10 (1709–22H2)7Medium
10.71.2.102Windows XP lab hostWindows XP SP2/SP34High
10.71.2.106Windows 7 lab hostWindows 7 / Embedded Std 76High
10.71.2.254Cisco gateway / deviceCisco IOS (no exact match)3Low
10.71.2.20Scanner (0 hops)Linux (Debian)2Info

Host by host

10.71.2.101

Windows 10 · VMware · 00:50:56:81:B2:1C · 0.00019s latency · 93 closed ports
Medium
PortServiceVersion / notes
135/tcpmsrpcMicrosoft Windows RPC
139/tcpnetbios-ssnMicrosoft Windows NetBIOS
445/tcpmicrosoft-dsSMB
3389/tcpms-wbt-serverRemote Desktop
5357/tcphttpMicrosoft HTTPAPI 2.0 (SSDP/UPnP)
5800/tcpvnc-httpTightVNC, user [redacted]
5900/tcpvncVNC protocol 3.8

VNC and RDP are both exposed, and the TightVNC banner gives away a username.

nmap · 10.71.2.101
5800/tcp open  vnc-http  TightVNC (user: [redacted]; VNC TCP port: 5900)

10.71.2.102

Windows XP SP2/SP3 · VMware · 00:50:56:81:39:AB · 0.00018s latency · 96 closed ports
High
PortServiceVersion / notes
135/tcpmsrpcMicrosoft Windows RPC
139/tcpnetbios-ssnMicrosoft Windows NetBIOS
445/tcpmicrosoft-dsWindows XP SMB
3389/tcpms-wbt-serverRemote Desktop

Windows XP is long past end of life and gets no security updates.

SMB and RPC on an unpatched XP system are typically open to well-known remote exploits; I would verify before concluding.

10.71.2.106

Host name redacted · VMware · 00:50:56:81:1D:90 · 0.00019s latency · 94 filtered ports
High
PortServiceVersion / notes
135/tcpmsrpcMicrosoft Windows RPC
139/tcpnetbios-ssnMicrosoft Windows NetBIOS
445/tcpmicrosoft-dsWindows 7–10 SMB (workgroup: WORKGROUP)
554/tcprtsp?Unconfirmed service
3389/tcpms-wbt-serverRemote Desktop
5357/tcphttpMicrosoft HTTPAPI 2.0 (SSDP/UPnP)

Windows 7 is end of life. Nmap flagged its OS detection as unreliable because it found no closed port, so treat the OS as a best guess.

Most ports are filtered, which points to an active host firewall. Port 554 (RTSP) is unexpected on a lab workstation.

10.71.2.254

Cisco device · 70:B3:17:E5:61:FA · 0.0014s latency · 97 closed ports
Low
PortServiceVersion / notes
22/tcpsshCisco SSH 1.25 (protocol 2.0)
80/tcphttpOpenResty web app server
443/tcpssl/httpOpenResty web app server

Management runs over SSH and HTTPS, but plain HTTP on port 80 is open too. I would confirm it only redirects to HTTPS.

10.71.2.20

Scanning host (0 hops) · Linux · 98 filtered ports
Info
PortServiceVersion / notes
22/tcpsshOpenSSH 10.3p1 Debian 4 (protocol 2.0)
5900/tcpvncVNC protocol 3.8

The OS fingerprint was inconclusive; the best guesses were various Linux kernels.

Key findings

  • HighTwo end-of-life Windows systems (XP at .102, 7 at .106) are reachable on SMB and RDP.
  • MediumSMB (445) and RDP (3389) are open on all three Windows hosts.
  • MediumVNC is exposed on .101 and the TightVNC banner discloses a username.
  • LowThe Cisco device at .254 serves HTTP, HTTPS and SSH.

What I would do next

  1. Retire or isolate the XP and Windows 7 hosts and segment them from everything else.
  2. Restrict RDP, SMB and VNC to the sources that need them, and require network-level authentication for RDP.
  3. Disable or firewall VNC on .101 if it is not needed, or tunnel it over SSH or a VPN.
  4. Confirm the Cisco device redirects HTTP to HTTPS and limit management access to trusted addresses.
  5. Follow up with a vulnerability scan (Nmap NSE scripts or a dedicated scanner) to confirm which weaknesses actually apply.

Every article is human-written, not AI-generated.