Member Avatar for qusac

When I log into my pc, the network needs to be disabled and then enabled again before it can be used. There are no error messages and it appears to be working in the network properties page. It even clams to be receiving packets (but only 2).
I am running an up to date copy of win2000, my network card is a Linksys Wireless - G PCI adapter (WMP54G) and the router is a Netgear Wireless ASDL firewall router (DG834G). I am also running McAffee Guardian.
I know this seems like an inconvenience but as I don’t know what is coursing it, it is a worry as well.
Thanks in advanced for you help.

Qusac

  • 2 Contributors
  • 5 Replies
  • 106 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by DMR

Dani AI

Generated

followed 's test and confirmed the connection works when the firewall is disabled, so the firewall is almost certainly interfering at startup. The likely culprits are: the firewall loading before the network stack or NIC driver completes initialization; the firewall filter blocking initial DHCP/ARP/handshake packets; or a driver/compatibility issue between the network stack and the firewall’s kernel filter.

Check and narrow the cause before making permanent changes:

  • Look in Windows Event Viewer (System and Application) and in the firewall logs for blocked DHCP, ARP or TCP attempts during the failed startup.
  • While the connection is broken, run ipconfig /all and attempt ipconfig /renew to see if DHCP succeeds.
  • Capture startup traffic with a packet sniffer (for example Wireshark) and look for DHCP Discover/Offer or blocked SYNs — this shows whether the firewall is dropping the boot-time traffic.
  • Test with a direct wired connection (if possible) to rule out a wireless driver/init timing problem.

A practical workaround that avoids leaving the machine unprotected is to delay the firewall service start until after the NIC is up. Set the firewall service to Manual and create a small startup script that waits a few seconds then starts the service. Example batch (replace the service display name):

@echo off
ping -n 10 127.0.0.1 >nul
net start "Firewall Service Display Name"
exit

Place that in a Scheduled Task or Startup folder so it runs at logon. Longer-term fixes: update NIC drivers and the firewall software to current builds, review the firewall’s allowed-application and trusted-interface settings, selectively disable intrusive components (IDS/filters) while testing, and if necessary perform a clean uninstall/reinstall. Keep the machine protected while testing — don’t leave the firewall disabled permanently.

Recommended Answers

All 5 Replies

Member Avatar for DMR

First of all, disable McAfee entirely and see if that changes anything. Let us know what happens and we'll take it from there.

Member Avatar for qusac

First of all, disable McAfee entirely and see if that changes anything. Let us know what happens and we'll take it from there.

Ok did that and it worked with McAffee off.
When I start the firewall it stops the connection so it seems resanable that there is a setting wrong??
I do not like the idea of having to remember to start the firewall each time so if anyone has any ideas of what setting may be wrong I'd be gratefull.

N. Costa

Member Avatar for DMR

Which exact McAfee package (including version) are you using? The configuration options can vary between the different products/versions.

Member Avatar for qusac

Which exact McAfee package (including version) are you using? The configuration options can vary between the different products/versions.

Sorry :o its taken so long the ISP had some problems as well so have not been online :mad: .
The firewall is McAfee Guardian v3.01.1000.0 (v number from the about section)
It was installed as part of McAfee VirusScan Professional Edition v7
Thanx for the help in advanced.
Just ask if you need any more info.

Nick

Member Avatar for DMR

Well... there seem to be a lot of unhappy people out there who've had similar problems with that version. Unfortunately, some of them were never even able to get a solution; they had to uninstall it.

Here are a couple of things to look at; you might at least be able to narrow things down by checking these out:

1. Look through the list of applications that McAfee has configured for Internet/network access. Make sure it hasn't mistakenly decided to block access for any applications or services that it shouldn't have. If it has done that, you'll need to manually reset the access permissions for those programs.

2. Try temporarilly disabling individual components of the firewall package such as IDS (incoming intrusion detection), privacy filters, etc.

3. If you can, eliminate the possibility of a specific conflict with your wireless card/configuration by plugging the computer directly into the router with an Ethernet cable.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.