ipconfig /renew fails on w2kpro

Having 2 dhcp servers will cause issues.  Shut DHCP off on the DSL.
On the client do a ipconfig /flushdns
Power off DSL modem power back on
Power off router power back on.
Run ipconfig /renew

Since you have set a static IP in the same range, could you ping the router? - I suspect not, indicating a faulty router. but a full reset to factory defaults should help..
http://hri.sourceforge.net/di_604/reflash.html

yes that right ryansoto, but the DI-604 is both....

DOH, my bad.. your good... sry

ryansoto:
2 dhcp servers has never been a problem, DI-604 works just fine as client and server - it has for several years. Tried. On one network card I got no IP address
On the otherone - the motherboard one, the one that I have always used, I got the usual IP address from the router... sorry, that card is the one with static IP right now, but I get it...
Ipconfig /renew still does not work
dbuggerau:
No, I cannot ping the router. I can just ping that compuer.

Extra info: the only identifiable action that I can realate to is that I was upgrading my ZoneAlarm free... Of course, I uninstalled - and reinstalled it, and uninstalled it already.... -
Also, I have other computers working just fine thru the DI-604 and my Visionnet Moden, that is what I am using to communicate right now. I have 2 other computers right now connected thru the DI-604 and both with mutual access and internet NP.

Thank again!

as far as the to update the firmware, I just cannot find it anymore... they took it out of dlink....

well, I wouldnt worry updating the firmware if you have working PC's connected now, that little gem changes everything.
Now, I would be looking at the patch cable, or network card/software...
Try another cable off a working PC and verify it still doesn't work..
If so, then start looking at your clients hardware/software...

Sometimes it helps removing the TCP/IP protocol and reinstall it (it installs from files present in the windows installation, no extra disks needed).

I assume you mean that the router is DHCP client on the WAN side and DHCP server on the LAN side; that's common practice. Having 2 DHCP servers on the same network is not good.

Try booting the problem unit with a Knoppix live CD or something like that. If you get networking to run OK, your hardware is good; if it doesn't work hardware is suspect.
/RID

rid

that is right, router is dhcp client on the wan side and dhcp server on the lan side. why is it not good? what other options would you suggest, change of hardware?

downloading a knoppix live cd and uninstalling TCP/IP as I write...

Thanks.

I didn't say it's not good, I merely described the situation as I thought there were tendencies towards a misunderstanding earlier. The WAN and LAN sides of a router are not on the same network; your situation is quite OK. If, however, two DHCP servers should exist on the same network, like if you had a router AND a computer that both were running a DHCP service in the same network (the same subnet: e.g. two devices inside the 192.168.0... address segment), you may run into problems.
/RID

TCP/IP  reinstall did not work.... and the CD knoppix will bring my computer to a black screen :(
Any other suggestions?

Very unfortunate; knoppix usually works with most systems.

You could try removing the Network card (NIC) physically and in the device manager, then reinstalling the NIC and its drivers
/RID

Actually, I had just installed an older NIC I had around to test, getting the same results... The other ethernet is built into the motherboard. Is there any possibility that the older NIC is giving any trouble?

It's possible that the old NIC has a defect or something, not very common in my experience, though; I'd be prepared to guess at driver error or a more general windows issue. It's a pity the knoppix thing didn't work. An Ubuntu or KUbuntu CD will do the same service, so if you're prepare to do another download you could try either. It may serve to eliminate or pinpoint the hardware here. (www.ubuntu.com)

If you can remove both on-board and add-on NIC in device manager, have windows re-detect the one you want to use (make sure on-board is disabled if you try to use the add-on), then you should be able to load the drivers again, properly and see if that helps. Possibly windows has just gotten confused and tries to use the NIC that isn't actually connected...

Depending on the make of your add-on NIC, you may have some tools included on the driver disk (like old 3Com cards) that may help testing the NIC.
/RID

You didnt mention the results from trying another cable off a working PC and verify it still doesn't work???

Hi,
debuggerau, thanks for reminding me, I tried different cables to no avail. Actually, funilly enough, at a certain point ipconfig/renew started to work, but I still could not ping the gateway...

In any case, at this point I will reinstall W2K - once I have passed all important info to another computer - and see wether it was a hardware problem or not.

I am delaying the reinstallation of W2K, since it is no longer needed. I do hope to add more info about the final outcome here in the next couple of weeks.

I finally installed XP in another drive, and everything is working... I could not know what is the solution and do not know quite well how should I address the point award. All I know is it definitely was a software problem...

How should I close this question?