I have a piece of software I have written that talks to a web service over it's Wifi connection on a Casio WinCE handheld.
Unfortunately the Wifi network and the network created by WMDC (or ActiveSync) to host the debugger connection clash, they are both 192.168.55.0/24. So I can't have them both connected at the same time.
Does anybody know if you can reconfigure WMDC to use a different address range?
I've hunted through the registry but can't see anything obvious, and Google is not turning up anything useful.
Thanks,
James.
Is the development PC on teh same network as the WiFi connection? If so, I'd abandon ActiveSync/WMDC altogetehr and just use ethernet debugging over the same connection that it's using for the web service calls.
Related
I had this problem previously (but didn't know the cause) and had to reformat my machine to eliminate the problem. Now I a pretty sure I know the cause:
I have both a wired and wireless internet connection. If I unplug my wired connection I cannot use SSMS to connect (forcibly closed by the remote host) to my Azure database (even though the wireless connection to the internet is fine). I can still connect using sqlcmd over the wireless connection.
By simply plugging/unplugging the Ethernet cable I have confirmed that this is the problem. I have checked my firewall rule for 1433 and it is supposed to be interface independent.
I've tried turning Firewall off completely and forcing TCP in the SQL connection properties.
Has anyone else found this to be a problem and found a solution? Is there a way to specifically tell SSMS to communicate over a specific network interface? Otherwise, I will have to reformat my machine again (and never use a wired Ethernet cable, since it worked fine before I ever plugged in an Ethernet cable) to eliminate this problem.
My guess is that you may be fighting (unbeknownst to you) network protocols.
https://www.connectionstrings.com/define-sql-server-network-protocol/
in the above URL, find the section labeled "Network protocol codes"
"Network Library=dbmssocn"
The above network-library is the 'tcp' one..and is the most common (in 2019) version. (I started sql-server when named-pipes was the biggest player and learned the hard-way about network-protocols ! )
That is how you "force" a certain network protocol in a connection string.
You can also set this value in Sql Server Management Studio.
See here:
https://kb.intermedia.net/article/1893
Find the sentence
"2. If it does not work with default settings, go to Options > Connection Properties tab. And choose TCP/IP in the drop down menu for Network Protocol."
Try experimenting with that.
APPEND:
Your first two screen shots are really hard to read. You have alot of blue space. I'd suggest making your ssms window smaller, then taking the screen shot.
Are you using these credentials naming style?
myazuresqlservername.database.windows.net,1433
MyUserName#myazuresqlservername
Could it be this??
Impossible to connect to Azure SQL database with ipv6 address due to recent forced update from v11 to v12
Turns out this doesn't seem to be a problem with SSMS at all. Although Windows responded that I had the latest Network Driver, I discovered that the manufacturer had a new driver and that seems to have solved the problem.
http://support.killernetworking.com/knowledge-base/clean-install-killer-control-center/
Product Type Killer(R) Wireless-AC 1550 Wireless Network Adapter (9260NGW) 160MHz
Product Type Killer E2500 Gigabit Ethernet Controller
My Hardware:
Operating System: Windows 10 Pro 64-bit (10.0, Build 17763) (17763.rs5_release.180914-1434)
Language: English (Regional Setting: English)
System Manufacturer: Alienware
BIOS: 1.6.5 (type: UEFI)
I have a native iPhone app that connects to a client machine via sockets. The connection works over WIFI but does not work over 3G.
Does anyone have ideas what the issue could be?
Thank you.
UPDATE: The client machine is not on the same network as the iPhone.
Is this client machine within the same network as the iPhone? Then you can access it over Wifi, but would need a proxy over 3G. Just a guess.
The issue is that some cellular networks block certain ports. This is why it worked over WIFI but not 3g. One of the reasons why it is better to use web services.
I've developed a Windows phone app which consumes some data from WCF Service. My app seems to be very slow in Wi-Fi on comparing it with 3G or LAN. I'm a new bee to both Windows phone app dev and WCF. I've verified a number of variables on WiFi bandwidth and connection. Wi-Fi looks good, but the app still slows down. So not sure where the problem is? Do I need to add any configuration to my service to avoid this? Or do I need to check my device? Can anyone help me to find out the cause?
I have had a similar issue. Seems like the 3G data and WiFi do not work smoothly when they're both turned on. Disable 3G data and only enable WiFi and vice versa.
This issue appeared for me after the 7.10.8107.79 update.
This bug have been reported to Microsoft and they are looking into the issue.
I don't know why? Whenever I install AOL desktop (9.5, 9.6, 10.0) on my computer and I'm connected to the internet using cable, every thing is ok. I can browse websites and sign in to AOL.
But whenever I connect to the internet using my wireless network at home, I can not sign in to AOL, but I can still browse the web.
My wireless network uses WPA2-Personal with AES encryption type.
I always get the AC-3000 error message whenever I want to sign into AOL. None of AOL solutions could be useful to solve this.
What do I have to do ?
You didn't mention what version of windows you are using but my suspicion would be that if you are on Windows Vista/7 then the cable connection is identified as "home" or private and that the wireless connection is identified as public and the AOL connection (which used to be on port 5190 IIRC) is getting blocked as a result.
If I am right, to change what apps have access on which network types, you can follow the instructions here:
http://www.addictivetips.com/windows-tips/how-to-stop-a-program-from-gaining-unsolicited-internet-access-in-windows-7/
Although it is about how to stop a program from accessing the internet, it works just as well the other way around ;)
You could use netstat to determine what the successful connection to AOL is on the cable set up in terms of destination and IP and then attempt a simple telnet connection to the same address/port on the wireless set up to verify if this is blocked at the network/port level or if it is blocking the application (usually referred to as ACS). If the telnet connection succeeds and does not timeout, then it is an application level restriction which you will need to fix .
I have a USB modem on a server which occasionally needs to be turned off/on again to receive SIM updates and I can't reboot the server as we rely on it to serve various web pages.
Is there any way to do this programmatically? An AT command? Power down the USB port?
I don't always have access to the server so unplugging it and plugging it back in isn't an option unfortunately.
We're coding in C++/CLI if that makes a difference.
It would be great if someone knew of a generic solution to this, but for the Option Globetrotter 452 I'm using, the manufacturer reports that issuing an AT_ORESET command will instruct the device to reboot ...just in case anyone else wants to do this.