Atheros AR5008 miniPCIe, and D-Link DAP -1353/e

[CrunchDude]

Hi all...The above mentioned combination is what I currently have. Sigh. This wrieless-N WiFi has been something else. The D-Link DAP-1353 it turns out is a German model, and since I am currently in Germany, I guess that makes sense.

The Access point promises the 300Mbps speed ALL OVER THE BOX, documentation, and full manual, even though it is only a SINGLE-band (2.4GHz range) AP. It is connected to a DSL-Modem/router combo made by AVM, which is called FritzBox 7170.

I may very well be able to get it to work but I CANNOT GET into the darn web config utility!!!!

192.168.0.50 is what it says everywhere, but I even tried other ones based on the router config, and nothing, NOTHING, works.

Does anyone know if the AP can be upgraded to Draft 2.0 firmware, as 300Mbps on a SINGLE-band sounds like Draft 1.0, which I've actually SEEN it advertised as. The other way to try this would be to downgrade my Atheros mini-PCIe card to Draft 1.0. I just want to see 300Mbps. And I'll go from there. What driver for the Atheros card do you guys recommend??

I'm so frustrated with this. I really need this for its RANGE, as well as for the capability of stronger streaming! I'd be someone who would totally benefit from BOTH of N's main new technologies.

What do you guys recommend I do/try? I hope this is in the right forum...

Thanks everyone!!

Crunch

[kris23]

nearly all D-link routers use 192.168.0.1 as their address, try that

[Tipstaff]

Try 192.168.178.1. I remember my friends Fritz!Box using that address, so it might be the same.

Interesting little router, btw. Just wish they sold it here.

[CrunchDude]

Well, my problem is not with the router. And yea, it is the Linksys of Europe it seems. I need to get into the D-Link Access Point DAP-1353. It's supposed to be 192.168.0.50...I tried all of the ones you guys had me try. Thank you! Unfortunately, no dice on any of the above!

So if I JUST have my DAP 1353, and my laptop connected via Ethernet, wouldn't I be able to do the 192.168.0.50?? I tried that upon initial setup. Why doesn't THAT at least work??? Is it Vista? Is it 64-bit?? I'm grasping at straws here. Should I install XP just for that. I will. It would be totally worth it to me.

D-Link's Click'n'Connect works great, so at least I was able to encrypt it, changed the SSID, etc., but the TOOL got into the router, why can't I? LOL...Is there any way to extract the way that IT gets access to the AP??

This is crazy. WHat else can I do? Does what I suggested make any sense?? Oh man...I'm ready to take it back! This so blows, and it was expensive, too.

Thank you all very very much!

[dj_stick]

the OS you're using shouldn't affect how you access the router (you'd probably be able to use win 3.1 and still get in)

have you read the manual that came with the AP? that should tell you early on the exact IP address you need to type in

[CrunchDude]

Originally Posted by dj_stick

the OS you're using shouldn't affect how you access the router (you'd probably be able to use win 3.1 and still get in)

have you read the manual that came with the AP? that should tell you early on the exact IP address you need to type in

Yes, of course. I'm so way past that. This is going back if I can't get into the web config utility.

I agree, of course, on the OS part. I only mentioned it, as that's the extent to which I'm grasping at straws lol...PLEASE HELP ME!! The documentation, etc., says 192.168.0.50. I've tried SO much besides that. NOTHING WORKS...I can EASILY get into the router, though. What's the matter with this thing??

[Tipstaff]

It suddenly dawned on me, but I think the problem is that you are running 2 different levels of IPs. In this case your network is running most likely off of 192.168.178.xxx, yet your Access Point is running 192.168.0.xxx. Sometimes this should not effect things, but other times I've seen networks completely bork, and not work at all. So, here's a couple things to try (it's also best to do these things hooked up to your router by wire, not wireless as you could run into a lot of issues):

1) Set a static IP address for your computer that is within range of your your APs IP. For instance, try setting a static address of 192.168.0.100, with a subnet of 255.255.255.0. Don't worry about putting in a Gateway or Primary/Secondary DNS address as it's not necessary at this point. Then, try connecting to your AP.

2) Since you can get into your router you may want to consider changing it's default 192.168.178.1 address to be in line with your APs addresses, in this case you could do 192.168.0.1. This would also change the IP range it dishes out for DHCP to be within your APs range as well, in which case any computer running on DHCP would be "technically" on the same network now as your AP.

[CrunchDude]

I knew it was a simple thing I overlooked. I knew it was an obvious thing I overlooked. Turns out it was.

I'm slinging like crazy with the latest firmware on the D-Link AP, and the latest 64-bit driver for Atheros...all the way from the WEST COAST!!!!!!

Vista finally recognizes my Access Point as a wireless-N AP, too! And no more 130Mbps. It displays the straight 300Mbps now!

Of course, it's not reeeaally running at 300, I know. Which utility can I use to measure the ACTUAL speeds I'm getting? Speed tests reveal around 15,000kbps, and the range on G was poor and dropped a lot, whereas this baby is usually "Good" (three bars) and occasionally "Very good" (four bars), so the range is significantly improved, as promised! Mind you, I am TWO floors up from where it's located, and exactly on the opposite end of the house! Impressive. Very impressive!

Thanks everyone for helping me! Hopefully this will help someone else as well. I will make myself available for any and all questions now that I've learned a LOT about WiFi, and it was all a rousing success in the end!

Will Draft 3.0(.2) be released anytime soon for us N'ers??

P.S. ONE thing STILL doesn't work! Torrents. It does on my Netgear AP, but it's G, not N. What do I have to tweak for that??

[Tipstaff]

What was it exactly that did it? Was it just a matter of having to upgrade the firmware?