The situation when the application WO Mic A "fail to connect to server" error when attempting a wireless connection is one of the most common problems among users trying to turn their smartphone into a high-quality microphone for their PC. This error message indicates that the client program on the computer cannot "see" the server application on the phone over the local network, even though both devices are formally connected to the same router.
The reasons for such a disconnection can be hidden in a variety of layers of the network architecture: from a banal mismatch of IP addresses to strict rules Windows Firewall, blocking incoming connections. Users often forget that modern operating systems perceive any new network request as a potential security threat, especially if the network is marked as "public."
In this guide, we'll detail the diagnostic and troubleshooting process so you can ensure stable, lag-free audio transmission. Understanding the operating principles TCP/IP protocols within your local network will help not only fix the current error, but also prevent it from occurring in the future when changing network settings.
Checking the basic network configuration
The first and most critical step is to verify that both devices are actually on the same network segment. Error WO Mic fail to connect This often occurs when the computer is connected to the router's guest network and the phone is connected to the main network, or when one of the devices is using mobile 4G/5G Internet instead of Wi-Fi.
You need to make sure that discovery is enabled on both devices. In Windows settings, this may be called "Make this PC discoverable," and in your router settings, it may be called AP Isolation (Access Point Isolation), which must be disabled. When enabled, the router physically prevents devices within the network from exchanging data packets with each other.
- 📱 Check what's on your phone in the app WO Mic The IP address starting with the prefix is displayed
192.168.or10., and not127.0.0.1. - 💻 Make sure the network type in Windows is set to "Private" and not "Public" to allow local discovery.
- 🔄 Reboot your router if the list of connected devices exceeds the standard DHCP server limit.
⚠️ Important: If you're using a corporate or dorm network, your administrator may have disabled client-to-client blocking. In this case, the wireless connection won't work regardless of your settings.
It's also worth paying attention to the frequency range. If your router broadcasts two networks (2.4 GHz and 5 GHz) with different names (SSIDs), make sure both devices are connected to the same one. While modern routers can forward traffic between bands, some budget models can create isolated subnets.
Setting up a firewall and antivirus
The most likely reason why WO Mic The "fail to connect" error message indicates that the application's port is blocked by Windows Firewall or a third-party antivirus. When you first launched the server component on your PC, the system should have requested permission to access the network, but if you accidentally clicked "Cancel" or "Deny," the connection will be blocked.
To fix this, you need to manually add an exception rule. Go to the firewall control panel and select "Allow an application to communicate." Find it in the list. womicserver.exe and make sure that the boxes next to the network types "Private" and "Public" are checked.
If a simple permission isn't enough, you'll need to create a manual inbound rule. This is especially true for users Kaspersky, ESET or Dr.Web, which have their own firewalls that ignore the standard Windows settings.
netsh advfirewall firewall add rule name="WO Mic Server" dir=in action=allow program="C:\Program Files (x86)\WO Mic\womicserver.exe" enable=yesRunning this command in the command prompt with administrator privileges will forcefully open the required port. Afterwards, try restarting the server and checking the connection status on the client.
- 🛡️ Temporarily disable your antivirus to check: if the connection appears, then the problem lies with the antivirus's firewall settings.
- 🔓 Check if your firewall is blocking the port specified in the application settings (by default)
46784). - 📂 Make sure that the path to the executable file in the firewall rules matches the actual location of the program files.
Static IP problem and address change
One of the most insidious causes of connection errors is the dynamic change of the phone's IP address. Protocol DHCP, which distributes addresses on the network, can give your smartphone a new IP address after the router reboots or the lease time expires.
If you entered the old IP address into the client program on your PC, and your phone received a new one, the connection will naturally fail. The app will try the old address, which may already be occupied by another device or be empty.
The solution is to set a static IP address directly on the phone itself in the Wi-Fi settings. This ensures that the device's address on the local network will always remain constant, and you won't have to change the settings in the client. WO Mic on the computer.
| Parameter | Recommended value | Description |
|---|---|---|
| IP address | 192.168.1.150 | Address outside the DHCP range (e.g. above 100) |
| Gateway | 192.168.1.1 | Your router's address |
| Subnet mask | 255.255.255.0 | Standard mask for home networks |
| DNS 1 | 8.8.8.8 | Google DNS (for stability) |
After setting a static address, be sure to restart the application. WO Mic on your phone so it updates the information in the interface. Now you can enter this fixed address into the client settings on your PC and forget about the problem of changing IP addresses.
Port conflicts and application settings
By default server WO Mic uses the port 46784If this port is occupied by another application or blocked, a connection error will occur. While such situations are rare, they are possible when using specific streaming software or Android emulators.
You can change the listening port in the server settings on your PC. Go to WO Mic Client, go to the menu Transport and select Settings. Change the port number to any other from the high port range (for example, 50000), but don't forget to specify the same port in the settings on your phone.
It's also worth checking the transfer protocol. The app supports TCP And UDPTCP is more reliable because it guarantees packet delivery, but it can introduce significant latency. UDP is faster, but packets can be lost. If your connection is unstable, try switching protocols in the settings.
- 🔢 Try changing the port to
46785or8080, if the standard one doesn't work. - 📡 Switch from Wi-Fi to a USB cable for testing: if it works via cable, the problem is definitely with the network.
- 📉 Reduce the audio bitrate in the quality settings if the channel is narrow and packets are being lost.
⚠️ Important: When changing the port or protocol, the settings must be identical on both the server (PC) and the client (Phone). A single character mismatch will result in a "fail to connect" error.
Diagnostics via Ping and Telnet
For a deep diagnosis of the problem, when visual settings do not help, you need to use the built-in Windows tools. Command ping This will allow you to check the phone's physical network availability. Open the command prompt (cmd) and enter the phone's IP address.
If you see the response "Request timed out," it means the computer doesn't physically see the phone. This could be due to port isolation on the router or the wrong subnet. If you see the response "Reply from...," it means the network is working, and the problem is software blocking the port.
To check the port specifically, you can use the utility telnet (must be enabled in Windows Features) or PowerShell Command Test-NetConnection -ComputerName 192.168.1.X -Port 46784 will show whether the port is open for connection.
Test-NetConnection -ComputerName 192.168.1.55 -Port 46784Result TcpTestSucceeded: True means that the path is open and the application is ready to work. If False, this means that the connection is blocked at the OS or antivirus level, even if the ping is successful.
What to do if Telnet is not installed?
In Windows 10 and 11, the Telnet Client component is disabled by default. To enable it, go to "Control Panel" → "Programs and Features" → "Turn Windows features on or off" and check the box next to "Telnet Client." After a reboot, you will be able to use the telnet command.
Alternative connection methods
If you still can't set up a Wi-Fi connection due to limitations of your corporate network or router, there are always alternatives. The most stable of these is connecting via USB cable.
USB mode eliminates any issues with IP addresses, packet loss, and signal interference. It requires USB debugging enabled on your phone (for Android) or ADB drivers installed. This ensures maximum data transfer speed and minimal latency.
You can also use the mode BluetoothIf sound quality isn't critical, Bluetooth offers lower bandwidth, so audio may be more compressed, but the connection is easier and doesn't require network configuration.
- 🔌 USB: Better sound quality and no lag, cable required.
- 🔵 Bluetooth: Convenient without wires, but the sound may be mono or low quality.
- 🌐 Wi-Fi: Good balance, but requires proper network configuration.
☑️ WO Mic connection diagnostics
Frequently Asked Questions (FAQ)
Why doesn't WO Mic see my phone even though both are connected to the same Wi-Fi?
Most likely, the "AP Isolation" or "Client Isolation" feature is enabled on your router, which prevents devices from seeing each other. Also, check whether one of the devices is using a 4G mobile network instead of Wi-Fi, and make sure Windows Firewall isn't blocking the connection.
What port does WO Mic use by default?
The standard port for the WO Mic server is 46784If it is busy or blocked by your ISP/router, you can change it in the app settings (Transport -> Settings section) to any free port, for example, 50000.
Can WO Mic be used over the internet (not local Wi-Fi)?
The standard version of the app is designed for use on a local area network (LAN). Connecting via the internet (WAN) requires complex port forwarding configuration on the router and the use of a public IP address, which is not recommended for security reasons.
Why does the sound cut out or have a delay?
Latency is typical for wireless connections. Try lowering the bitrate in the WO Mic quality settings, moving your phone closer to the router, or switching to a 5 GHz network. For professional work with minimal latency, use a USB cable.