Netgear WGR614 wireless router and XP - connection exists but no data transfer

Hi,

I'm having a problem with a computer connecting to my wireless router.
The router is Netgear WGR614. The computer has Windows XP. So I enable
the access point, assign a unique SSID, enable 128bit WEP, and enter
the key that I automatically generated via the computer I'm trying to
connect.

Sure enough, Windows XP sees the network and connects to it. The link
status is "Connected". However I only see outgoing data transfer on
the link. It can't receive anything.

I can't ping the router and even the router "Connected device table"
doesn't list the computer on the network. Anyone have any ideas as to
what is causing this?

Thanks!
L

"L. Li" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Hi,
>
> I'm having a problem with a computer connecting to my wireless
router.
> The router is Netgear WGR614. The computer has Windows XP. So I
enable
> the access point, assign a unique SSID, enable 128bit WEP, and enter
> the key that I automatically generated via the computer I'm trying
to
> connect.
>
> Sure enough, Windows XP sees the network and connects to it. The
link
> status is "Connected". However I only see outgoing data transfer on
> the link. It can't receive anything.
>
> I can't ping the router and even the router "Connected device table"
> doesn't list the computer on the network. Anyone have any ideas as
to
> what is causing this?
>
> Thanks!
> L

Leave WEP disabled till you get it working..
Are you getting a good IP address?

go to the status tab on your connection properties and check if the I
is within the range defined in the router

Also, check if you have any firewall filtering the ICMP packets tha
could be filtering the ping command

--
gonsa
brought to you by http://www.wifi-forum.com

Yeah I was thinking I'll try that when I get home tonight. I've
configured a static IP address within the defined range I've set on the
router. So I'm not able to tell, I don't think.

It is within the defined range. I've set up static IP addressing on the
network so I've made sure that everything fits. I have two other
computers (wired connections) on the network within the same address
space and they're working just fine.

I've disabled all firewalls on the system. So the pings aren't
filtered. Regardless, no data is actually coming back. DNS lookups
fail, etc. The fact that the router can't see the computer is what
disturbs me, when WinXP says it should.

L. Li <(E-Mail Removed)> wrote:
> I'm having a problem with a computer connecting to my wireless router.
> The router is Netgear WGR614. The computer has Windows XP. So I enable
> the access point, assign a unique SSID, enable 128bit WEP, and enter
> the key that I automatically generated via the computer I'm trying to
> connect.

What client card are you using? Which of the WGR614 router models are you
using?

I have a WGR614v4 Firmware Version 5.0_02.

I have a Netgear WG511 in a WinXP-SP2 laptop. It didn't work initially,
although I forget now what the symptom was. I had to upgrade the firmware
to get it to work on WinXP. Driver 2.1.25.0 Firmware 2.04.12.00 Driver
Date September 06, 2004

When I first configured WEP, I had to delete the Windows profile that had
the SSID of the non-WEP router, or change the SSID so Windows would
configure correctly and pop up a WEP key page.

I have run no encryption, WEP-64, WEP-128, and WPA on this router-laptop
combination.

---
Clarence A Dold - Hidden Valley (Lake County) CA USA 38.8,-122.5

Client card is Linksys WMP54G.
Using WGR614v1. Running the 1126 firmware (latest non-beta release).

I do have the beta 1400 firmware ready to install if I want to try it.
It only adds WPA support to the router according to the release notes
so I think I'll only go that route as a last ditch effort.

Windows got a bit wonky on me at first. Initially what I did was
configured the WAP on the router with some SSID and had the router
auto-generate a key based on the passphrase that I entered. Then I went
to the client computer and created a profile for that SSID using the
same authentication (Shared key) and typed in the passphrase I wanted.
This did *not* work. It would try to connect for 2-3mins then just stop
trying to connect without any error message.

So I wound up using the Windows wizard (eep) and had it generate a key
for me. I set that up on the router and the computer supposedly
connects now, but just with no data transfer.

There was another thread out there talking about the same problem
(minus his TCP/IP problem). But it didn't have any replies and was too
old for me to reply to:

http://groups.google.ca/groups?hl=en...6btnG%3DSearch

(E-Mail Removed) wrote:
> Client card is Linksys WMP54G.
> Using WGR614v1. Running the 1126 firmware (latest non-beta release).

> I do have the beta 1400 firmware ready to install if I want to try it.
> It only adds WPA support to the router according to the release notes
> so I think I'll only go that route as a last ditch effort.

1400 "Fixed Pass phrase length of more than 64 characters was
accepted without error issue. "

Does that mean it only did 64 bit WEP before? Have you tried 64?
1400 was published April 26, 2004. If it were buggy, I think it would have
disappeared. You could try email to (E-Mail Removed) to ask.

> So I wound up using the Windows wizard (eep) and had it generate a key
> for me. I set that up on the router and the computer supposedly
> connects now, but just with no data transfer.

> There was another thread out there talking about the same problem
> (minus his TCP/IP problem). But it didn't have any replies and was too
> old for me to reply to:

I hate that about Google... ;-)
1: good search, solves the problem.
2: hundreds of replies, all saying something different fixes the problem.
3: hundreds of people with the same problem and no solutions.


--
---
Clarence A Dold - Hidden Valley (Lake County) CA USA 38.8,-122.5

Nope. It does both 64 bit and 128 bit. But before it would not allow
more than 64 characters in the passphrase used to generate the key. I
haven't tried 64 yet though. But I'll try that out after I disable WEP
and give that a go. The thing was released as beta and I believe all
development has just stopped on it, given the 5 different versions of
the router available today. I'm pretty sure it's safe, but there's no
real point in upgrading if there isn't anything I absolutely need. WPA
I don't need and a passphrase greater than 64 characters is unnecessary
as well.

Google's saved me so many times. Takes a bit to search but I can't
imagine it trying to do it on yahoo or MSN. I'd shoot myself. But yeah
there are often times a lot of empty threads. This actually happens to
be only the second time I've only been able to find a single thread
relating to the problem with 0 replies.

<(E-Mail Removed)> wrote in message
news:cughmi$58m$(E-Mail Removed)...
> (E-Mail Removed) wrote:
> > Client card is Linksys WMP54G.
> > Using WGR614v1. Running the 1126 firmware (latest non-beta
release).
>
> > I do have the beta 1400 firmware ready to install if I want to try
it.
> > It only adds WPA support to the router according to the release
notes
> > so I think I'll only go that route as a last ditch effort.
>
> 1400 "Fixed Pass phrase length of more than 64 characters was
> accepted without error issue. "
>
> Does that mean it only did 64 bit WEP before? Have you tried 64?
> 1400 was published April 26, 2004. If it were buggy, I think it
would have
> disappeared. You could try email to (E-Mail Removed) to ask.
>
> > So I wound up using the Windows wizard (eep) and had it generate a
key
> > for me. I set that up on the router and the computer supposedly
> > connects now, but just with no data transfer.
>
> > There was another thread out there talking about the same problem
> > (minus his TCP/IP problem). But it didn't have any replies and was
too
> > old for me to reply to:
>
> I hate that about Google... ;-)
> 1: good search, solves the problem.
> 2: hundreds of replies, all saying something different fixes the
problem.
> 3: hundreds of people with the same problem and no solutions.

Have you tried it with no encrytion? Or try it with WEP with open
authentication.
Open is preferred over shared as shared exposes the
authentication/encrytion key.