Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Can't ping, traceroute, access host with pfSense as a VM

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 1 Posters 1.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • F
      fly
      last edited by

      Hi guys,

      I've installed pfSense as a VM under Virtualbox on a Windows 7 host.

      pfSense has its own dedicated NIC with 2 ports (1 x WAN, 1 x LAN) - LAN is connected to the switch and so is Windows 7's NIC (it's a twin dual-port NIC machine).

      I can ping all other 192.168.1.* machines/access internet/tracert from Windows 7 but I cannot access Windows 7 resources (files, RDP) from any other computer connected to the switch.

      Anybody know what went wrong? I only downloaded VBox, pfSense i386, installed both, added Squid package with transparent proxy and that's literally it.

      ALL computers can access internet fine. ALL cabling has been verified and is correct (ADSL modem <–- WAN_pfSense_LAN, Win7_LAN ---> Switch <--- other computers).

      Thanks!

      1 Reply Last reply Reply Quote 0
      • F
        fly
        last edited by

        Figured this one out.

        Somehow pfSense's WAN interface became Private network under Windows however both, pfSense's and Windows' LAN interfaces were 'Guest or public networks'. Naturally, Windows restricts access to files on public networks and changing network profile from public to private solves all issues at once!

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.