Suddenly, my wireless devices (a Samsung S9 and a 3rd generation Apple iPad Pro) no longer work with the VPN service that’s built into my corporate firewall, as they have for years. They both connect OK (near-instantly) and obtain a DHCP IP address from the firewall, but the connection is completely non-functional – if you try to load a web page in a browser, the progress bar goes to about 10% and then stops. You have to turn off VPN to restore functionality.
Meanwhile, the VPN connection continues to work perfectly with two Windows 10 desktops. Unlike the wireless units, the connection isn’t instant – there’s a 30-second “completing the connection” phase – but it always completes and gives me a working connection.
Especially confusing is that there are no errors in the log. Both Windows 10 and Samsung/iPad connections report the exact same connection data.
1: https://i.stack.imgur.com/jeXNs.jpg
I’ve been through all the help for my VPN setup at Troubleshooting L2TP connectivity when using iPhone, iPod, iPad | SonicWall. No luck.
Is there an obvious answer that a vpn-guru can provide? I can furnish any technical info you request.
I think I've found the problem. The iPad and the Samsung Galaxy both use IKEv2 for the VPN connection -- my Sonicwall only supports IKEv1.
Related
Hello.
I have recently been trying to mount a home automation station on a raspberry.
I need to communicate with the station via SMS. To do this, I order a 3G dongle (UMTS / GSM / 3G / 4G etc ...) operating on the country's network (verified frequencies). I connect to the network via wifi. But when connecting the 3G dongle, here I am blocked on access to Wifi.
My first question is therefore: is this normal?
And my second is: is it possible to make both work in parallel?
Thx all
It depends on the exact use case or requirement and type of device in hand.
In general, the device will choose/use the wireless connection with better connectivity strength as per its design/specification and also it depends on the support at device.
In case you have the option of WiFi Hotspot tethering enabled, it is possible that most of the devices nowadays allow you to use 3G for the internet communication and at the same time, it allows WiFi hotspot sharing with the help of WiFi from your device.
Also, few devices have support for file sharing between device to device whereby they provide support for wifi direct and wifi sharing while 3G connectivity with internet is still fine. Few devices from Samsung, support an application called "Download Booster" that allows your device to download files using WiFi connection and a mobile data connection simultaneously.
Few devices from Apple starting iOS 7 introduced Multipath TCP enables users to have their streaming music to never get interrupted while on high mobility or in trains and other vehicles with changing connectivity whereby no manual switch from between WiFi and Cellular is required in which case, the device shall stay connected over both cellular and WiFi simultaneously and whenever the WiFi connection fails, the cellular connection shall continue with streaming operation without any interruption.
There is also a app called 'Speedify' in android that uses channel bonding technology to combine multiple Internet connections together for increased throughput & redundancy and thereby it can merge WiFi and Cellular connection simultaneously. Here, a Speedify client software is used to establish a connection to a Speed Server in cloud that acts as a middleman between you and the rest of the internet. The Speedify client software then works together with Speed Server to distribute your internet traffic and deliver the combined speed of all available internet connections.
Computer is connected directly to modem via ethernet. Upon boot, an online speed test is consistently 10 Mb/s. This is significantly less than my service is supposed to be (50+). As soon as I disable and enable the ethernet adapter I can run another speed test at 60+ Mb/s. The connection appears to be stable at this point.
Additional information: Ethernet adapter is Realtek PCIe GBE Family Controller. Drivers are up to date. Tried rolling back drivers. Tried an old modems. Tried flushing DNS, resetting winsock, resetting IP. Tried changing the adapters speed from auto negotiation to 100 full.
I've got nothing. For the time being I've just got a batch file (using devmanview.exe) that resets the adapter on delay after boot but I'd like a more elegant solution. I've had hilarious conversations with my ISP support where I realize this is no longer on their script so they're no help.
Thanks for any help.
I stumbled upon a fix. Turns out the power output to wifi in my router settings was set to 100%. On a whim, I turned this down to 75%. This didn't seem to effect the wifi performance elsewhere in the house but it made my ethernet adapter resolve the connection speed correctly and perform more reliably.
The router is a Motorola Surfboard modem/router combo.
This is my first post, so don't judge if I mess something up.
The problem is that I bought a new Desktop PC for my office (a Windows 8 machine with motherboard Z97-HD3 (has integrated Ethernet/LAN card)) and it worked OK for a few weeks, but now, the internet is gone.
When I boot up my PC I get "Network Identifying". After a minute or so, it says that it is connected, but when I open a browser it either says: "This webpage is not available" (more often) or "SSL certificate problem" (rarely). I've been chipping on this problem for a few days and the only steps that I've mustered up to take are these:
1. Is it the cable? Try the Ethernet/LAN cable on a different computer
Tried that. It works on my other laptop. So I conclude that the problem is with the new computer.
2. Is it a software problem or hardware?
2.1. Look at the back of the PC. The Ethernet card lights are on.
2.2. Try pinging localhost. Start > Open command prompt (cmd) > "ping 127.0.0.1". All 4 packages are sent and received with time 1ms
2.3. Maybe there is something wrong with Windows? Tried installing Ubuntu, but the internet doesn't connect as well
Anything else I could do? Or should I conclude that this is a hardware issue and return it to the shop?
First, make sure that you can ping your Gateway (gateways are computers/routers that are between two networks ). You can find out the IP of your gateway by running this in cmd:
ipconfig
There you will see your currently assigned(or static) ipaddress, the subnetwork, as well as the IP of your Gateway. Then try to ping your Gateway.
If you can then you know that all is good with cables and software and the problem is either configuration(you dont have gateway set) or the gateway can't make the connection outside of your local network.
if you can't ping your gateway, then you know something is wrong on your PC.
We have problems when using a device on windows compact framework 2.0 (windows mobile) and a server with IIS (7) on windows server 2008 R2. We are on WIFI.
We encounter many problems of latency and freezing. Our app is pretty simple. It just send a very small request (a string of 10 chars) to the server which will respond with a string of the same length. There is a request from the device to the server every 3 or 4 seconds.
It works well for some times and suddenly it freeze. It does that with other clients environment : so the only things which vary is the network itself (not the device or the server they both were tested separately and together and they perform well on a wired network).
We are using TCP and we read that it does not work so well on WIFI where the packet loss are not always due to the same reason when on a wired network (congestion).
Does somebody had freezing problems like us on TCP over WIFI ? Do you think we pointed out the same problem as you (TCP over WIFI) ?
We would like to change the protocol used. The first thing we would like to try is TCP Westwood.
Is TCP Westwood not offered on windows server and windows mobile ? If yes, how do you activate it ?.
Our last solution is to build our own server and protocol using UDP. But it's a hard work.
Thank you for answering.
Try setting the TCP_NODELAY socket option as your sending small chunks less than 1500. This will improve performance in a lossy network.
I've got a Windows app that runs on my desktop and connects to a Windows CE app on a handheld device. The handheld fetches data using the Windows app as its conduit (it downloads tables and then converts them into another format, but that's probably neither here nor there as far as this question goes).
Because of the bizarre anomaly we experience where in certain rare instances the handheld app hangs (if the filesize is a very specific number - see Why would a fetch operation crash when the amount of data is divisible by 1023 or 1024?), I want to see just exactly what is being passed between the two devices.
I've gotten the IP Address for both machines/devices using "ipconfig" at the command line. Running Wireshark while they communicate (activity is taking place) and then poring over the capture afterwards, I see several occasions where the desktop machine's IP Address is involved (both as the Destination and the Source) but never do I see the handheld device's IP Address...Why not?
A lot of the "talking" that the desktop machine is engaged in seems to be with wireshark, too.
So the two devices/apps obviously are communicating, but it's as if Wireshark is blind to it...???
If the desktop and handheld are communicating over a Wi-Fi network, and you're running Wireshark on the desktop machine, that should work, if you capture on the Wi-Fi network (leave promiscuous and monitor mode turned off in this case).
If you're running Wireshark on some third machine, you will have to capture in either promiscuous or monitor mode on the third machine, and monitor mode won't work on Windows. If the network is protected (WEP, WPA, WPA2, etc.), you will need to configure Wireshark to decrypt packets on the network.
If the desktop and handheld are communicating over a mobile phone network, you might be able to run Wireshark on the desktop and capture the traffic (but probably not on Windows), but you won't be able to run it on a third machine.