RE: Client IP/DHCP

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hmmm...do you have an antivirus program running on your network? if yes, run
it against this pc or locally. Also, an antispyware program? Adaware or
Spybot, run them both. Download them from the Internet install, update and
scan; they are free.

Let me know...


--
MCSE/MCSA A+ Network+


"Matt Stephenson" wrote:

> Have followed the steps to the letter, however, this didn't make any
> difference whatsoever.
>
> Not sure where I go now?
>
> "pQi" wrote:
>
> > the NIC is not set up for DHCP, or there is a problem communicating wit the
> > DHCP server. You have a Winsock problem. I am going to past a link from
> > Microsoft below. Please follow the steps precisely as this should correct the
> > problem
> >
> > http://support.microsoft.com/kb/811259
> >
> > Hope this information helps you. Good Luck!
> > Let me know if this still does not resolve your problem.
> >
> > --
> > MCSE/MCSA A+ Network+
> >
> >
> > "Matt Stephenson" wrote:
> >
> > > Looked in the regedit on one of the affected client machines and it does have
> > > some folders in there labelled with random numbers and letters. They have IP
> > > files inside them but they all show as IP 0.0.0.0 Then there is one folder
> > > the same but lists the manual IP I have assigned it to temporarily work.
> > >
> > > "pQi" wrote:
> > >
> > > > Can you please provide me with the exact message that appears when you do an
> > > > IPCONFIG/RENEW.
> > > >
> > > > For the path I have specified below: go into a run command START/RUN and
> > > > then type regedit once in the registry follow the path I gave you on the
> > > > previous post. HK_LOCAL_MACHINE then continue on to the next keys I have
> > > > provided for you...if you still don't understand let me know....its okay.
> > > > Lets just focus on trying to get this resolved.
> > > > --
> > > > MCSE/MCSA A+ Network+
> > > >
> > > >
> > > > "Matt Stephenson" wrote:
> > > >
> > > > > Thanks for your continued help.
> > > > >
> > > > > As I said previously, I am quite a newbie so am not too sure about your
> > > > > instructions:
> > > > >
> > > > > 1. What do you mean by 'remove it from the entry'?
> > > > > 2. Where do I enter
> > > > > 'HKLM/CurrentControlSet/Services/Tcpip/Parameters/Interfaces'? Do I just
> > > > > search for this in the registry?
> > > > >
> > > > > I did try ipconfig/renew on the client but it just return a message saying
> > > > > something along the lines of it couldn't whilst it was attached/connected to
> > > > > mediadisks?
> > > > >
> > > > > "pQi" wrote:
> > > > >
> > > > > > Try this:
> > > > > >
> > > > > > Check the troubled machine with the static IP that you have entered, go
> > > > > > ahead and remove it form the entry. Reboot the computer/enter the registry by
> > > > > > selecting the following:
> > > > > > HKLM/CurrentControlSet/Services/Tcpip/Parameters/Interfaces...check to see if
> > > > > > there is an entry for an IP address, if there is--remove it. Then try and do
> > > > > > a ipconfig/release--renew. What may be happening is that when you setup the
> > > > > > pc to receive an IP from DHCP, it conflicts with the possible cached IP in
> > > > > > the registry in which prevents you from receiving one, unless we remove it
> > > > > > from the registry then it may permit DHCP to forward the request to the
> > > > > > client. Lets hope this works...
> > > > > > --
> > > > > > MCSE/MCSA A+ Network+
> > > > > >
> > > > > >
> > > > > > "Matt Stephenson" wrote:
> > > > > >
> > > > > > > Tried those solutions and still no luck.
> > > > > > >
> > > > > > > The problem has now spread with two more clients not working unless they are
> > > > > > > assigned manual IPs.
> > > > > > >
> > > > > > > I have rebooted the server and restarted the DHCP and DNS services. Still no
> > > > > > > change.
> > > > > > >
> > > > > > > Weird thing is that I have three clients operating without a problem and
> > > > > > > automatic IPs assigned. It was all working fine for six months and no
> > > > > > > problems until yesterday. I haven't even touched any settings on the server
> > > > > > > for the past week?
> > > > > > >
> > > > > > > "pQi" wrote:
> > > > > > >
> > > > > > > > Please read the "Planning the DHCP Server Configuration" as this may give you
> > > > > > > > some guidance as to what may be the problem with your situation. Scroll down
> > > > > > > > till you see this topic.
> > > > > > > >
> > > > > > > > http://www.windowsitlibrary.com/Content/155/08/4.html
> > > > > > > >
> > > > > > > > "pQi" wrote:
> > > > > > > >
> > > > > > > > > to disable local firewall on local machines you would need to edit the GPO in
> > > > > > > > > this following manner:
> > > > > > > > >
> > > > > > > > > Launch GPO, then go to...Administrative Templates/Network/Network
> > > > > > > > > Connections/Windows Firewall.
> > > > > > > > >
> > > > > > > > > From this point you should be able to modify the settings in which this will
> > > > > > > > > also effect everyone, so please be aware of this action.
> > > > > > > > >
> > > > > > > > > Have you tried using the IP instead of host name in DNS client settings?
> > > > > > > > >
> > > > > > > > > "Matt Stephenson" wrote:
> > > > > > > > >
> > > > > > > > > > The DHCP has more than enough range to cover the amount of machines I have
> > > > > > > > > > and also all the lease times have a least 3 days to run.
> > > > > > > > > >
> > > > > > > > > > All machines are Win XP Pro. How do you disable the local firewall, as when
> > > > > > > > > > I go into in on the client machine it won't let me change anything as it says
> > > > > > > > > > it is controlled by a group policy?
> > > > > > > > > >
> > > > > > > > > > Thanks for your help so far, much appreciated
> > > > > > > > > >
> > > > > > > > > > "pQi" wrote:
> > > > > > > > > >
> > > > > > > > > > > Have you checked your DHCP settings, for ex. scope range? lease time? Is this
> > > > > > > > > > > a Windows XP machine? Do you have the local SP2 firewall on the client
> > > > > > > > > > > machine enabled? if yes, disable it.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > "Matt Stephenson" wrote:
> > > > > > > > > > >
> > > > > > > > > > > > 1. Yes, several other clients are.
> > > > > > > > > > > > 2. Yes I can ping and the NIC is connected
> > > > > > > > > > > >
> > > > > > > > > > > > As it happens one other machine has just gone the same way in the last hour
> > > > > > > > > > > > in not getting an IP assigned to it. Had to manually assign one to get it
> > > > > > > > > > > > back up and running on the network. Don't want to have to do this wth every
> > > > > > > > > > > > client.
> > > > > > > > > > > >
> > > > > > > > > > > > "pQi" wrote:
> > > > > > > > > > > >
> > > > > > > > > > > > > Hello,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Questions:
> > > > > > > > > > > > > 1. Are your other clients receiving an IP from your DHCP Server?
> > > > > > > > > > > > > 2. Can you ping the server from the client pc? if not check * note below
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > *It appears that your media (NIC) is disconnected on the client pc. Check
> > > > > > > > > > > > > the enternet adapter to make sure you have a link on the card.
> > > > > > > > > > > > >
> > > > > > > > > > > > > "Matt Stephenson" wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Question from a newbie so please be understanding.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I have been running SBS 2003 Premium (with 2 NICs) succuessfully for nearly
> > > > > > > > > > > > > > the past 6 months. I have recently installed SP1 along with ISA 2004. There
> > > > > > > > > > > > > > were a few minor problems with FTP which I resolved.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > All the client machines except one are working properly. I can't figure out
> > > > > > > > > > > > > > what is wrong with this one client machine and hope someone can help?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Bacially if I assign it a manual IP address and some other settings it
> > > > > > > > > > > > > > connects to network. It won't automatically assign an IP and when connected
> > > > > > > > > > > > > > manually the internet and intranet seem very slow.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Here is the IP config for the Server:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Windows IP Configuration
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Host Name . . . . . . . . . . . . : server
> > > > > > > > > > > > > > Primary Dns Suffix . . . . . . . : taylorsyms.local
> > > > > > > > > > > > > > Node Type . . . . . . . . . . . . : Unknown
> > > > > > > > > > > > > > IP Routing Enabled. . . . . . . . : Yes
> > > > > > > > > > > > > > WINS Proxy Enabled. . . . . . . . : Yes
> > > > > > > > > > > > > > DNS Suffix Search List. . . . . . : taylorsyms.local
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ethernet adapter Server Local Area Connection:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Connection-specific DNS Suffix . :
> > > > > > > > > > > > > > Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
> > > > > > > > > > > > > > Physical Address. . . . . . . . . : 00-0F-1F-F9-F9-7A
> > > > > > > > > > > > > > DHCP Enabled. . . . . . . . . . . : No
> > > > > > > > > > > > > > IP Address. . . . . . . . . . . . : 192.168.16.2
> > > > > > > > > > > > > > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > > > > > > > > > > > > Default Gateway . . . . . . . . . :
> > > > > > > > > > > > > > DNS Servers . . . . . . . . . . . : 192.168.16.2
> > > > > > > > > > > > > > Primary WINS Server . . . . . . . : 192.168.16.2
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ethernet adapter Network Connection 2:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Connection-specific DNS Suffix . :
> > > > > > > > > > > > > > Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Dual Port Server
> > > > > > > > > > > > > > Adapter #3
> > > > > > > > > > > > > > Physical Address. . . . . . . . . : 00-04-23-AF-2C-2F
> > > > > > > > > > > > > > DHCP Enabled. . . . . . . . . . . : No
> > > > > > > > > > > > > > IP Address. . . . . . . . . . . . : 83.100.184.58
> > > > > > > > > > > > > > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > > > > > > > > > > > > Default Gateway . . . . . . . . . : 83.100.184.57
> > > > > > > > > > > > > > DNS Servers . . . . . . . . . . . : 192.168.16.2
> > > > > > > > > > > > > > NetBIOS over Tcpip. . . . . . . . : Disabled
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Here is the problem client IP:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Windows IP Configuration
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Host Name . . . . . . . . . . . . : STUDIO
> > > > > > > > > > > > > > Primary Dns Suffix . . . . . . . : taylorsyms.local
> > > > > > > > > > > > > > Node Type . . . . . . . . . . . . : Hybrid
> > > > > > > > > > > > > > IP Routing Enabled. . . . . . . . : No
> > > > > > > > > > > > > > WINS Proxy Enabled. . . . . . . . : No
> > > > > > > > > > > > > > DNS Suffix Search List. . . . . . : taylorsyms.local
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ethernet adapter Local Area Connection:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Media State . . . . . . . . . . . : Media disconnected
> > > > > > > > > > > > > > Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
> > > > > > > > > > > > > > Connecti
> > > > > > > > > > > > > > on
> > > > > > > > > > > > > > Physical Address. . . . . . . . . : 00-12-3F-02-47-BD
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Ethernet adapter Wireless Network Connection:
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Connection-specific DNS Suffix . :
> > > > > > > > > > > > > > Description . . . . . . . . . . . : Dell Wireless 1350 WLAN Mini-PCI
> > > > > > > > > > > > > > Card
> > > > > > > > > > > > > > Physical Address. . . . . . . . . : 00-0B-7D-18-1C-84
> > > > > > > > > > > > > > Dhcp Enabled. . . . . . . . . . . : No
> > > > > > > > > > > > > > IP Address. . . . . . . . . . . . : 192.168.16.19
> > > > > > > > > > > > > > Subnet Mask . . . . . . . . . . . : 255.255.255.0
> > > > > > > > > > > > > > Default Gateway . . . . . . . . . : 192.168.16.2
> > > > > > > > > > > > > > DNS Servers . . . . . . . . . . . : 192.168.16.2
> > > > > > > > > > > > > > Primary WINS Server . . . . . . . : 192.168.16.2
> > > > > > > > > > > > > >
.

Relevant Pages

  • Re: WAP54Gs with WPA not handing out IPs from SBS2003 server
    ... Do you have enough IP addresses in the DHCP pool on the DHCP server? ... There's not even 50 machines total on the network. ... I'll assume you're running Windoze XP Home using Wireless Zero Config ... With the PCMCIA card, it's the WZC software. ...
    (alt.internet.wireless)
  • Re: WAP54Gs with WPA not handing out IPs from SBS2003 server
    ... Do you have enough IP addresses in the DHCP pool on the DHCP server? ... There's not even 50 machines total on the network. ... I'll assume you're running Windoze XP Home using Wireless Zero Config ... With the PCMCIA card, it's the WZC software. ...
    (alt.internet.wireless)
  • Re: Whats the benefit of using superscopes?
    ... A superscope is a collection of individual scopes that can be ... A superscope is actually a collection of individual scopes. ... Place DHCP clients from multiple network IDs on the same ... The superscope will allow the DHCP Server to answer requests from ...
    (microsoft.public.windows.server.networking)
  • <LONG>Re: Question rephrase
    ... >currently only one master NS server, ... become a master NS for that network. ... a computer is brought back into our facility, the first thing security ... so your DHCP server configures itself? ...
    (comp.os.linux.networking)
  • Re: Networking between Irix and Osx
    ... Is your router a DHCP server? ... My router is a DHCP server and my G5 was already configured to ... keep networking information (ip, dns,etc.) from it. ... In the panel Modify Network Settings on Iris, i also try to write the ...
    (comp.sys.sgi.admin)