DHCP screwed (after ZA upgrade?)

Digdis

OSNN Addict
Political User
#1
Hi folks,
Got this very weird problem I hope you can help me with:

Got a PC (running WinXP SP2) connected to an Alcatel ADSL router. I Also use the ZoneAlarm Firewall. The other day I upgraded ZA's version (something I do all the time), and suddenly my PC wouldn't receive an IP address from the modem (via DHCP) any more. The network connection icon showed the limited connection sign (telling me there was a problem renewing my IP address). This repeated also after shutting down ZA, and even after uninstalling it!
I can tell this is not the modem's problem, as besides the timing of the problem, I connected a laptop to the modem, and it got the IP address ok and connected to the internet.
The weirdest thing happened when I tried setting up a fixed address to this port: The modem responded to my ping, but I still couldn't see the modem's HTML home page in my browser, and still couldn't connect to the internet as well. Furthermore, the ping command to the modem (done in the command prompt) showed "pinging _o ..." (or some other gibberish) instead of "pinging <ip-address>".

I checked all the details in the Local Area Network properties dialog, and everything seemed in order. Does anyone here have any idea WTF is going on there? What else should I check?

D.
 

Digdis

OSNN Addict
Political User
#5
hansrijf said:
wireless or cabled network?
Sorry forgot to mention: The ADSL router is connected to the Ethernet port in the PC. All the problems I mentioned were on the Ethernet connection ("Local Area Network").
 

hansrijf

sh! it stinks
#6
ZoneAlarm in not in "stop all internet activity" mode?

Oh, just read it happened after uninstalling too. Maybe reinstall and check anyway?
 

kcnychief

█▄█ ▀█▄ █
Political User
#10
Well from all your troubleshooting it limits to a software problem on the PC. I would try to do what is called a "repair" on the connection. This can be performed by clicking Start - > Control Panel - > Network Connections. Once in that area, right-click on your Ethernet Connection, and then select "Repair". This resets a whole bunch of settings related to your connection, and may do the trick.

Also, are you getting an IP at all? Do a ipconfig /all and post a screenie please :)
 

Digdis

OSNN Addict
Political User
#11
kcnychief said:
Well from all your troubleshooting it limits to a software problem on the PC. I would try to do what is called a "repair" on the connection. This can be performed by clicking Start - > Control Panel - > Network Connections. Once in that area, right-click on your Ethernet Connection, and then select "Repair". This resets a whole bunch of settings related to your connection, and may do the trick.

Also, are you getting an IP at all? Do a ipconfig /all and post a screenie please :)
Also tried "repairing". In fact the repairing fails with the message it can't renew the IP address. I'm not in front of my PC right now, so I can't post the ipconfig screenie - will do when I get back home.

In the meantime I also browsed the ZA forum, and it seemed that their newest version (6.1.737) had caused many problems to many other users (some of the problems resemble mine). They advised a clean uninstall (including some dll deleting in safe mode :mad: ). I'll try this and post. In the meantime I can only advise you not to upgrade to the latest ZA version.
D.
 

Digdis

OSNN Addict
Political User
#13
Just posting my ipconfig output:
Windows IP Configuration
Host Name . . . . . . . . . . . . : *****
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com EtherLink XL 10/100 PCI TX NIC
(3C905B-TX)
Physical Address. . . . . . . . . : *******
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.249.90
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Uninstalling ZA the way they recommended didn't work. Getting desparate here.
D.
 

kcnychief

█▄█ ▀█▄ █
Political User
#14
169.x.x.x is an APIPA address, which pretty much indicates that the hardware/software is fine, just can't contact the DHCP server which you already knew :)

Try running WinsockXPFix
 

Digdis

OSNN Addict
Political User
#16
kcnychief said:
169.x.x.x is an APIPA address, which pretty much indicates Try running WinsockXPFix
KCNYCHIEF YOU ARE THE MAN! :rambo:

This indeed was the problem. The funny thing about it was that right before I tried it, my AntiVirus app tried an update and failed with the message it couldn't open the socket...

Cheers to this great community as well.
D.
 

Members online

No members online now.

Latest posts

Latest profile posts

Perris Calderon wrote on Electronic Punk's profile.
Ep, glad to see you come back and tidy up...did want to ask a one day favor, I want to enhance my resume , was hoping you could make me administrator for a day, if so, take me right off since I won't be here to do anything, and don't know the slightest about the board, but it would be nice putting "served administrator osnn", if can do, THANKS

Been running around Quora lately, luv it there https://tinyurl.com/ycpxl
Electronic Punk wrote on Perris Calderon's profile.
All good still mate?
Hello, is there anybody in there? Just nod if you can hear me ...
Xie
What a long strange trip it's been. =)

Forum statistics

Threads
61,971
Messages
673,299
Members
89,016
Latest member
Poseeut