Related
Anyone get these two to play nice together?
Details:
Cisco PIX 501e at the office
WM6 3g phone (HTC TyTn II)
vista/xp laptop (working properly on either would be great right now )
VPN setup on the pix is, i believe, fine. I could be wrong tho, i set it up by trial and error + reading the manual having never even touched a cisco device before
It works tho and has worked flawlessly for months now with Cisco VPN Client on XP or Vista machines.
Old phone was WM5 and used the clunky and annoying modem emulator to enable a laptop to use it to connect to intarwebs in the middle of nowhere, this was great and after faffing about getting it setup worked fine (required you to be logged in as administrator on vista tho :\ and not just a user account with admin privileges, actually administrator. Annoying.)
New phone is WM6 and uses internet sharing to connect with a laptop, this is a much better solution with no faffing about in vista and XP
Problem: Cisco VPN client connects to the pix through Internet Sharing on the phone just fine, however no traffic gets through.
Cannot ping, web browse, dns, rdc or anything to the network at work. Tried with Cisco VPN client v4.6.00.0049 and v5.0.01.0600 on XP and v5.0.00.0340 on Vista, none work.
This sucks
Now, i know its not a problem with the laptop or the vpn software on the laptop as these work fine when connected over ethernet or wifi.
Its not a problem with the phone's 3g connection, i installed a trial of bluefire vpn client onto it and that connects to the vpn and works just fine when the phone is in standalone mode.
However for the life of me i cannot get the two bloody things to work together.
Plz halp
Hi,
Often times, the inability to ping a local host (computers or other connected devices e.g router, hardware firewall, printer, PPC, etc) or hosts, is due to the firewall not allowing traffic through the router. It can also be that the hosts are incorrectly configured to be on different subnets, even though they are local, as in your own case.
Proceed as follows to troubleshoot:
a). Ping the router
Note that the idea is to see if we can establish communication with the router or hardware firewall such as the Pix.
At command prompt (c:\>) type:
ping 192.168.0.1
(each router manufacturer uses a different default internal IP address for its router) - the one above is for a Netgear or D-Link router - for a Cisco router, you would need to know the Cisco IOS command - see your router manual for this.
b). ipconfig /all
Note: there is a space before the forwardslash.
When it returns the parameters, check to see that the IP addresses are all on the same subnet.
This is crucially important for you to take good note. If you are not able to ping a local host or gateway, it's most likely due to this.
c). Ping the Pix Firewall (using its IP address)
d). Ping a remote IP address, e.g. your ISP's gateway or DNS server
e). Is there traffic? If it returns successfully, then ping the other hosts, including the VPN client.
Pix Firewall
Check to see that the Access Control List is configured correctly by ensuring that the IP addresses of the connected hosts have been entered, with the relevant access rights.
Router
Log on to the router. Whilst there:
Ensure that the hosts (computers, etc) are all on the SAME subnet. If they are on different subnets, you must correct the IP addresses to reflect that they are on the same subnet.
Note: If you do really want them to be on different subnets, then you need to use a default gateway.
Hope this helps.
kiwi992.
What is the method for configure the remote desktop program on this device.?
The computer you want to control needs to be XP professional, W2K professional, Vista business or ultimate, or one of the various windows server versions.
On the computer, right click My Computer, select properties, go to the remote tab (on vista select Remote Properties on the left).
Select Allow remote connections.
If you're running a Home version, then as you're not a business user, you are deemed to not need this business function.
Look up RDP and MSTSC in google.
1)configure allow remote desktop connection as described in above post
2)now how is ur pc connected to net?
its recommended that u should not be behind firewall and ur pc should be directly connected to internet with its own ip and make sure ur antivirus firewall is also preferably disabled
3) today's dsl service providers usually allot dynamic public ip adresss to pc so just click the properties of ur dail up broadband connection and note down ur ip adress ( dsl modems are usually always online connection you have to check and modify ur dsl router settings to bridge connection mode and create a dail up connection on desktop ;before modifying any setting in dsl modem make sure u have ur username password for dsl connection and have a back up of dsl router settings)
4)just note down ip and write it in computer box in remote desk top connection in ur handheld
in username field put ur pc user name
in password field put ur pc password
5)just press connect hopefully its done
but some times it really sucks......
Definitely make sure you're behind a firewall! You usually are with your asdl router.
Open port 3389 and forward it to your PC.
For extra security, you can configure your PC to listen on a different port, and configure the router to use that of course.
As commando0 says, you're most likely to have a dynamic IP address, meaning whenever your router connection drops, you'll more than likely get a new address from your ISP, so do get around this, you can use dynamic dns (check dyndns.org).
So use your dyndns address to connect via the internet, and your PC's name for when connecting at home via wifi.
xaccers said:
Definitely make sure you're behind a firewall! You usually are with your asdl router.
Open port 3389 and forward it to your PC.
For extra security, you can configure your PC to listen on a different port, and configure the router to use that of course.
As commando0 says, you're most likely to have a dynamic IP address, meaning whenever your router connection drops, you'll more than likely get a new address from your ISP, so do get around this, you can use dynamic dns (check dyndns.org).
So use your dyndns address to connect via the internet, and your PC's name for when connecting at home via wifi.
Click to expand...
Click to collapse
hi i forwarded port 3389 to my pc (192.169.1.5)
enabled the firewall to listen to that port,
enabled remote connection on vista
but its still not connecting.. i tried using my external as well as lan ip.. nothing seems to work
btw, yes ive been connecting using wifi
anyone uses logmein on here??
Just to confirm, what version of Vista are you running? Business or Ultimate?
On the remote tab of System properties, make sure you've selected "Allow connections from computers running any version of Remote Desktop (less secure)"
Click the "Select Users" button and make sure it says your username already has access, if not, add your username to the list.
Once you've done that, open a cmd window and type:
telnet localhost 3389
then press enter and you should get a blinking curser.
That means your computer is accepting remote desktop connections.
Hold down ctrl and press ] then at the prompt type exit to close the telnet session window.
Then try from your phone.
Logmein.com works perfect over the internet to connect to your pc from a WM device, realy fast and smooth and you can customise the display settings to maximise your speed and refresh rate. 100% recommended
The best use I ever had with Logmein was using it with my HTC Universal, it was so good having VGA and a qwerty keyboard.....
I remember once sat in a pub I needed a file from my PC at home ASAP (to settle an alchole fueled argument, lol), I connected within 30 secs and E-mailed the file to my phone from home. Amasing, also works with any windows OS, I have been using it for about 4 years and its still 100% free.
Hi everyone,
I would like to connect to my laptop next room from local network. I can connect perfectly when I type in my IP address into the first textbox (Computer), but I can't connect when I type in my Computer Name (full computer name) instead. I tried MyPCName as Computer, \\MyPCName as Computer, forwarding port 3389 to my IP, leaving domain name empty, putting in my workgroup name as a domain, putting in my computer name as a domain, putting in myPCName\MyUserName as Username, \\MyPCName as Computer, still the same. It won't connect unless I put in the IP address. I would like to do this since my workplace assigns a different IP to my laptop then I assign at home, but naturally I have the same computer name at both places, so I would like to have a permanent setting for both places.
I'm running Windows 7 64 bit on my laptop and 1.66.405.2 ROM on my HTC HD2.
Many thanks in advance.
can you connect to it ok using another computer? might be a dns issue at a guess...
I can connect from other computers fine. Also on my HD2 I can see the host names of PC's under Resco Explorer and map them. However, remote desktop mobile refuses to work with the Computer Name. I can ping my Laptop's IP and also Computer name from pingbox2. Only in Remote Desktop Mobile there is a problem.
windows 7 by default blocks remote desktop connections from different versions of remote desktop. if you right click computer and select properties, then choose remote settings on the right hand side and select the middle option (accept connections from all verions of remote desktop). havent tried this my self but it solves most issues when using different versions of windows
OK, I sort of figured it but would still appreciate some help. Here is how I got it to work:
I had OpenDNS IP under DNS settings for wireless adapter. I deleted them. If I don't do this, pinging my computer name from HD2 always brings 67.215.65.132, which is opendns and not my true local IP, i.e. 192.168.x.x. I also had to disable the data connection (3G) and only have wireless. If I don't disable 3G, I can only connect with IP and not computer name. Only after doing these 2, when I pinged my computer name, I got the true local IP and I was able to connect with Remote Desktop Mobile using computer name. Now my question is:
1- I don't want to quit using opendns, is it possible?
2- I don't want to disable 3G connection every time, is it possible?
thanks in advance.
For me it works with MyPCName in computer and empty domain, both for XP and 7.
Something seems strange with your phone's networking configuration. At a guess (and this is a long shot), I would check your VPN settings on your phone to make sure you're not connecting to a different domain over 3G as this might explain why it works when you turn off the data connection on the phone and why it works by IP address.
As I said though, it's a long shot and is the only thing I could think of that fits your particular symptoms...
ozkaya said:
OK, I sort of figured it but would still appreciate some help. Here is how I got it to work:
I had OpenDNS IP under DNS settings for wireless adapter. I deleted them. If I don't do this, pinging my computer name from HD2 always brings 67.215.65.132, which is opendns and not my true local IP, i.e. 192.168.x.x. I also had to disable the data connection (3G) and only have wireless. Only after doing these 2, when I pinged my computer name, I got the true local IP and I was able to connect with Remote Desktop Mobile using computer name. Now my question is:
1- I don't want to quit using opendns, is it possible?
2- I don't want to disable 3G connection every time, is it possible?
thanks in advance.
Click to expand...
Click to collapse
about the open dns issues, I suspect that can be solved by making sure your router lets the incoming connection into your home network (you say it resolves to 66.whatever when open dns is used, shouldn't be a problem do long as you don't forget that will be your home ip address so that connection will neef to be allowed through the router and then forwarded by your routers virtual server (our whatever your router software calls out) to your laptops internal ip address.
as for the 3g it should use wifi over 3g by default..... mine certainly does, no need for me to disable it.
tomallen35 said:
Something seems strange with your phone's networking configuration. At a guess (and this is a long shot), I would check your VPN settings on your phone to make sure you're not connecting to a different domain over 3G as this might explain why it works when you turn off the data connection on the phone and why it works by IP address.
As I said though, it's a long shot and is the only thing I could think of that fits your particular symptoms...
Click to expand...
Click to collapse
I think you're right, when the 3G is on (and also Wifi on), Resco shows computers from all around the country when I click computers near me and not my local network. When only wifi is on I can see my local computers. 3G probably has precedence over Wifi? How can I correct this?
samsamuel said:
about the open dns issues, I suspect that can be solved by making sure your router lets the incoming connection into your home network (you say it resolves to 66.whatever when open dns is used, shouldn't be a problem do long as you don't forget that will be your home ip address so that connection will neef to be allowed through the router and then forwarded by your routers virtual server (our whatever your router software calls out) to your laptops internal ip address.
as for the 3g it should use wifi over 3g by default..... mine certainly does, no need for me to disable it.
Click to expand...
Click to collapse
But the 66.whatever address is generic openDNS lookup IP and same for everyone. Are you suggesting me to route this IP to my local IP, i.e. 192.168.x.x? Oh, one more thing, I can also connect when 3g and wifi are both on, but only through computer's IP and not computer name. Can you connect with computer name while both are on and connected?
when your phone does a dns lookup on the name it resolves to the open dns assigned address (not the same for everyone, otherwise the open fns system wouldn't work) so to connect to your computer the phone sends its request to open dns who forward that request to your current actual address.at home that address is your home ip address BUT it isn't your laptops address it is your routers address.(stop reading here if you don't have a router).
so the router needs to be told "if you get a connection request in port (whatever the remote desktop port is) please forward it to (laptop ip address)
its called port forwarding in some routers, virtual server in others.
samsamuel said:
so the router needs to be told "if you get a connection request in port (whatever the remote desktop port is) please forward it to (laptop ip address)
its called port forwarding in some routers, virtual server in others.
Click to expand...
Click to collapse
You're mixing up things a bit - he's not using dns but the computer netbios name. The point is that he has wifi on and connected as well as 3G, thus with an "intranet" ip address on Wifi... so the program/phone should be looking up the name on that connection, where it would find it, instead of looking up over the 3G connection. As the netbios protocol is not routable, it has no chance of finding the computer name over 3G/internet and back home, even with port mappings.
kilrah said:
You're mixing up things a bit - he's not using dns but the computer netbios name. The point is that he has wifi on and connected as well as 3G, thus with an "intranet" ip address on Wifi... so the program/phone should be looking up the name on that connection, where it would find it, instead of looking up over the 3G connection. As the netbios protocol is not routable, it has no chance of finding the computer name over 3G/internet and back home, even with port mappings.
Click to expand...
Click to collapse
you're totally right, I have a router and its port is forwarded to my laptop IP, but this is only good (and works well too) when I want to connect from Internet to my local network. I tried OpenDNS exceptions for VPN and defined an exception named as MyComputerName but it didn't work. Then I tried a dyndns solution, but it only works for external connections and not local network, i.e. it can't map local IP's. What I need is a dynamic client which can update my local IP.
I also tried to edit hosts entry in the registry with MyComputerName. It works for a single IP, but I'm not sure if I can write multiple IP adresses (my work and home local IP) into that. If I could maybe everything would be OK.
I've just tried a couple of things and it really works fine for me. If I connect Wifi only, I can remote desktop with the computer name. If I then connect data connection, it still works. Disabling wifi and obviously it doesn't work anymore. Re enabling wifi, it doesn't work at first, but does again after ~30 seconds once the netbios protocol has done its host lookup procedures.
There simply shouldn't be anything special to do.
kilrah said:
I've just tried a couple of things and it really works fine for me. If I connect Wifi only, I can remote desktop with the computer name. If I then connect data connection, it still works. Disabling wifi and obviously it doesn't work anymore. Re enabling wifi, it doesn't work at first, but does again after ~30 seconds once the netbios protocol has done its host lookup procedures.
There simply shouldn't be anything special to do.
Click to expand...
Click to collapse
thank you very much for your time, I appreciate it. You're right in that waiting a bit resolves the issue (it's a bit more than 30 secs for me that's why I thought it wasn't working when 3G is enabled) but only when OpenDNS is not used. I assume you don't use OpenDNS, right? Once I put that one into equation, it takes over NetBIOS protocol and returns its IP instead of the local IP(192.168.x.x). As far as I understand, DNS lookup has precedence over NETBIOS and if the name is not found in DNS it consults NETBIOS protocol. However OpenDNS has this nice "feature" where it finds the name with its own IP. There are several posts about this on its webpage and they say to either disable the typo correction or put exceptions for Netbios names, but sadly none of them works for me right now.
Nope, no OpenDNS, never actually heard of it.
How does it work? Do you enter their DNS server address in the network settings of your pc/phone, or is it an app you run?
you click Start/Settings/All Settings/Connections/Wifi/First Button/Switch to Network Adapters tab/Select Broadcom 802.11 DHD Network Adapter/Switch to Name Servers Tab/Type in 208.67.222.222 for primary DNS and 208.67.220.220 for secondary DNS, click OK. that's all. Could you try if it's not so much trouble? Thanks.
OK, remote desktop doesn't work either with the OpenDNS servers in.
I'm pretty sure it must be a limitation of the remote desktop app itself, as resco explorer can still navigate and/or discover the network shares of my other PCs with no problem. NBTStatCE also finds everybody.
Wouldn't even surprise me, as that Remote desktop mobile has always been troublesome. I don't remember exactly, but in the WM5 days it was pretty much impossible to use on a local network due to a weird handling of names... if I remember well all "local" (NetBIOS) addresses without a '.' entered in the remote desktop app would be redirected to the "Work" connection, while "remote" ones with a period would be directed on the "Internet" connection. As a network card can only be defined as one of them, if you wanted it to work in both cases through Wifi you had to switch the card from Work to Internet and back all the time. And of course when it's on Work it breaks some other things that use the default system handling like mail.
I'm trying to figure out how to set up remote desktop... I'm using Kumars rom... not that that makes a difference i dont think. anyways. I'm running Windows 7 on my computer.
start ->
right click on "My Computer" ->
Properties ->
remote settings (top left hand)
remote tab ->
Allow remote assistance connections to this computer box is checked
allow connections from computers running any version of remote desktop (less secure) is checked ->
on to my phone...
i go to remote desktop mobile on it... I've read online that for the Computer dialog box i input my computers IP address... now, is that the IPV4 address that i get from the CMD box after typing IPCONFIG... or is it the address that i get when i browse over to the website www.whatismyipaddress.com ??
what do i put for my user name and password? is it my PC's password and user name? also... my ISP (internet service provider) is Verizon. i currently have their built in wireless modem up and running. i've seen the tutorial on youtube of how to set up remote desktop by going in to my router and port forwarding numbers... but thats also something i am having trouble with.... ive been cracking my head at this for over 3 hours. can someone please help
Nano3 said:
I'm trying to figure out how to set up remote desktop... I'm using Kumars rom... not that that makes a difference i dont think. anyways. I'm running Windows 7 on my computer.
start ->
right click on "My Computer" ->
Properties ->
remote settings (top left hand)
remote tab ->
Allow remote assistance connections to this computer box is checked
allow connections from computers running any version of remote desktop (less secure) is checked ->
on to my phone...
i go to remote desktop mobile on it... I've read online that for the Computer dialog box i input my computers IP address... now, is that the IPV4 address that i get from the CMD box after typing IPCONFIG... or is it the address that i get when i browse over to the website www.whatismyipaddress.com ??
what do i put for my user name and password? is it my PC's password and user name? also... my ISP (internet service provider) is Verizon. i currently have their built in wireless modem up and running. i've seen the tutorial on youtube of how to set up remote desktop by going in to my router and port forwarding numbers... but thats also something i am having trouble with.... ive been cracking my head at this for over 3 hours. can someone please help
Click to expand...
Click to collapse
For username and password, don't bother with them. You MUST have user logins setup on your PC for this to work. When you eventually do connect to your PC, you'll be presented with the login screen, so you can enter authentication information there instead. Yes, it's your login and password for your PC, but you don't need to worry about that to actually connect.
Without seeing your specific router setup, it's difficult to help with the next part. Go to start, run and type cmd. Type IPCONFIG - this will give you the IP address that your computer has. You need to allow all traffic on port 3389 to go to that IP address. There will be something about port forwarding in your router setup (which I have to assume you know how to access).
If you have trouble, google for the model number of your router and "port forwarding" and you're bound to find a how-to page.
Incidentally, that IP address is your "internal" IP address - the one that your router assigns to your PC so you can communicate with it. When you go to whatismyipaddress it tells you the IP address of your router. You need to connect to that from outside, and the port forwarding says "someone's connecting to me on port 3389 via my external IP address. I've got port forwarding set up to allow traffic on that port to go to an internal IP address." (You may not hear it say that )
this is the screen on my ip router set up
Looks fine. So did you try logging in?
These instructions won't work if you have more than one device in your house using that router and each device will get its own IP from the router, so when a request comes in from the outside network, it won't know which IP to send the request to.
**UNLESS** you're doing it over WIFI from your phone, which would already put you on the inside network so you don't need to worry about that.
Tell us, are you trying to connect using 3G, or are you trying to connect using your in-house WiFi using the router?
zdrux said:
These instructions won't work if you have more than one device in your house using that router and each device will get its own IP from the router, so when a request comes in from the outside network, it won't know which IP to send the request to.
Click to expand...
Click to collapse
Good point - I didn't pick up on the fact that the port forwarding is not asking for an end IP address.
As zdrux says, if you're connecting your HD2 to your wireless network then you can connect to your PC directly, using the internal IP address, as mentioned in the post above.
Nope not working... im getting really irritated. i dont understand why it isnt working. do i need to be connected through my own wifi? or should i disable it?
You don't need to connect via your own wifi, as long as your router is doing it's job properly. It's easier to connect via wifi though, as you can rule out the router completely and at least get it working.
A few questions...
Do you have to log onto windows with a username and password?
Do you have windows firewall on?
What version of Windows 7 is it?
Nano3 said:
Nope not working... im getting really irritated. i dont understand why it isnt working. do i need to be connected through my own wifi? or should i disable it?
Click to expand...
Click to collapse
Nobody will help if you can't answer our questions.
- Are you connecting through 3G, or through you WiFi at home? Where do you get your connection on your phone?! This is important.
- Turn off windows fire-wall completely until you solve this so you know its not getting in the way.
- Go to Control Panel > System and Security > System ..and click on "Remote Settings" in the left pane, once a new window opens up, make sure you check the box where it says "Allow assistance from other computers" and also a little lower where it says "Allow other versions of windows to connect to this computer".
- Go to your router and look for an option where you can set a computer as the DMZ, put in the IP of your computer in that box if you have one of those boxes as an option. This is the IP you see when you type "ipconfig" on your computer.
- Go to www.canyouseeme.org to test if your Remote Desktop port is open. Once you get to that webpage, type in port number 3389 and click "Check", this will confirm if it's an issue with your computer or your phone.
- Like the other person said, if this doesn't work, try connecting your computer without a router. Just get the cable running from the modem straight into your network card, unless you have one of those router/modem all-in-one things.
If you are connecting over the home wifi, then you shouldn't need to go near port forwarding, or indeed your router at all.
the target ip is the PC address you get from cmd - ipconfig (192.168.....) and as johnc said, you can leave user and pass blank and log in directly.
If you are wanting to connect over your phones data, then the target ip is found either by visiting whatismyip or in the router, look for the wan ip address. (Example 82.27.19.187)
and in that case you set up in your router a port forward from external port 3389 to internal address (your pc address from ipconfig) on port 3389.
Hello Everyone,
Not to hijack the thread but, I am having problems using remote desktop also. Maybe you can help.
Host Computer: Notebook
OS: Win xp pro
Connectivity: T-Mobile USA PCM/CIA card gprs/edge/3G
User name has Admin Privileges
In Security Center, Firewall. I made exceptions for Remote Desktop and Remote Assistance.
When I goto www.canyouseeme.org on the notebook on the t-mobile wireless card, Error: I could not see your service on on port 3389 Reason: Connection refused
Client: HD2
Connectivity: T-Mobile USA 3G
On the HD2 I put:
Computer: IP address of the host computer
User name: Name of Admin Privileged User
Password: Password that corresponds to the user name
When I goto www.canyouseeme.org on the HD2, Error: I could not see your service on on port 3389 Reason: Connection refused
1) On the host computer, Must all users be logged off and the computer at the login screen or can I be logged in on an Admin User?
2) If users must be logged off, I can go to Task Manager and disconnect user that will be used to login with remote desktop?
3) T-Mobile USA Blocking ports 3389?
If I log out of the user, I go to the login screen but the wireles connection is terminated.
My Goal:
I have a notebook in my work vehicle on the T-mobile air card (Wireless ) and while I am in a building working, I would like to connect to the notebook in the vehicle with my HD2 instead of walking back and forth or having to carry my notebook with me.
If you need more information, I will do my best to give exact details.
Thank you,
Monnie
You left out a step on the PC.
On the Remote screen setup on the PC you have to add the Login IDs that will be allowed to login remotely.
Hello Everyone,
I called T-mobile usa, spoke with their PDA/Smartphone Tech Support, They could not give me an answer that A) They are blocking ports 3389 or B) They are not blocking ports 3389.
The tech continued to asked me over and over again " did that application come on the phone or you installed it" I told him repeatedly " Remote desktop come loaded on the factory T-mobile ROM"
He then said, they are working with their network dept and directly with HTC
Just a heads up
Thank you,
Monnie
tms02 said:
You left out a step on the PC.
On the Remote screen setup on the PC you have to add the Login IDs that will be allowed to login remotely.
Click to expand...
Click to collapse
You have to connect first before you can even think of logging in. We still didn't get to that part.
MonnieRock said:
Hello Everyone,
I called T-mobile usa, spoke with their PDA/Smartphone Tech Support, They could not give me an answer that A) They are blocking ports 3389 or B) They are not blocking ports 3389.
The tech continued to asked me over and over again " did that application come on the phone or you installed it" I told him repeatedly " Remote desktop come loaded on the factory T-mobile ROM"
He then said, they are working with their network dept and directly with HTC
Just a heads up
Thank you,
Monnie
Click to expand...
Click to collapse
This is irrelevant, the website checks to see if the port on your PC is open, this has nothing to do with the phone (yet). If your port 3389 is open and accepting connections, the website should say so, nothing to do with the phone at this time.
This basically means your computer has port 3389 shut off/blocking, figure out what's doing that and then you can connect.
johncmolyneux said:
You don't need to connect via your own wifi, as long as your router is doing it's job properly. It's easier to connect via wifi though, as you can rule out the router completely and at least get it working.
A few questions...
Do you have to log onto windows with a username and password?
Do you have windows firewall on?
What version of Windows 7 is it?
Click to expand...
Click to collapse
I do have a username and password
windows firewall is on
windows 7 ultimate 64 bit
Here is basically a run-down of what I did. I hope this helps everyone out.
Device specs:
Samsung Galaxy Player 4.0 Rooted
Network Specs:
DSL Modem
Router (DHCP with WPA security and does not have MAC Filtering)
4 Access Points (all on same channel broadcasting same SSID with same WPA security DHCP)
2 Servers - Static IPs
-Server 1 - DNS (not sure if it is actually a DNS server or just forwards the requests). Also storage/application server.
-Server 2 - Storage/Application/SQL server
Many clients on network (unsure of total amount but somewhere around 30 would be my guess)
Problem (note this is only on this network, every other network wifi
works just fine):
Wifi Connected but no internet.
My Windows 7 laptop (same network) gets internet access with no problems
No reports of any other clients on the network having this issue
Device has assigned a good DHCP IP address
Subnet, Gateway, and DNS IPs are all correct (they match the ones on my laptop)
Connection strength is great (speed is 52mbps)
Device has full local access (intranet). It can access all files and other devices on the network.
On occasion the device will get "internet" access for a brief period of time but will go back to "intranet" access only after a few minutes.
Tests Performed (My android device will be referred to as "device" my laptop will be reffered to as "laptop". All tests were performed with both laptop and device connected to the network in question, unless otherwise specified, and device was not able to access internet):
Ping from laptop to device - Successful
Ping from device to laptop - Successful
Ping from laptop to gateway - Successful
Ping from device to gateway - Failed
Resolve DNS IP on device - Successful
Resolve DNS IP on laptop - Successful
Ping from laptop to google - Successful
Ping from device to google - Failed
Small FTP file transfer from laptop to device - Successful
Small FTP file transfer from device to laptop - Successful
Device has no problems on other networks (tried un-secured, WEP, and WPA/WPA2)
Connect device using Google public DNS servers
-Intranet - Successful
-Internet - Failed
-Resolve DNS IP - Successful
Connect laptop using Google public DNS servers
-Intranet - Successful
-Internet - Successful
-Resolve DNS IP - Successful
More that I cannot remember right now. Will add as they come to me.
At this point I gave up for a few days. Every test and every bit of research returned nothing. I had spent many many hours trying to figure this out and testing theories and nothing ever pointed me in the right direction of where to go. Nothing made sense EVERY single setting is the same is on my laptop. Started thinking maybe there was something in the router that could be blocking Android devices (since it is a work network). Although I am not a aware of a router feature to do that I figure I would try some more tests.
Testing Round 2 (same conditions as initial tests):
Configured laptop to be a Wifi hotspot.
-From CMD command 1: netsh wlan set hostednetwork mode=allow ssid=AP key=XXXXXXXXX
-From CMD command 2: netsh wlan start hostednetwork
-From network and sharing center: Shared the physical wireless network connection with the Microsoft Virtual WiFi Miniport Adapter.
-The above commands create a virtual wireless adapter and set it broadcast the specified SSID with the specified WPA security key. Then you can choose any available, connected, physical, internet connection and share it's internet connection with the virtual connection, thus theorectically turning my laptop into a 5th access point on the network.
Connected device to the SSID "AP"
-Intranet - Successful
-Internet - SUCCESSFUL
Horray!!!! Progress! So with the above information I went to our IT guy and we sat down and looked at some stuff (settings in the router, access points, and servers). After digging and digging around within the settings we came up with.... you guessed it NOTHING!!!!!!!!!!!!! Now I was in "Its on!" mode and decided I wasn't going to stop until I found out at least what was causing the problem. My IT guy was also very determined to figure this out as he doesn't like to get beat either. So we both went at it. We decided the first thing to do was make a very detailed network map containing every piece of information we could possibly find. We did this all from his machine (laptop with Windows 7) and wrote everything down on paper (we even used a piece of our 36" wide roll paper from our plotter to make sure everything would fit) and made an excel spredsheet with all the info. Now with the newly aquired network information I decided I was going to do more testing.
Testing Round 3 (same conditions as initial test):
Map the entire network again gathering every piece of information possible just like before but this time using MY DEVICE (not my laptop).
Compare
Finally! I have found the problem! As stated before my device was getting the correct gateway IP (XXX.XXX.XXX.1) which is the same as my laptop). However the assigned MAC address OF THE GATEWAY (router) to my device is XX:XX:XX:XX:XX:FB but the MAC address OF THE GATEWAY (router) to my laptop is XX:XX:XX:XX:XX:FA. Got back with our IT guy and we found (by looking the router config) that the XX:XX:XX:XX:XX:FA is the LAN MAC address for the router. The XX:XX:XX:XX:XX:FB is the WAN MAC address for the router.
Testing Round 4 (same conditions as intial test):
Connected laptop to network, confirmed XX:XX:XX:XX:XX:FA MAC address was assigned for the gateway by running "arp -a" in CMD.
-Pinged google - Passed
-Changed assigned MAC address of gateway by running "arp -s XXX.XXX.XXX.1 XX:XX:XX:XX:XX:FB" in CMD
-Verified new MAC address assignment by running "arp -a" in CMD
-Pinged google - Failed
-Changed the MAC back and pinged google again - Successful
Connected device to network, confirmed XX:XX:XX:XX:XX:FB MAC address was assigned for the gateway by running "arp -a" in Terminal.
-Pinged google - Failed
-Changed assigned MAC address of gateway by running "su" then "arp -s XXX.XXX.XXX.1 XX:XX:XX:XX:XX:FA" in Terminal
-Verified new MAC address assignment by running "arp -a" in Terminal
-Pinged google - Successful
-Changed the MAC back and pinged google again - Failed
Conclusion:
For some reason the device is getting assigned the correct gateway IP but the wrong gateway MAC. This is allowing the device to connect to the network but not communicate with the router. Since it can't communicate with the router any "Internet" requests time out because the packets have to go through the router to make it to the "Internet". Since it is not blocked from the network it can still connect and communicate with other clients on the "Intranet" but not the router.
Our IT guy thinks there is a client somewhere on the network in the same subnet that is configured in this matter and it just so happens that for some reason my device is picking that up when it connects. He is going to look into it more when time permits but since we are very busy and we have already spent way too much time on this, and I now know at least what the issue is, he is going to move on for now.
Why would my device be picking up the WAN MAC address of the router?
What would be responsible for assigning a WAN or LAN MAC address?
How can I prevent this?
Has anyone ever experienced anything like this?
Temporary Solution (must be rooted):
Open your favorite terminal app on your device.
-Enter "su" (without quotes)
-Enter "arp -s [Your gateway IP here] [Your gateway's LAN MAC address here]
Browse away!!!!!
Hello.
I had the same problem, that I could connect to router but had no connection to internet.
Read this post and started to do some research on my router. When I configurated my router, there was an option to clone MAC address. And of course to get it done fast I cloned MAC. And now I checked that it cloned my laptop MAC. Changed MAC from laptop to Routers MAC (must be on label under router) and got a really nice internet connection.
Hi, I think I have the same problem with the same device, Samsung Galaxy Player 4, but even if my device is rooted I still can't excecute the "arp" command from the Terminal application (there is no "arp" command). How can I check/modify the arp list on my device???
I really appreciate your help. Thanks in advance!!!
I use the terminal emulator app. It works just fine for me and I never had to download any other software to be able to run the ARP command.
bmx0964 said:
Here is basically a run-down of what I did. I hope this helps everyone out.
Temporary Solution (must be rooted):
Open your favorite terminal app on your device.
-Enter "su" (without quotes)
-Enter "arp -s [Your gateway IP here] [Your gateway's LAN MAC address here]
Browse away!!!!!
Click to expand...
Click to collapse
anyone found a solution to this ?
just updated to ics4 and cannot connect to the internet.
You only have one device that assigns IP adresses, right?
How about changing the channel to see if that works? or maybe even the security protocol
greeky510 said:
You only have one device that assigns IP adresses, right?
How about changing the channel to see if that works? or maybe even the security protocol
Click to expand...
Click to collapse
the only thing that worked for me is to turn on the dhcp option
in my router. previously, i was using static ips
may_east said:
the only thing that worked for me is to turn on the dhcp option
in my router. previously, i was using static ips
Click to expand...
Click to collapse
I had the sams problem. I could connect with my wifi but had no internet acces. The solution here was the wifi encription.
My smartphone could not encript the hard encription I think. With WEP encription it all works well.
Hey guys,
Here's a run down of the problem I'm currently having. A few months ago I purchased a Dapeng A75 currently running ICS 4.0. Although a beautiful and fast phone, just recently it started going out of wack.
- Youtube and Play Store hang on "Loading" screen
- My Gmail accounts won't sync
- I can no longer search on Google.com with ANY browser through WiFi. (I do not have data service on my phone)
I've tried several attempts at troubleshooting this, all which have failed.
- I restored my phone to factory default.
- Uninstalled and reinstalled these apps.
- Downgraded the apps to previous versions.
- Cleared my cache on just about everything.
- Release and renewed my IP in Terminal.
Just recently I noticed a CWM recovery image posted and I figure this is the only solution. Wiping out the phone and flashing a fresh ROM but unfortunately I can only get as far as installing the drivers to my Windows 7 machine. Some reason when I plug the phone in after installing the drivers, Windows will prompt me that the device is plugged in but before I get a chance to hit F9 for SP Flash Tool to do it's thing, the device quickly disconnects.
NOTE: I am able to browse Google via WiFi only by using HotSpot Shield VPN (Which is problematic in itself).
I'm currently losing the battle with this phone and at my wits end. Is there anyone out there who is experiencing the same situation or has some sort of solution which doesn't involve be shelling out more money for a new phone?
good work brother
i understood the above problem n i too experienced the same problems so now i will take ur research to next level n see my know of network .
i appreciate all the work done you , in research of this LITTLE but hetic problem.
i have learned a lot through u r research.
n will do more n keep u guys posted if i found somthing on this
---------- Post added at 11:11 AM ---------- Previous post was at 11:06 AM ----------
bmx0964 said:
Here is basically a run-down of what I did. I hope this helps everyone out.
Device specs:
Samsung Galaxy Player 4.0 Rooted
Network Specs:
DSL Modem
Router (DHCP with WPA security and does not have MAC Filtering)
4 Access Points (all on same channel broadcasting same SSID with same WPA security DHCP)
2 Servers - Static IPs
-Server 1 - DNS (not sure if it is actually a DNS server or just forwards the requests). Also storage/application server.
-Server 2 - Storage/Application/SQL server
Many clients on network (unsure of total amount but somewhere around 30 would be my guess)
Problem (note this is only on this network, every other network wifi
works just fine):
Wifi Connected but no internet.
My Windows 7 laptop (same network) gets internet access with no problems
No reports of any other clients on the network having this issue
Device has assigned a good DHCP IP address
Subnet, Gateway, and DNS IPs are all correct (they match the ones on my laptop)
Connection strength is great (speed is 52mbps)
Device has full local access (intranet). It can access all files and other devices on the network.
On occasion the device will get "internet" access for a brief period of time but will go back to "intranet" access only after a few minutes.
Tests Performed (My android device will be referred to as "device" my laptop will be reffered to as "laptop". All tests were performed with both laptop and device connected to the network in question, unless otherwise specified, and device was not able to access internet):
Ping from laptop to device - Successful
Ping from device to laptop - Successful
Ping from laptop to gateway - Successful
Ping from device to gateway - Failed
Resolve DNS IP on device - Successful
Resolve DNS IP on laptop - Successful
Ping from laptop to google - Successful
Ping from device to google - Failed
Small FTP file transfer from laptop to device - Successful
Small FTP file transfer from device to laptop - Successful
Device has no problems on other networks (tried un-secured, WEP, and WPA/WPA2)
Connect device using Google public DNS servers
-Intranet - Successful
-Internet - Failed
-Resolve DNS IP - Successful
Connect laptop using Google public DNS servers
-Intranet - Successful
-Internet - Successful
-Resolve DNS IP - Successful
More that I cannot remember right now. Will add as they come to me.
At this point I gave up for a few days. Every test and every bit of research returned nothing. I had spent many many hours trying to figure this out and testing theories and nothing ever pointed me in the right direction of where to go. Nothing made sense EVERY single setting is the same is on my laptop. Started thinking maybe there was something in the router that could be blocking Android devices (since it is a work network). Although I am not a aware of a router feature to do that I figure I would try some more tests.
Testing Round 2 (same conditions as initial tests):
Configured laptop to be a Wifi hotspot.
-From CMD command 1: netsh wlan set hostednetwork mode=allow ssid=AP key=XXXXXXXXX
-From CMD command 2: netsh wlan start hostednetwork
-From network and sharing center: Shared the physical wireless network connection with the Microsoft Virtual WiFi Miniport Adapter.
-The above commands create a virtual wireless adapter and set it broadcast the specified SSID with the specified WPA security key. Then you can choose any available, connected, physical, internet connection and share it's internet connection with the virtual connection, thus theorectically turning my laptop into a 5th access point on the network.
Connected device to the SSID "AP"
-Intranet - Successful
-Internet - SUCCESSFUL
Horray!!!! Progress! So with the above information I went to our IT guy and we sat down and looked at some stuff (settings in the router, access points, and servers). After digging and digging around within the settings we came up with.... you guessed it NOTHING!!!!!!!!!!!!! Now I was in "Its on!" mode and decided I wasn't going to stop until I found out at least what was causing the problem. My IT guy was also very determined to figure this out as he doesn't like to get beat either. So we both went at it. We decided the first thing to do was make a very detailed network map containing every piece of information we could possibly find. We did this all from his machine (laptop with Windows 7) and wrote everything down on paper (we even used a piece of our 36" wide roll paper from our plotter to make sure everything would fit) and made an excel spredsheet with all the info. Now with the newly aquired network information I decided I was going to do more testing.
Testing Round 3 (same conditions as initial test):
Map the entire network again gathering every piece of information possible just like before but this time using MY DEVICE (not my laptop).
Compare
Finally! I have found the problem! As stated before my device was getting the correct gateway IP (XXX.XXX.XXX.1) which is the same as my laptop). However the assigned MAC address OF THE GATEWAY (router) to my device is XX:XX:XX:XX:XX:FB but the MAC address OF THE GATEWAY (router) to my laptop is XX:XX:XX:XX:XX:FA. Got back with our IT guy and we found (by looking the router config) that the XX:XX:XX:XX:XX:FA is the LAN MAC address for the router. The XX:XX:XX:XX:XX:FB is the WAN MAC address for the router.
Testing Round 4 (same conditions as intial test):
Connected laptop to network, confirmed XX:XX:XX:XX:XX:FA MAC address was assigned for the gateway by running "arp -a" in CMD.
-Pinged google - Passed
-Changed assigned MAC address of gateway by running "arp -s XXX.XXX.XXX.1 XX:XX:XX:XX:XX:FB" in CMD
-Verified new MAC address assignment by running "arp -a" in CMD
-Pinged google - Failed
-Changed the MAC back and pinged google again - Successful
Connected device to network, confirmed XX:XX:XX:XX:XX:FB MAC address was assigned for the gateway by running "arp -a" in Terminal.
-Pinged google - Failed
-Changed assigned MAC address of gateway by running "su" then "arp -s XXX.XXX.XXX.1 XX:XX:XX:XX:XX:FA" in Terminal
-Verified new MAC address assignment by running "arp -a" in Terminal
-Pinged google - Successful
-Changed the MAC back and pinged google again - Failed
Conclusion:
For some reason the device is getting assigned the correct gateway IP but the wrong gateway MAC. This is allowing the device to connect to the network but not communicate with the router. Since it can't communicate with the router any "Internet" requests time out because the packets have to go through the router to make it to the "Internet". Since it is not blocked from the network it can still connect and communicate with other clients on the "Intranet" but not the router.
Our IT guy thinks there is a client somewhere on the network in the same subnet that is configured in this matter and it just so happens that for some reason my device is picking that up when it connects. He is going to look into it more when time permits but since we are very busy and we have already spent way too much time on this, and I now know at least what the issue is, he is going to move on for now.
Why would my device be picking up the WAN MAC address of the router?
What would be responsible for assigning a WAN or LAN MAC address?
How can I prevent this?
Has anyone ever experienced anything like this?
Temporary Solution (must be rooted):
Open your favorite terminal app on your device.
-Enter "su" (without quotes)
-Enter "arp -s [Your gateway IP here] [Your gateway's LAN MAC address here]
Browse away!!!!!
Click to expand...
Click to collapse
i would like to add if u have seen the
cmd-ncpa.cpl-ipv4-propreties- in this section u see its Dhcp so all fields are inactive
but u can see gateway ip which is inactive such as in my case 192.168.1.1
u cannot remove that.
any body saw the reply....
thanks regards
bmx0964 said:
Temporary Solution (must be rooted):
Open your favorite terminal app on your device.
-Enter "su" (without quotes)
-Enter "arp -s [Your gateway IP here] [Your gateway's LAN MAC address here]
Browse away!!!!!
Click to expand...
Click to collapse
Thanks, This Solution Saved me Today