342156 / android-wifi-tether

Automatically exported from code.google.com/p/android-wifi-tether
0 stars 0 forks source link

my computer doesnt show up on the access control screen but it says on my computers network connection it has limited connectivity to the g1 tether #124

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. connecting with or without wep encryption
2. wifi is enabled on pc and g1
3.

What is the expected output? What do you see instead?
limited connectivity on my network connection on vista, and no user on 
access control

What version of the product are you using? On what operating system?
1.51 on windows vista and cyanogen mod 3.8.6.1

Please provide any additional information below.

Original issue reported on code.google.com by amaadkha...@gmail.com on 4 Aug 2009 at 11:29

GoogleCodeExporter commented 9 years ago
Sounds to me like you have a problem on the client side (pc/vista).

Please do some checks and post results:

- Open a command-prompt.

1) Check the wifi-interface.
type: ipconfig
Look for the wireless adapter. On my german win7 it looks like this:

Drahtlos-LAN-Adapter Drahtlosnetzwerkverbindung:

   Verbindungsspezifisches DNS-Suffix:
   Verbindungslokale IPv6-Adresse  . : fe80::852b:c1fe:2930:365c%14
   IPv4-Adresse  . . . . . . . . . . : 192.168.2.103
   Subnetzmaske  . . . . . . . . . . : 255.255.255.0
   Standardgateway . . . . . . . . . : 192.168.2.254

2) Are you able to ping the gateway?
ping 192.168.2.254

example-output:
C:\Users\Harry>ping 192.168.2.254

Ping wird ausgeführt für 192.168.2.254 mit 32 Bytes Daten:
Antwort von 192.168.2.254: Bytes=32 Zeit=4ms TTL=64
Antwort von 192.168.2.254: Bytes=32 Zeit=4ms TTL=64
Antwort von 192.168.2.254: Bytes=32 Zeit=5ms TTL=64
Antwort von 192.168.2.254: Bytes=32 Zeit=4ms TTL=64

Ping-Statistik für 192.168.2.254:
    Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
    (0% Verlust),
Ca. Zeitangaben in Millisek.:
    Minimum = 4ms, Maximum = 5ms, Mittelwert = 4ms

Original comment by harald....@gmail.com on 5 Aug 2009 at 8:34

GoogleCodeExporter commented 9 years ago
Harold, 
I was able to ping just fine the following is what i got:
     ping statistics for 192.168.1.1
          packets: sent = , received = 4, lost = 0 <0% loss>
     approximate round trip times in milli-seconds:
          minimum = 1ms, maximum =4ms, average = 2ms

I am able to connect to other routers and access points just fine. I've 
restarted my 
phone and my computer numerous times. Stumped.

Original comment by amaadkha...@gmail.com on 6 Aug 2009 at 12:13

GoogleCodeExporter commented 9 years ago
You have pinged 192.168.1.1 and not 192.168.2.254!?

Do you get an ip-address from the phone? Check that please by typing "ipconfig" 
(look
for the wireless-adapter) in a command-prompt and post results.

Original comment by harald....@gmail.com on 6 Aug 2009 at 7:30

GoogleCodeExporter commented 9 years ago
I used 192.168.1.1 because that was my default gateway. But this is what 
ipconfig 
returns when I am connected to the G1Tether network with limited connectivity:

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\owner>ipconfig

Windows IP Configuration

Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . : mshome.net
   Link-local IPv6 Address . . . . . : fe80::a55a:3d44:b0ed:5185%9
   IPv4 Address. . . . . . . . . . . : 192.168.1.2
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.1.1

Ethernet adapter Local Area Connection:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : field.nml.com

Tunnel adapter Local Area Connection* 7:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Local Area Connection* 9:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Local Area Connection* 10:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Local Area Connection* 13:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :

Tunnel adapter Local Area Connection* 14:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . : mshome.net

C:\Users\owner>

Original comment by amaadkha...@gmail.com on 6 Aug 2009 at 9:17

GoogleCodeExporter commented 9 years ago
Do you think this had to do with Cyanogen's ROM? I am using 3.9.7 right now and 
it is 
not working and previously when i made my first post i was running Cyanogen 
3.8.6.1. 
Thanks Harold i really appreciate the time your giving me. Donation coming your 
way no 
matter the results.

Original comment by amaadkha...@gmail.com on 6 Aug 2009 at 9:20

GoogleCodeExporter commented 9 years ago
PC OS: Windows Vista Home Premium (x86-32) (Yes, I know. It came with the 
laptop, 
which is due for replacement in the next few weeks.)
Handset: T-Mobile G1 (UK)
OS: OpenEclair 1.2.2 (25/02/10)

I seem to have a similar problem running OpenEclair 1.2.2 on my UK T-Mobile G1. 
It 
came with a copy of the Wifi Tether pre-installed, but I think the 
configuration 
files were missing, so I went and re-installed it by downloading the 2.00 r7 
version 
assuming this choice OpenEclair ROM is based-on Android 2.1 update 1.

Would this be a hardware-based issue? Should I have gone for the 1.6 version 
instead?

This is what I get on the computer when I punch "ipconfig" into the command 
prompt:

--------------------------------------------------
Wireless LAN adapter Wireless Network Connection:

   Connection-specific DNS Suffix  . :
   Autoconfiguration IPv4 Address. . : 169.254.41.110
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
---------------------------------------------------

The phone also started the tethering "with errors", with the error in the log 
showing:

"Activating WiFi interface..." failed

Any ideas?

Original comment by Cyclonef...@gmail.com on 5 Mar 2010 at 9:30

GoogleCodeExporter commented 9 years ago
@Cycloneflame:
please open a new issue-report here:
http://code.google.com/p/android-wifi-tether/issues/entry

I will close this old issue report. thanks.

Original comment by harald....@gmail.com on 5 Mar 2010 at 11:07