Related
I live on campus and I get internet through residence...
I set up connectify on my computer so that I can use Internet on my phone as well.
Has anyone tried this??
On my x10, it says it's connected, but I can't load any pages (Web page not available...says the browser) and when I look at the connectify panel, under Connected Clients - 1, it's got sony logo and says <Connecting...>
I'm not sure if it's because my wifi card doesn't support it? (but it says all do..hmm)
or if it's my phone? My phone's always had problem with wifi 'outside home'.. Like the only wifi I would be able to use would be a secure wifi through my home router. I haven't been able to connect to any 'public wifi' like at cafe or restaurants...
If anyone's used this and knows how to fix the problem it'd be great... thank you!!!
(or it could be that my school's lame and they block any internet connection through personal hotspots )
Same happened with me on my network. I have tried it on my friends laptop and it worked just fine but i wasn't able to connect using my own laptop( on my home connection which got a windows server machin ).
I'm just guessing it was caused by my windows server machin and some firewall setting that i couldn't adjust.
By the way i just the exact same problem as yours, phone keep showing that it's connected and couldn't open anything and Connectify keep saying connecting.
sorry for my bad english.
I had the same issue, it was a firewall thing. I emailed Connectify and was told
"At a minimum, DualServer.exe (ConnectifyNetServices.exe in 2.1 Beta 1) needs to be allowed to access the network, and ports 67 and 68 for DHCP, and port 53 (DNS), as well as 1317, 1318, and 1303 (internally used ports for DHCP and DNS), need to be open. Connectify 2.1 Beta 1 will try to configure Windows firewall to open all necessary ports."
Currently i have just disabled windows firewall and all works fine (I have a hardware firewall between me and WAN).
I had the same problem with my x10. It kept saying connecting. I contacted the developer, they asked me to use beta. I just installed beta and every thing is fine now...
h**p://www.connectify.me/download/2.1/ConnectifyInstaller_2.1_Beta_3.exe
replace ** with // as Im not allowed to link...
07ee17 said:
I had the same problem with my x10. It kept saying connecting. I contacted the developer, they asked me to use beta. I just installed beta and every thing is fine now...
ConnectifyInstaller_2.1_Beta_3.exe
replace ** with // as Im not allowed to link...
Click to expand...
Click to collapse
this version didnt work for me but the 2.2 version works for me, My phone is Xperia x10 mini 2.1
Using HP Pavilion DM4, I can use connectify and my X10 gets internet access...not sure what's your problem though.
I use Connectify on my Win7 PC too, sometimes, out of the blue, while I am connected and loading pages, it stops, even though it is still connected.
I find that killing the app and the process on my PC and then opening the app again, fixes the problem.
Connectify is very buggy but incredibly useful when it works right, imho.
Hi, in case this has been already solved I apologize in advance, however I searched all the post on this and could't find real solution to my problem and from what I have read I am not alone...
The think is that if I install any build of Androud to my Leo everything works perfect except the WiFi connection - after enabling WiFi and pointing it to my router it recognizes it, accepts the password (WPA-PSK protection) and then after some time of getting IP it never connects and it goes on and on.
I tried every single thing I have found all around this forum and many others, unfortunatelly nothing could make it work (forcing static IP, opening the network without protection, changing networks SSID, leaving WiFi on and restarting, etc.)
It is really pitty as I really like the way Androind moves on HD2, but as I use the Wifi a lot to unload a bit my data plan I cannot stick with it at the moment. So, is there any real solution to this problem?
Thank you in advance.
I have the same problem. But the connection is fine when I was under Winmo.
The only time I've experienced a similar issue was when I upgraded to a new kernel, without pushing the new modules. What builds and kernel are you using?
Sincerely,
Mac
Try updating your builds or just modifying the mac adresses
I already have this issue when upgrading or changing build. I resolved the problem with Airplane Mode. switch on/switch off. Let us know the result. ^^
I was having the same problem. It wouldnt connect to my home network, but it would connect to every other network. Turns out my router was too old. I recently got a new router and it works fine. Also, when I had my G1, it also wouldnt connect to my home network via wifi, but it does with the new router.
wangshuokevn said:
I have the same problem. But the connection is fine when I was under Winmo.
Click to expand...
Click to collapse
On WinMo no problem.
white-energy said:
Try updating your builds or just modifying the mac adresses
Click to expand...
Click to collapse
As I wrote before, I tried many different builds with no succes. At the moment I installed MCCM SE V3.4(FroyoStone Sense)[kernel hastarin r8.5]. As I have nothing to save I do everytime clean install on reformated card.
lamario said:
I was having the same problem. It wouldnt connect to my home network, but it would connect to every other network. Turns out my router was too old. I recently got a new router and it works fine. Also, when I had my G1, it also wouldnt connect to my home network via wifi, but it does with the new router.
Click to expand...
Click to collapse
IMHO the router is not the problem even it's a bit outdated - Linksys WRT54GL - as I tried to connect to friend's network, I also created AP from my notebook - with the same result.
hatchy77 said:
I already have this issue when upgrading or changing build. I resolved the problem with Airplane Mode. switch on/switch off. Let us know the result. ^^
Click to expand...
Click to collapse
The Airplane mode you toggle in WinMo or Android? I tried it in WinMo - no success.
oh yes...
... I know this kind of problem.
Tried so many builds of Froyo. Most wlan-stable was indeed MCCM SE V3.4(FroyoStone Sense)[kernel hastarin r8.5] - with this build I had no wifi drops or hsdpa drops.
From today on I try the MDJ FroYo HD v.4.1[kernel:MDJ S7.3HD]. Most time it holds the connection, but sometimes when waking up from stand-by I have to disconnect and reconnect wifi.
Router: Linksys WRT54G.
mac-nukem said:
... I know this kind of problem.
Tried so many builds of Froyo. Most wlan-stable was indeed MCCM SE V3.4(FroyoStone Sense)[kernel hastarin r8.5] - with this build I had no wifi drops or hsdpa drops.
From today on I try the MDJ FroYo HD v.4.1[kernel:MDJ S7.3HD]. Most time it holds the connection, but sometimes when waking up from stand-by I have to disconnect and reconnect wifi.
Router: Linksys WRT54G.
Click to expand...
Click to collapse
Thanks for the answer, unfortunatelly I have nothing to drop as I cannot connect. On the other hand either EDGE and HSDPA works like charm - solid connection.
snekoza said:
The Airplane mode you toggle in WinMo or Android? I tried it in WinMo - no success.
Click to expand...
Click to collapse
Into Android my friend
I also had this problem. It's easily solved by loging into your router and setting up the access list (under adv wireless settings on mine). You can add the device in with its specific mac address and by doing this I was instantly able to use wifi.
It's not an issue with mac address filtering. I know this issue because I have the same problem with the wifi router at the office. I can connect without any problem at home but It just won't work at the office.
DHCP server assigns an IP, but if you try to ping any IP outside LAN you'll get network unreachable.
I didn't have time to test a bit more, but I'll try to change the mac address of my wlan in order to test if the problem relies in there. The idea is to assign the same MAC Adress I have on WinMo. This will be very useful also to people with 2 HTC HD2 using the same ROM and Kernel.
BTW, I'm not using MAC Address filtering, this issue has nothing to do with it.
I have the same problem here ..
Please help me buddy!
thank you in advance
hassohd2
I tried this switching in and out of Airplane mode in Android with varying degrees of success. The problem itself seems intermittent for me - sometimes I get a decent amount of time with successful access and sometimes I don't. Similarly a reboot (of Android) may or may not work for me. I am using kernel version 2.6.32.15-gd09adbb gcc version 4.4.0 and is dated Thu Dec 30 19:14:35 CET 2010 for me. I notice I am more inclined to have an issue with Market even than with Firefox. Also it is more of a problem now than with a previous kernel version (but it had problems too if I recall correctly). I upgraded because I am having difficulties with getting the USB link to work under Android (but that problem is still there). It did seem to work well for the first few hours after the upgrade, but since then...
I did notice that under MS WM, the MAC address is quite different to that recorded by my DHCP server (a unix box the other side of my wireless router) for Android. The Android one looked like it was a stock standard number sequence, so fabricated. I wonder where that is set on the phone?
I also noticed that the phone does not have the usual (for Linux) resolv.conf file that often gets configured by the DHCP connection process. Further, entering a host IP in the /etc/hosts file does not necessarily mean that a command like ping will find it every time. Of recent I have not been checking that - I have been using the IP address of my unix box to do ping tests to. The network does (of course) shut down when the phone goes into sleep mode, but does wake up, even responding to a ping from the unix box. Running up Market, though, seems to kill the connection every time now (but a weather update won't).
A further observation: if I get the Wi-Fi network connection to reset itself (straight forward when the lease expires), it is hard to get it to reset itself until after the next lease expiry for some reason.
I did some further tests. I don't have a pipe (|) key on my HTC HD2 that works so the following commands are a little long winded.
localhost / # getprop > /data/tmp/props
localhost / # grep dns /data/tmp/props
[net.change]: [net.dnschange]
[dhccp.eth0.dns1]: [192.168.10.1]
[dhccp.eth0.dns2]: []
[dhccp.eth0.dns3]: []
[dhccp.eth0.dns4]: []
[net.dns1]: [192.168.10.1]
[net.dnschange]: [49]
localhost / #
Now 192.168.10.1 is my (Unix) DNS server.
When I do the following on the phone
localhost / # nslookup 192.168.10.1
(or even localhost / # nslookup cicada or even the fqdn of the server)
and I tail -f /var/tmp/named.log on the server (where I set up logging for queries and resolver categories for this test)
I see no action at all on the server and on the phone I get
localhost / # nslookup 192.168.10.1
Server: 192.168.10.1
Address 1: 192.168.10.1
Name: 192.168.10.1
Address 1: 192.168.10.1
localhost / #
localhost / # nslookup cicada
Server: 192.168.10.1
Address 1: 192.168.10.1
nslookup: can't resolve 'cicada'
localhost / #
and the same for the FQDN.
The DNS server does not even see the request for forward or reverse lookup, strangely enough. But it is seeing the requests from other machines with logs to the reverse lookup from those other machines looking like:
10-Jan-2011 22:21:57.953 queries: info: client 192.168.10.20#38971: query: 1.10.168.192.in-addr.arpa IN PTR +
So, not only does the wi-fi link drop when Market is run, the DNS is behaving strangely to terminal based testing. Further, an update of the weather does not show any traffic in the DNS server log (at least for the logging level I have set up) even though the weather does get updated. It makes me wonder what DNS it is really using.
The other avenue I want to check is DHCP time-out, which I have been keeping an eye on (it does seem to time out and not update, but there are also other issues that suggest the problem is not a time-out one). That will have to be another day at this stage, though.
what channel is the router using for wifi?
Hi all,
Ive been having a problem whereby my twitter and facebook feeds wont refresh after browsing the net for 15 mins or so on WiFi.
They work without problems based on phone signal but when using WiFi its as if the signal just drops out even though it says not, and the browser will work just not facebook/twitter. A phone restart or toggle off/on of WiFi doesnt fix the problem.
Im on 2.3.3 and firmware version KE2.
Any ideas or anybody been having the same issue? Ive done some searching but cant find any help...
Sent from my GT-I9100 using XDA
Any body any ideas?
I'm struggling with this. Thinking of selling it and getting a Sensation...
It may be a defect on your phone. Try bringing it back to the shop and ask for a replacement if you can repeat the issue on their Wi-Fi.
And I wouldn't really recommend on getting a Sensation because of Wi-Fi issue because the Sensation has a worse "death grip" issue (YouTube that and you will see quite a lot of videos on that), other than a very small 1.5GB internal storage/
luke222010 said:
Hi all,
Ive been having a problem whereby my twitter and facebook feeds wont refresh after browsing the net for 15 mins or so on WiFi.
They work without problems based on phone signal but when using WiFi its as if the signal just drops out even though it says not, and the browser will work just not facebook/twitter. A phone restart or toggle off/on of WiFi doesnt fix the problem.
Im on 2.3.3 and firmware version KE2.
Any ideas or anybody been having the same issue? Ive done some searching but cant find any help...
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Does your wifi routes data through a proxy. If yes apps wont be able to connect to the internet on wifi, the browser can.
This is an android issue so shifting to sensation wont help.
Hello Guys,
I can think of two possibilities.. Cause, I had somewhat the same problem in the earlier Galaxy S (I am now on Galaxy SII).
First Scenario :
Both Facebook and Twitter have a refresh timing option under Settings. You must set it to minimum. (For facebook, minimum refresh is 30 mins and for Twitter, Its 15 Mins).
Second Scenario :
I assume that you are using WiFi and I also assume that you have a repeater installed. In that case, you must tinker with the Network WAN settings of your repeater. Typically, the broadband "modem" is set to MTU = 1500 and the "Repeater" MTU is also set to 1500. This causes some problem in uploading data. Now, as facebook and twitter ( as also Android Market ) sends some data first and then downloads data, if the sendng is problamatic, the downloading of data would also not be good. ( A typical way to check it is to try uploading some test snap on facebook. If the test snap is uploading, then your home Wifi is working all right). However, if the picture uploading is not getting through, try to reduce the MTU. This guide will help you :-
"Max MTU: How do I find mine?
The MTU setting controls the maximum ethernet packet size your PC will send (you did know the Internet works in packets, didn't you?). Why a limit? Because although larger packets can be constructed and sent, your ISP and Internet backbone routers and equipment will chop up (fragment) any packets larger than their limit. These parts are then reassembled by the target equipment before reading. This fragmentation and reassembly is not optimal.
MTU and Windows and Defaults
Unless otherwise set, Windows defaults MTU to 1500, or a lower value of 576 for external networks. 1500 is OK unless you are running PPPoE, want to use IPSec (Secure VPNs) or both, then it's too big. 576 is not efficient for the broadband/Internet; it's too small.
Finding the largest MTU, by EXPERIMENT
If your MTU is too low already, maybe 576, the following method will not be able to detect whether you can switch to an optimal size. So first follow "CHANGING MTU for PPPoE" to reset MTU to 1500, reboot and then come back to this!
The best value for MTU is that value just before your packets get fragmented. How do you find that out? By using Ping at an command prompt.
Windows 2000/XP users:
Go to Start/ Programs/ Accessories/ Command Prompt and type the following:
ping -f -l 1472 www.dslreports.com
(That is a dash lower case "L," not a dash "1." Also note the spaces in between the sections.)
Linux users:
ping -s 1472 www.dslreports.com
OS X users:
ping -D -s 1472 www.dslreports.com
Linux and OS X commands are case sensitive.
Press Enter. Then reduce 1472 by 10 until you no longer get the "packet needs to be fragmented" error message. Then increase by 1 until you are 1 less away from getting the "packet need to be fragmented" message again.
Add 28 more to this (since you specified ping packet size, not including IP/ICMP header of 28 bytes), and this is your MaxMTU.
Note:If you can ping through with the number at 1472, you are done! Stop right there. Add 28 and your MaxMTU is 1500."
I hope with the above, the prroblem gets sorted. If you succeed, please leave your experience here...
Regards.
Hi all,
Thanks for your replies.
Neither facebook nor twitter work at all on wifi now. I've figured out that they DO work on wifi on friends/family routers, just not mine!
Whats weird is facebook will work if I login through a browser such as dolphin or firefox, but not through the official facebook app itself. Same with twitter.
My max MTU is set to 1492 - i've checked this is correct using the instructions you provided and it is...
Another issue is browsing the internet - sometimes if i open more than one tab, it stops working altogether, and subsequently any other app that requires access to the internet will not work also. The only way to resolve this issue is by turning the phone off and back on again.
Really struggling with this. Could it be as simple as switching channels within the router?
Im open to suggestions so any ideas i'd appreciate!
Thanks again,
Luke.
Dear Luke,
Ok.. Thanks for the input.. See, if your facebook and twitter is working fine on other Wifi's, it means that there is no problem with your phone setup.. also, when you are using on 3G, there is no problem and that confirms that your handset has no problem at all.. so dont worry on that count..
Read my post carefully..
I had suggested you try upload a pic on facebook using wifi (the one which has problem).. If you are not able to upload, that should confirm that your home wifi has to be set up properly. There are two types of installations of Wifi.. (1) in which the Broadband Modem and Wifi is in a single device and (2) where you have a broadband modem and then a seperate wifi device.
Now the broadband modem also has its seperate MTU which it uses to interact with the broadband server.
Similarlt, the wifi decive connected to the Broadband modem also requires its own MTU to communicate with the broadband modem..
These two are therefore different settings.
You dont typically have to change the settings on the Modem, but only the wifi device. When I faced a similar issue, I had to check and reduce it to 1430 myself so that it works properly.. Try the same.. Try reducing wifi MTU to 1430 leaving the modem MTU to 1500 (default). If you do it right, you will solve the problem...
I had exactly the same problem but I found no real help on the internet android forums.. But that history..
Now, I know this is the real problem and the cure is easy... "Just set the MTU on wifi (device) to 1430... DONE.
Try rebooting the router, and then flush dns settings in cmd.
how to flush dns http://www.tech-faq.com/how-to-flush-dns.html
akshayadv said:
Dear Luke,
Ok.. Thanks for the input.. See, if your facebook and twitter is working fine on other Wifi's, it means that there is no problem with your phone setup.. also, when you are using on 3G, there is no problem and that confirms that your handset has no problem at all.. so dont worry on that count..
Read my post carefully..
I had suggested you try upload a pic on facebook using wifi (the one which has problem).. If you are not able to upload, that should confirm that your home wifi has to be set up properly. There are two types of installations of Wifi.. (1) in which the Broadband Modem and Wifi is in a single device and (2) where you have a broadband modem and then a seperate wifi device.
Now the broadband modem also has its seperate MTU which it uses to interact with the broadband server.
Similarlt, the wifi decive connected to the Broadband modem also requires its own MTU to communicate with the broadband modem..
These two are therefore different settings.
You dont typically have to change the settings on the Modem, but only the wifi device. When I faced a similar issue, I had to check and reduce it to 1430 myself so that it works properly.. Try the same.. Try reducing wifi MTU to 1430 leaving the modem MTU to 1500 (default). If you do it right, you will solve the problem...
I had exactly the same problem but I found no real help on the internet android forums.. But that history..
Now, I know this is the real problem and the cure is easy... "Just set the MTU on wifi (device) to 1430... DONE.
Click to expand...
Click to collapse
Hi again,
Allow me to give you a bit more info...
I'm on a talktalk (rubbish!) landline/internet package. My netgear router is plugged directly into the phone line via an adsl cable. The router is configured for wifi access. I presume as I have no seperate device, that the modem is built into the router also.
I tried uploading a picture to facebook and it failed after a few minutes of trying.
Basically last night I tested the MTU via the command line interface using the ping command you provided. At 1464 i no longer received the fragmented packet errors, so i presumed adding 28 to 1464=1492 was the correct thing to do, and so I did this and then checked that in the WAN settings in the router config the MTU value was set to this which it already was.
I'm not quite sure how I set the MTU value specific to the modem if doing so under the WAN settings has not already applied it for both wifi and the modem. Can you provide further assistance if I should be changing a setting elsewhere?
Some further info - I have changed my router so it does not broadcast the SSID, and so that you can only connect to it if your MAC address is listed under the allowed devices which my phone is. I'm not sure if this would cause a problem - it never with the iPh*** (he who should not be named!) i had previously!
stoney73 said:
Try rebooting the router, and then flush dns settings in cmd.
how to flush dns http://www.tech-faq.com/how-to-flush-dns.html:
Click to expand...
Click to collapse
Hi,
I had never thought of doing this but will give it a go tonight.
Thanks,
Luke.
luke222010 said:
Hi,
I had never thought of doing this but will give it a go tonight.
Thanks,
Luke.
Click to expand...
Click to collapse
Its probably not the answer, but its one of those silly things...and the worst it can do is just freshen the connection.
EDIT:I messed up the previous link. so here it is: http://www.tech-faq.com/how-to-flush-dns.html
Just set it to 1464 then. We are on the right track.
Sent from my GT-I9100 using XDA App
I've tried all the fixes, it seem either 3.1 broke it completely. or is acers/google's implementation?
and if I ping north-america.pool.ntp.org from adb shell.. I get the correct dns data (or so I think) about one every 3 trys.
64.73.32.134 seems right but the other 2 are like
# ping north-america.pool.ntp.org
PING north-america.pool.ntp.org (216.144.229.211) 56(84) bytes of data.
64 bytes from armakuni.lastninja.net (216.144.229.211): icmp_seq=1 ttl=50 time=109 ms
# ping north-america.pool.ntp.org
PING north-america.pool.ntp.org (198.137.202.16) 56(84) bytes of data.
64 bytes from conquest.kjsl.com (198.137.202.16): icmp_seq=1 ttl=50 time=86.2 ms
which might just be theire backup round robin providers (the names just strike me as weird and Im too lazy to whois them lol)..
anyways, if anyone has a working 3.1 solution for the US lay it on me!
Confirmed
Having GPS issued under 3.1 - just the early official Acer release. No worries here, usually use my Samsung Intercept device for nav/GPS - but kinda suck that it's not working since 3.1 update
PRIMEE ROM has very good gps. It is based on asus.
my gps works fine, but i switched from north-america.pool.ntp.org to us.pool.ntp.org
sometimes there is a delay in acquisition, but all my other gps devices other than my car's have been having similar issues lately
don't have 3.1 yet but my GPS works fine. did your GPS work before 3.1. ?
Over the past couple of weeks since I got a GTX 760 for my main rig, I've been playing with getting Shield streaming to work through a NAT. With a combination of an Android app and Windows app, I've been able to get the Shield to stream through a NAT device.
This is alpha software, so it may not work for you. I'll be continuing development on it to make it more robust based on bug reports filed here and on the GitHub projects
This method is potentially more complex than running a VPN, but it is lower overhead and works in environments where VPNs cannot.
For those who don't care about the technical details, skip the next section.
Relay Technical Details
The Shield uses MDNS to discover compatible streaming PCs. It issues a query for _nvstream._tcp.local to which streaming PCs reply with PTR, A, AAAA, and TXT records. MDNS isn't routable outside of the local network (and sometimes blocked within the network too), so naturally PCs outside the Shield's local network won't be available as streaming targets.
To solve the MDNS problem, I wrote MDNS relays for Android and Windows that operate on UDP port 5354. The Android relay sends MDNS queries to the Windows relay where the Windows relay replays them local and sends the reply back to the Shield. The Android relay then takes the reply and parses it to look at the A record. It replaces the IP address specified in the A record with the IP address it received the MDNS reply from so it can properly connect to PCs behind a NAT. With the MDNS relay code in place, the Shield could see the PC and even start games.
There was still a problem getting the video stream back. It turns out that the way that UDP port 47998 is used on the Shield streaming software running on the PC prevents it from traversing NATs when going back to the Shield because it assumes that the source is always 47998. This is IMHO a bug because all other ports deal with NAT traversal properly, but needless to say I still had to deal with this.
The only option I had for fixing the port 47998 issue was to capture the packets as they go onto the wire in the Windows relay. I used WinPcap to capture the UDP packets leaving the machine. I then filter based on whether the packet was addressed to us. If it's a packet from the Shield to us on port 47998, then I save the source port of that packet. When I see a packet going out from us to port 47998, I extract the data from that packet and send it again on my own socket also bound to port 47998 (so the source port is correct) with the destination specified in the packet and the port that we saved from the Shield's last communication. With this code, the Shield can connect to a PC from behind a NAT.
Instructions
1. Download and install the Shield Proxy APK on the Shield from https://github.com/cgutman/ShieldProxyAndroid/releases
2. Install WinPcap on your streaming PC from http://www.winpcap.org/install/
2.1 Only required for v0.1-- Install the Visual C++ 2013 runtime library for x86 (use x86 even on x64 systems) from http://www.microsoft.com/en-us/download/details.aspx?id=39315
3. Ensure your router is configured properly as described in the next section.
4. Download and run the Shield Proxy Windows program on your streaming PC from https://github.com/cgutman/ShieldProxyWindows/releases
5. On the Android app, fill in the externally accessible IP address or DNS name for your router. You can get your external IP address from http://www.whatsmyip.org/ on your streaming PC.
6. Tap the start button to start the Android relay service
7. Stream like normal from the TegraZone app
NAT/Router configuration for Shield streaming
The following ports need to be forwarded to the streaming PC:
UDP 47998, 47999, 48000, 5354 (MDNS relay port)
TCP 35043, 47989, 47991, 47995, 47996
Troubleshooting
Make sure ShieldProxy.exe is allowed through Windows Firewall for Private and Public networks.
Make sure ShieldProxy.exe and the Android Shield Proxy service are running
Make sure the external IP address of your streaming PC is correct in the Android app (use http://www.whatsmyip.org/ from your streaming PC)
If TegraZone doesn't show your PC as online and you see "We haven't received any DNS responses. Is the Windows Shield Proxy running on your PC?",
Ensure the router is properly forwarding the specified ports to your PC. Note that TCP vs UDP matters when setting the router forwarding configuration.
Issues
If anyone encounters problems, please report them here or on the GitHub issues page. I'll try my best to get them fixed.
After getting all the initial setup done, it's seemingly ran great so far; considering the circumstances. Haven't had any errors besides some DNS thing I didn't get to read fully when it booted up Steam but did not have any impact on playability.
DLL error
I keep getting an error that MSVCR120.dll is missing. I checked the windows\system32 folder and it wasn't there, so installed the Visual C++ redistributable package for Visual Studio 2012 and 2013 Preview. This added the DLL to the system32 folder, but still getting the same error after a reboot. Tried copying the DLL to the directory for Shield Proxy and it then gives me an error "The application was unable to start correctly (0xc000007b). Click ok to close the application.
Any ideas?
Thanks and thanks for putting this together!
Cheers!
daethang said:
I keep getting an error that MSVCR120.dll is missing. I checked the windows\system32 folder and it wasn't there, so installed the Visual C++ redistributable package for Visual Studio 2012 and 2013 Preview. This added the DLL to the system32 folder, but still getting the same error after a reboot. Tried copying the DLL to the directory for Shield Proxy and it then gives me an error "The application was unable to start correctly (0xc000007b). Click ok to close the application.
Any ideas?
Thanks and thanks for putting this together!
Cheers!
Click to expand...
Click to collapse
I can't remember whether the 64-bit Visual C++ redistributable includes both 32-bit and 64-bit runtime dlls. The relay is built as a 32-bit program so it needs the 32-bit runtime even on a 64-bit machine.
For the next version, I'll build it with the runtime linked into the executable so people won't have to hunt down the runtime.
cgutman said:
I can't remember whether the 64-bit Visual C++ redistributable includes both 32-bit and 64-bit runtime dlls. The relay is built as a 32-bit program so it needs the 32-bit runtime even on a 64-bit machine.
For the next version, I'll build it with the runtime linked into the executable so people won't have to hunt down the runtime.
Click to expand...
Click to collapse
Thanks - installed the 2013 32bit preview and it worked like a charm after. Will start testing the remote streaming now. Thanks for the quick pointer. Appreciate it!
Cheers
daethang said:
Thanks - installed the 2013 32bit preview and it worked like a charm after. Will start testing the remote streaming now. Thanks for the quick pointer. Appreciate it!
Cheers
Click to expand...
Click to collapse
Cool, I updated the instructions to mention that the Visual C++ 2013 x86 runtime is required.
Oh, nice.
Since VPN method didn't work on my rig, I tried this one... and works great!
thanks a lot.
Seems to be working here as well, although similar to VPN, streaming outside of my WIFI connection doesn't seem to work. The game will start and every once in a while I will see video start (more often though just a blank screen followed by a timeout). My home connection has 55 down and ~12 up, so I think the connection on that end is good. I have tried from multiple remote locations, but none of them have worked so far. Will do some speed tests on the remote connections to see if they are the cause. Splashtop seems to stream fine when on remote connection, so I dont think its a connection issue. One thing that works better on this solution is the PC actually shows as available, for some reason it does not when on VPN.
daethang said:
Seems to be working here as well, although similar to VPN, streaming outside of my WIFI connection doesn't seem to work. The game will start and every once in a while I will see video start (more often though just a blank screen followed by a timeout). My home connection has 55 down and ~12 up, so I think the connection on that end is good. I have tried from multiple remote locations, but none of them have worked so far. Will do some speed tests on the remote connections to see if they are the cause. Splashtop seems to stream fine when on remote connection, so I dont think its a connection issue. One thing that works better on this solution is the PC actually shows as available, for some reason it does not when on VPN.
Click to expand...
Click to collapse
From what it sounds like, the MDNS relay is working fine and the router is definitely configured correctly because you get video sometimes. I assume you also see the message in the ShieldProxy.exe console: "Shield is now communicating with us on port XXXXX".
If I had to speculate, I'd say it's related to high packet loss. Shield streaming (both on the network and through my proxy) use UDP for the video stream and a PPTP VPN uses GRE packets which are both lossy protocols, while Splashtop uses TCP which retransmits lost packets. It may be that the ISP is doing some QoS stuff that's causing non-TCP packets to be dropped at a higher rate, but this is complete speculation.
The Shield pings the streaming PC and the streaming PC sends back video data, but if the pings aren't reaching the streaming PC or the video isn't reaching the Shield, you get the dreaded "Streaming failed due to network interference ... etc" message.
The upside is that we can better troubleshoot the issue based on the output from the Windows Shield proxy. If you could paste that here, I could take a look (remove the last 2 octets of the IP addresses, so 192.168.1.1 becomes 192.168.X.X). Also if you would post what ISP you're using and where you were trying to connect from (whichever ones you feel comfortable mentioning).
I can't seem to get any of those ports open except 47989, even when I change my setup to be directly connected to my SB6141 modem. Port 5354 always appears closed and can't be accessed so I never can see my computer when I try connecting with the shield proxy app posted above.
Anyway to change the port to something other than 5354 or any idea why the port always appears closed even when connected from computer to modem?
Thanks
Edit: It seems only ports that are being listened to on netstat -an will appear as open to a port checker. Shouldn't there be something on that list listening for 5354 in order for Shield proxy to connect to that port?
HobsonA said:
I can't seem to get any of those ports open except 47989, even when I change my setup to be directly connected to my SB6141 modem. Port 5354 always appears closed and can't be accessed so I never can see my computer when I try connecting with the shield proxy app posted above.
Anyway to change the port to something other than 5354 or any idea why the port always appears closed even when connected from computer to modem?
Thanks
Click to expand...
Click to collapse
Ports will appear closed even if the router is properly forwarding them to your PC, but the PC is blocking them. Check your Windows Firewall settings and make sure ShieldProxy.exe is allowed through for both public and private networks. I also found out the hard way that it won't always prompt you to allow for public networks if it's already allowed for private and vice versa.
I think it's normal for those other Shield Streaming ports to be closed until streaming actually starts, but 5354 should appear open while ShieldProxy.exe is running.
It is possible for me to (and I plan to) add some code to make the MDNS relay port configurable but I don't think that would solve your issue here.
EDIT: Also make sure you're testing 5354 (and other UDP ports) as UDP, not TCP. TCP 5354 is not the same as UDP 5354. In fact, you can host different services on the same ports on TCP and UDP at the same time.
cgutman said:
Ports will appear closed even if the router is properly forwarding them to your PC, but the PC is blocking them. Check your Windows Firewall settings and make sure ShieldProxy.exe is allowed through for both public and private networks. I also found out the hard way that it won't always prompt you to allow for public networks if it's already allowed for private and vice versa.
I think it's normal for those other Shield Streaming ports to be closed until streaming actually starts, but 5354 should appear open while ShieldProxy.exe is running.
It is possible for me to (and I plan to) add some code to make the MDNS relay port configurable but I don't think that would solve your issue here.
EDIT: Also make sure you're testing 5354 (and other UDP ports) as UDP, not TCP. TCP 5354 is not the same as UDP 5354. In fact, you can host different services on the same ports on TCP and UDP at the same time.
Click to expand...
Click to collapse
Ah good call out of my lack of attention to detail I forgot to run Shieldproxy.exe again after removing my router from the loop and rebooting everything. It appears to be working now. Unfortunately my Linksys E2000 with DD-WRT has been having major issues port forwarding but at least I know it's my router now and I can keep playing with it to get it working like I had to do with VPN.
Thanks!
v0.2 released
I've posted updated releases for Android and Windows on the GitHub projects. None of the changes in either version break compatibility with v0.1 so you can update them at separate times.
Android v0.2 Changelog:
- Fix several bugs preventing the "MDNS relay not running" warning from showing up consistently
- Tighten the check that determines whether the MDNS query will be forwarded
Windows v0.2 Changelog:
- Statically link to the VC++ runtime so installing the runtime isn't required anymore
- Tighten the check that determines whether the MDNS query will be forwarded
cgutman said:
From what it sounds like, the MDNS relay is working fine and the router is definitely configured correctly because you get video sometimes. I assume you also see the message in the ShieldProxy.exe console: "Shield is now communicating with us on port XXXXX".
If I had to speculate, I'd say it's related to high packet loss. Shield streaming (both on the network and through my proxy) use UDP for the video stream and a PPTP VPN uses GRE packets which are both lossy protocols, while Splashtop uses TCP which retransmits lost packets. It may be that the ISP is doing some QoS stuff that's causing non-TCP packets to be dropped at a higher rate, but this is complete speculation.
The Shield pings the streaming PC and the streaming PC sends back video data, but if the pings aren't reaching the streaming PC or the video isn't reaching the Shield, you get the dreaded "Streaming failed due to network interference ... etc" message.
The upside is that we can better troubleshoot the issue based on the output from the Windows Shield proxy. If you could paste that here, I could take a look (remove the last 2 octets of the IP addresses, so 192.168.1.1 becomes 192.168.X.X). Also if you would post what ISP you're using and where you were trying to connect from (whichever ones you feel comfortable mentioning).
Click to expand...
Click to collapse
I think you are right in regards to packet loss. I have Comcast at home, and have tried various providers (ATT LTE, ATT WIFI so far with this solution and VPN over some other WIFI networks). I will be testing it again in the next couple of days and will report back with the additional details requested. I have the ASUS NT-R66U router as well. Thanks for the reply and offer of assistance, really appreciated.
Cheers!
Finally had some time to play with this more than some quick tests. This seems to run so much smoother than my old VPN configuration.
I don't know if anyone else has experienced with this but even though it's running like almost perfectly smooth sometimes the connection just completely drops. VPN would have big lag spikes but would rarely drop me.
Edit: Hm not sure if this is normal but there seems to be a larger audio latency (> 200-300 ms) which wasn't as bad with VPN. If I go to a friends house instead of playing around at work I'll try hard wiring my shield to ethernet to see if that improves anything.
HobsonA said:
Finally had some time to play with this more than some quick tests. This seems to run so much smoother than my old VPN configuration.
I don't know if anyone else has experienced with this but even though it's running like almost perfectly smooth sometimes the connection just completely drops. VPN would have big lag spikes but would rarely drop me.
Edit: Hm not sure if this is normal but there seems to be a larger audio latency (> 200-300 ms) which wasn't as bad with VPN. If I go to a friends house instead of playing around at work I'll try hard wiring my shield to ethernet to see if that improves anything.
Click to expand...
Click to collapse
Glad to hear that it's smoother than VPN for you.
The Shield Relay is just the same Shield streaming traffic just sent over the Internet rather than your home network. This comes with benefits (speed) and drawbacks (lower reliability). Both of the oddities that you mention are probably related to packet loss, latency spikes, and routing changes that are more prevalent on the Internet than the average home network.
I suspect that the reason the stream drops during big lag spikes is because the lag spikes are due to packet loss or high latency. If the Shield's pings to the streaming PC get lost or arrive very late, the PC will timeout the stream, stop sending video, and the stream will drop.
The audio latency is probably due to variances in the latency and routing of the Internet. It's possible that the video packets and the audio packets take different paths through the Internet, so they can reach the Shield at different times. Normally the latency is close on a home network because there's only one route from your computer to your Shield, but the Internet can have tens or hundreds of routes to get your packets from point A to point B (sometimes even the route from A -> B is different than B -> A).
Nvidia could timestamp the audio and video packets so they can be played back at the same time, but that would force the Shield to delay displaying the video while it waits for the audio packets to come (and vice versa). Since this is a gaming feature, they probably don't want to introduce more latency.
ok how to know if everything if ok ?
ok how to know if everything if ok ? ?
i done everything like it write over here and i don't get any error just "stop" after i click run in the shield.
so everything working right?
Yosizach said:
ok how to know if everything if ok ? ?
i done everything like it write over here and i don't get any error just "stop" after i click run in the shield.
so everything working right?
Click to expand...
Click to collapse
Do you see both lines like "Shield is now communicating with us on port XXXXX" and "Relaying MDNS traffic to XXX.XXX.XXX.XXX" on the Shield Proxy running on Windows?
cgutman said:
Do you see both lines like "Shield is now communicating with us on port XXXXX" and "Relaying MDNS traffic to XXX.XXX.XXX.XXX" on the Shield Proxy running on Windows?
Click to expand...
Click to collapse
dmm...no i don't see it ...this is what i get when i run the
ShieldProxy.exe
all i get is "shield streaming proxy for windows v0.2"
joined MDNS multicast group with interface 192.168.1.13 (my pc)
listening on Microsoft for shield traffic
relay is up and running..."
what i am doing wrong .. i open all the ports i have RT-AC66U so..
Yosizach said:
dmm...no i don't see it ...this is what i get when i run the
ShieldProxy.exe
all i get is "shield streaming proxy for windows v0.2"
joined MDNS multicast group with interface 192.168.1.13 (my pc)
listening on Microsoft for shield traffic
relay is up and running..."
what i am doing wrong .. i open all the ports i have RT-AC66U so..
Click to expand...
Click to collapse
Does your PC show up as available in the TegraZone app with Shield Relay running on Windows and Android? The start button on the Android relay doesn't do anything other than just start the relay service in the background. You still need to use the TegraZone app to access streaming. If you see an error message saying "We haven't received any DNS responses. Is the Windows Shield Proxy running on your PC?" then check that ShieldProxy.exe is allowed through Windows Firewall on public and private networks.