Recommended Posts

An if the problem is related to dhcp -- going to static would be a pretty F'ing easy solution now wouldn't it ;)

Yeah its real difficult to install dhcp -- just add the role.. It does not have clue one to what you think your using it as.. An I don't even want to get started on 2k3 as a workstation.. You have a SERVER OS, with all kinds of functionality -- an your using to what play games an watch porn :rolleyes: Let me guess it's the ENT version.. An you forked over $4k for it :rofl:

Turn off the dhcp server on your router - turn it on 2k3 machine.. Point to your router as the gateway in the dhcp settings..

For that matter -- you have a FULL dns server that could actually do some real caching, etc.. an your pointing to your router with what 8mb of ram as a caching name server..

Great to see your putting all the features of that server os to good use :rofl:

Why do you even have a server O/S if your just using as a workstation, that is quite a waste of money.

I have a legit copy of 2k3. It happens to run better than XP on my notebook. Vista runs just as well but insn't quite compatible with all I do. I should look into installing what i can on Vista so I can dump the XP, I happen to triple boot. Oh, and my Vista Ultimate edition is also legit. I appreciate your expertise and experience, I'm just not interested in running a server. So any other suggestions on fixing the problem? You seem to think it's caused by the cache on the rounter for the dhcp.

Where did I say it was caused by the cache on router for dhcp??

Its clear you have a issue with getting a dhcp lease -- you should not have to ever /release /renew more than just once to release an then get an IP..

When the box turns on it should get its IP, etc. If not then yes its seems clear you have some issue with dhcp.. What I am not sure..

The EASY fix to a dhcp issue or renew problem is to just set a static! Or if there is some issue with your nic an this router talking dhcp for some reason - a static would remove the problem. Bringing up a different dhcp server -- would be a method to test to see if your dhcp issue is related to routers dhcp server.

The dhcp servers that come with routers are never very full function. You have an OS that has the ability to provide a very full function dhcp server -- with logging and diagnostics, etc.. etc.. I could care less if your copy is legit or not - no really I could give a rats ass if your the warez king of all england.. Or if you richer than bill gates an dropping $1k for a OS to use as a desktop is no big deal.

You have the ability to run another dhcp server right there at your finger tips is all I was trying to say!!

I would be happy to help troubleshoot your dhcp issue - if that is what it is! But you have not given us anything to work with. We do not know what version of the firmware your running on your router. We do not know what NIC is being used, we do not know what driver your using for said nic, etc.. etc.

We do not know if your connection is dying at lease expire or not..

How can we troubleshoot what seems to be an issue with getting an IP address from your current dhcp server, or renewing it when it expires if we have no idea what hardware we are working with, or what drivers they are using - so we can search to see if there have been any reports issues with any of it.

We could also get to the level where we run a sniffer an verify/watch what could be wrong with the dhcp process.

post-14624-1185393511.png

But without some basic info of what exactly we are working with -- its pretty hard to know where to go next.

So either set a static an see if your connectivity issues go away, or run a different dhcp server.. What runs it I could care less - if you do not want to use the one that came with the OS you legally have the right to use :rolleyes: then use another.. Here is a FREE option you can run on any windows based OS to provide dhcp on your network - other than your current router.

http://tftpd32.jounin.net/

Where did I say it was caused by the cache on router for dhcp??

We could also get to the level where we run a sniffer an verify/watch what could be wrong with the dhcp process.

post-14624-1185393511.png

But without some basic info of what exactly we are working with -- its pretty hard to know where to go next.

So either set a static an see if your connectivity issues go away, or run a different dhcp server.. What runs it I could care less - if you do not want to use the one that came with the OS you legally have the right to use :rolleyes: then use another.. Here is a FREE option you can run on any windows based OS to provide dhcp on your network - other than your current router.

http://tftpd32.jounin.net/

Look, I merely pointed out after having people suggest I'm not running legal stuff. I beta tested for MS, and have an uncle who runs a small softwear outlet. You seem pretty upset, not sure why other than your being frustrated with my lack of follow thru on providing info. I'll boot up that notebook and post the details you ask for. Maybe running a static IP from the router is the best option. I'd rather not mess with the dhcp is all I was saying, I want to keep it as simple as possible. thanks for the link, is it hard to setup?

Dude I'm not upset - really I'm not, but yes the lack of follow thru with information -- an you still having an issue is frustrating.

? you state "I happen to triple boot" Are we talking only 1 piece of hardware that is having the issue??

You have a router -- an how many different machines?? Or it one machine booting multiple OS's?

If you have other machines on the network - do they have issues??

The triple boot could be a factor - since a dhcp lease is given on mac, if your on the same hardware - the mac would be the same..

It normally should not be an issue - but it could be a factor in your dhcp process having an issue. What version of the firmware are running on the router? And are your issues all having to deal with 1 piece of hardware??

edit: as to hard to setup, no tftpd32 could be setup by any retarded monkey on crack in about 30 seconds!!

edit2: Maybe running a static IP from the router is the best option Um NO!! that is not what I am talking about -- what I am talking about is setting the machines IP static ON THE MACHINE!! not setting a reservation on the dhcp server.

http://www.microsoft.com/resources/documen...g.mspx?mfr=true

To configure TCP/IP for static addressing

Edited by BudMan
Dude I'm not upset - really I'm not, but yes the lack of follow thru with information -- an you still having an issue is frustrating.

http://www.microsoft.com/resources/documen...g.mspx?mfr=true

To configure TCP/IP for static addressing

Budman, that last link seems to have been the trick. I set the manual settings and it appears to be doing the job. Thank you.

An yet STILL no follow thru on any of the freaking questions!!! :argh:

Are we talking only 1 machine that triple boots - or multiple machines?

Using a static address was suggested back on post #9 of this thread ;) An then again in 22, 24 an 27.. Nothing like repeating yourself over an over again ;)

An yet STILL no follow thru on any of the freaking questions!!! :argh:

Are we talking only 1 machine that triple boots - or multiple machines?

Using a static address was suggested back on post #9 of this thread ;) An then again in 22, 24 an 27.. Nothing like repeating yourself over an over again ;)

I really appreciate your help. I didn't catch on to the static part, wanted to see if there were other options. I triple boot on one machine, Vista UE, XP Home, 2k3. I have some partition space after that. But with only a 80gig drive it's limited. I want to go to just a dual boot situation. Basically just Vista, 2k3.

My NIC on that notebook is Broadcom 802.11b/g WLAN, dv 4.10.40.1

An that driver is the same for both XP, Vista an 2k3?

the only problem with static on a laptop - is now it can be a pain putting it on another network, ie work,school, starbucks, etc.

Nothing you can not work with - simple batch file using netsh can change it from dhcp to all kinds of different static settings with click. But still a pain ;)

I will be willing to help you work thru the dhcp issues.. but we would need to get some details of EXACTLY what is happening.. Not just you get a 169 address ;) Let me know if you want to work out the root issue, an not just a work around by running static.

No the dv for vista is newer 4.82.28.56.

As long as I can access with Vista, then I shouldn't need 2k3 but for only my home wireless. I can set XP with static as well if need be. But seems I should be using a newer driver version for 2k3 and XP to match Vista.

that might clear it up..

BTW - for future reference.. when someone asks you for details. the broadcom 802.11b/g nic in your laptop is pretty much useless ;)

Maybe I missed it - did you even give a brand name for your laptop?

Details, Details!! What is the model number of your laptop? - an we could most likely look it up ourselves.. broadcom wireless is pretty freaking broad ;) I would assume 43xx chipset?

If I take a guess an use HP.. just picking any model say the dv9220us, the driver they list for download dated Jan 2007

Provides the Broadcom 4.102.15.61 Wireless LAN driver.

So your quite a bit dated on your drivers. Shoot I'm running a dated driver on an dell d610 with the dell 1370 WLAN an its driver is 4.100.15.5

So I would assume your drivers is quite dated - and updating it "might" remove your dhcp issue.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.