Note: Please do not post Personally Identifiable Information like email address, personal phone number, physical home address, product key etc.
Issue abstract: Since upgrading from V22 to V24, VPN connects but does not receive a Virtual IP address. Access to the internet is blocked without the virtual IP.
Detailed description: Prior to the upgrade, the VPN worked. The PC in question is running Windows 10. I have run Live Update. I have tried the troubleshooting utility and the remove and reinstall utility. I have deleted and reinstalled the WAN Miniport drivers. I have tried all of the different VPN regions. I have set DNS to look at 8.8.8.8 and 1.1.1.1 (and the IPV6 equivalents). I have restarted the pc. I have flushed the DNS cache. I have tried setting the metric to 15. Nothing seems to resolve the issue. Why does the VPN “connect” but not receive a virtual IP?
Product & version number:Norton 360 Deluxe, current version of 24
OS details: Windows 10
What is the error message you are seeing? VPN says connected, Virtual IP says n/a, VPN disconnects and tries again every 30 seconds.
If you have any supporting screenshots, please add them:
I have the same issue on my Norton Secure VPN. I use Norton 360 and Norton Ultimate also, and all my subscriptions are ok. I sometimes receive Virtual IP, but 30% of the time I can not. Restarting, etc does not help.
My laptop just updated to V25. The issue, no Virtual IP assigned, persists.
All: Disable netbios on your internet adapters and reboot as a test.
AI Overview
Learn more
[image]
To disable NetBIOS over TCP/IP in Windows, you can use the Control Panel or PowerShell.
Using the Control Panel
-
Open the Control Panel
-
Go to Network and Internet
-
Go to Network and Sharing Center
-
Click Change adapter settings
-
Right-click Local Area Connection
-
Click Properties
-
Select Internet Protocol Version 4 (TCP/IPv4)
-
Click Properties
-
Click Advanced
-
Click the WINS tab
-
Click Disable NetBIOS over TCP/IP
-
Click OK
SA
tried the solution above, didn’t work 
I tried it as well, while it didn’t work, other changes I made had some degree of success.
Before disabling NetBios, I tried connecting to the internet via WiFi instead of Ethernet. This had the result of assigning a virtual IP but disabling the change location option. I was receiving US based Virtual IPs. This is not a viable solution, I need to change regions.
I rebooted and went back to using Ethernet. This did not resolve the change location issue, I still was able to get a virtual IP, but not change region.
I disabled NetBios and rebooted again. Now I was back to where I started, able to change region, but not able to receive a virtual IP. I set NetBios back to the default value, rebooted and retained the ability to change regions, but not receive a virtual IP.
No success yet.
Additional information: I rebooted the laptop this morning. This time the change location was disabled and I couldn’t receive a virtual IP. I ran the repair utility. This enabled the change location option, but still no virtual IP. I was on the Ethernet connection.
Steve, I have contacted support today. They connected to my PC and told me that some people are having the same issue. they collected a report from my PC and told me that they will escalate the problem. So we might have to wait; I will post here if get more info.
All: Following up with the thread to ask if anyone changed their netbios settings, rebooted and rechecked?
SA
SA: See my notes from earlier today. Changing NetBios didn’t help, but I obtained interesting results by switching between Ethernet and WiFi. See earlier posts for details.
1 Like
Is this a version 25.1.9816 issue?
Its a version 24 and 25 issue LeftDented.
SA
Same here… It say connected but down there the virtusal ip section is showing n/a
i tried to edit host file of windows…
for example for france, autria, us etc servers add these strings to the host file:
54.193.155.183 us.surfeasy.mobi
52.53.241.220 us.surfeasy.mobi
34.219.143.36 us.surfeasy.mobi
44.199.228.109 us.surfeasy.mobi
18.224.20.210 us.surfeasy.mobi
3.122.112.61 no.surfeasy.mobi
3.66.166.28 no.surfeasy.mobi
13.38.49.193 fr.surfeasy.mobi
13.38.77.30 fr.surfeasy.mobi
16.62.211.78 at.surfeasy.mobi
16.62.128.218 at.surfeasy.mobi
when i’ve added it connects first attamp but later geting same old story…
Had another brain storming though. Is anyone seeing SSH connections being blocked in their Norton history?
SA
any update…? from anyone!?
No change on my end, the laptop still does not receive a virtual IP. For now I’m not running the VPN on that machine.
I install the vpn app from ios store to my iphone in the name of be sure any gov blockage to main service of vpn of norton… But it works fine… so the adding server ip-s to the host file of windows is unnecessary at this moment… i removed them all from host file… but as articles that i read… norton uses surf easy… and surv easy uses openvpn… and open vpn users also same problem… if you search on google as open vpn not taking v-ip… instead of norton vpn not taek v-ip… almost same results appear… BUT… on windows 10… things are different… i have historical old device for using as media centerish/like device… on that machine… everything works very smooth and instantaneously… Frankly. I’m tired of this Norton… Especially since they tried to make the their client’s machine do mining secretly, I’ve become disgusted with Norton. They ate the legacy of the old Norton and there’s no such legacy anymore… At least their credits ran out for me… Any way if i found any clue… i will share… thanks…
walkthrough/how to check pls…
/////
i just checked… but… nill… nothing happened somthing like that to me up-till now
1 Like
I will be booting my one device with version 25.xx installed and check my VPN against what you are all seeing, report my results. Maybe I can duplicate your issues and find something that we can benefit from.
SA