9 replies
by dryflies
by stevencbyers
by dryflies
by stevencbyers
Poster rated this answer.
by _christian_
What you have is your PC assigned an APIPA address becauses it does not find the DHCP server.
Under windows 2000 and XP, you MUST have domain administrator privileges to fix this.
The step-by-step (on 2000, it may or not be the same on XP, depending how XP has been configured(another can of worms)):
Start>Setting>Network and dial-up connections
OR
if you have the network icon on the taskbar, double-click on it (same for W2K and XP)
then:
right-click "local area connections", select "properties"
NOTE: at this point you may want to check "show icon in taskbar", if you did not have it.
select "Internet Protocol (TCP/IP)", then properties
Unless you have a customized network configuration (which should be documented somewhere if it is the case), you should have "obtain an IP address automatically" and "obtain DNS server address automatically". If it is not the case, WRITE DOWN what you have, before anything. DO NOT change it yet.
Now, click on the "Advanced" button.
.../...
I will finish this later, I disable my network while this PC is on the Internet, so I have to leave and come back to finish the step-the step-by-step (I know how and what to do, but never did a step-by-step for it before ;-) )
by stevencbyers
Poster rated this answer.
by willcomp
I have a Linksys wireless router that, at times, just decides it won't serve DHCP.
My simple fix was to assign permanently connected PCs static IP addresses. You will need to configure IP addresses in windows, provide DNS addresses, and specify gateway. It's a rather straightforward process.
Addresses are specific to your ISP and router, so can't provide them without that information.
Dalton
by stevencbyers
Poster rated this answer.
by stevencbyers
This discussion is closed to new replies.
Trending Desktop posts
Sort by Trending