| G520A2, 624C1 and Zone Alarm Pro Well as the title says I have a DWL-G520 (h/w:A2, driver 2.48) and a DI-624 (h/w:c1 f/w:2.37) and Zone Alarm Pro 4.5.538.001. I have had an issue since installing my wireless setup and I was wondering if anyone else has had it and can shed any light on it for me? I am running Windows XP Pro SP1. Any other specs needed I can give upon request.
When I start my system everything is fine, but my wireless network will not "connect" on its own. Using the D-Link AirPlus utility it can see the 624 but it is NOT making a connection. I have to use the site survey feature of the utility to actually make the connection so my system can receive information. I initially thought this was due to the 2.42 driver for the G520. When the new 2.48 drivers came out the first few reboots were ok with connection being automatically made. But after those first few things went back to the way it was before.
I am wondering if this is an issue with the G520's driver and/or the D-Link AirPlus utility or something dealing with ZoneAlarm Pro and it not initializing the TCP/IP stack soon enough for the NIC and router to talk to each other.
My intention here is to not have a thread of ZoneAlarm or D-Link bashing start. Please keep this informative. I would love to get to the bottom of this. Thanks.
--
"We defend and we build a way of life, not for America alone...but for all mankind." - Franklin D. Roosevelt |
|
| I had the exact same problem with a 624c1 and a dwl-g650b3 with driver 2.48 and win xph. I replaced the g650b3 for a g650c2 and installed the 3.17 driver and the problem went away. Now every time I start my laptop it auto connects to network.
Now neither of us can compare the 2.48 vs the 3.17 driver as your g520 Rev A won't accept the 3.17 and my g650 Rec C won't take the 2.48 driver but I believe this is a driver issue. If you can get a hold of a g520 rev b you can load the 3.17 drivers and confirm this. I know that some can not auto connect with 3.17 drivers but I think that they are mostly running win 2k.
I know that someone will respond that they auto connect just find with pre-3.17 drivers but I think the latest drivers from Dlink increase the number of system configurations that can auto connect. The only strange thing is that you said you could auto connect at first with 2.48 but then it stopped. But these days nothing surprises me about inconsistencies between Dlink users or among them (not a bash but a true observation on my part).
Lastly, some have said that they have had success with using WZC instead of the Dlink utility, but then you have to disable super g. And that solution may be more of resolving an issue with super g, pre-3.17 drivers and auto connect, then the actual Dlink utility itself. |
|
| According to DLink Level 3 tech support, the connection problem with the g520 B and the current drivers is known and is especially prevelant with W2K and a PIII CPU. I have the same problem with the g520/2.48 driver and it is not related to ZA Pro as it happens if ZA is on or not at start up. Also, for whatever reason I do not have the connection problem with my G650 PCMCIA card with driver 3.17. Also, it is the same with the 624 2.28 (Oct and Nov dates) and the 2.37 versions of the f/w.
steve rose |
|
| Try disabling auto load of the D-link Utility at startup and wait 30-60 sec.Works for me. |
|
| reply to Fubar12345
Thanks for the replies and suggestions. I PM'd Dlink_help about this thread and my issue and he suggested that I try adding 192.168.0.1 to the list of Trusted Zones allowed in ZoneAlarm Pro's Firewall Zones. This is talked about in ZoneLabs here »nh1.nohold.net/noHoldCust25/Prod···rts.html . I had assumed that setting a zone of 192.168.0.0/255.255.255.0 would cover all IP's in my subnet would allow program access. But it appears that it doesn't. After adding the routers IP the AirPlus utility is able to automatically make the connection to my router. I now DO NOT have to use the site survey feature.
Thanks again all especially Dlink_help!!!!
--
"We defend and we build a way of life, not for America alone...but for all mankind." - Franklin D. Roosevelt |
|
| said by Fubar12345:
After adding the routers IP the AirPlus utility is able to automatically make the connection to my router. I now DO NOT have to use the site survey feature.
I'm glad that adding the IP address to ZA worked for you. I had my IP address in ZA and I still could not auto connect to the network. I replaced the g650b3 to a g650c2 and viola without changing anything but the driver I can now auto connect to the network. So it appears that there are multiple reasons for the non-auto connect problem. |
|
