Problema con el teletransporte de Wi-Fi Unifi en PC
Problema con el teletransporte de Wi-Fi Unifi en PC
Hi everyone, I'm trying to set up Unifi Wifiman to link with another site that uses a UDM Pro. So far, connecting via Android on my mobile works fine—WiFi, SMB using name and IP, and browsing/copying files is smooth. However, when I install the desktop version on my PC, it shows the remote location's IP address, but I can't access SMB services or connect to anything beyond web pages like an IIS server or RDP. I'm on Windows 10. Anyone has faced this problem or found a solution?
Windows is configured to permit SMB shares only on local subnets by default. Teleport generates an extended subnet, which differs from your standard setup. In the Unifi app/web account, you’ll notice the teleport client displays an IP like 192.168.2.#, while your primary subnet appears as 192.168.1.# unless you adjusted it. To resolve this:
1) Open Windows Defender Firewall with Advanced Security on the host machine
2) Navigate to Inbound Rules
3a) Search for "File and Printer Sharing (SMB in)" – expect three options (Public, Private, Domain)
3b) Add your subnet to either Public or Private based on your network configuration
4) In the Scope tab, ensure "Remote IP Address" is selected
5) Enter your teleport’s subnet in the "IP Address" field: use a 0/24 mask (e.g., 192.168.2.0/24) to allow any device to connect via SMB
6a) Confirm the entry and click apply
This should resolve connectivity issues. I’ve attached a sample teleport subnet for reference.
Sorry, I'm also using Bitdefender on both devices. I might need to make some adjustments there too.
The device that manages file and folder shares is called a host. It keeps the files accessible across different systems. You must perform this action only on the host machine. The teleporting device requires just its IP address to identify the network segment.
It seems the problem was related to Bitdefender firewall. Disabling it helped me access SMB through the host PC. I followed specific steps and now can reach the IP, but I still can't connect via the PC name. Do you think Windows needs guidance on checking subnets? I can show how it works on an Android device. Steps include: applying rules for all apps, setting permissions, choosing network type, protocol, direction, showing advanced settings, hiding local address, enabling remote address, using IP 192.168.1.15 or a range, and leaving port fields blank.
I checked the setup process. The new subnet was supposed to accept it right away. Please confirm where you placed the firewall rule—Windows, router, or another device.
Reviewed the Windows firewall configuration, but it didn’t resolve the issue since AV handles firewall rules. Updated the rule in AV as mentioned in the prior post—now SMB access works through IP addresses, which is significantly improved. Currently, I can only connect via PC name. What I learned suggests that using a full VPN such as L2TP is necessary for PC names to function properly.