RE: Client IP/DHCP

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: "Do not have access to logon to this session"
    ... different machines and ended up with the same results. ... EventLog on these clients? ... Windows XP, Windows 2000, and Windows NT ... home to Remote Desktop on their Windows XP Pro SP2 machines here ...
    (microsoft.public.windows.terminal_services)
  • Re: ? super-auto for drive-thru espresso business ?
    ... United States because the clients actually listen to the training ... The only machines with a reliable track record in the sub 8k ... Super fit a very specific demographic customer, ... Super autos require ...
    (alt.coffee)
  • Re: VPN Settup
    ... search for HOSTS or LMHOSTS. ... > with entries for all machines on the LAN you need to access by name. ... >> clients do not need to be domain members to access resources, ...
    (microsoft.public.isa.vpn)
  • Re: VPN Settup
    ... search for HOSTS or LMHOSTS. ... > with entries for all machines on the LAN you need to access by name. ... >> clients do not need to be domain members to access resources, ...
    (microsoft.public.win2000.ras_routing)
  • Re: Unable to connect to shared directory, shared files from XP Pro client to XP Home Client on simp
    ... Here is the fix ... ... header discussed NAV so that is where I went. ... Home machines vs. the XP Pro machines was a red herring. ... None of the clients can view, open, read, change, ...
    (microsoft.public.windowsxp.general)
Loading