+ Post New Thread
Results 1 to 8 of 8
Windows Server 2000/2003 Thread, Windows Update causing DHCP to fail? in Technical; Is anybody aware of a Windows Update that is causing DHCP to fail? There have been 2 cases in recent ...
  1. #1
    Unvalidated User
    Join Date
    Jan 2012
    Location
    Bromley
    Posts
    3
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Windows Update causing DHCP to fail?

    Is anybody aware of a Windows Update that is causing DHCP to fail?

    There have been 2 cases in recent weeks and there is no obvious reason.

  2. #2

    Dos_Box's Avatar
    Join Date
    Jun 2005
    Location
    Preston, Lancashire
    Posts
    9,065
    Thank Post
    629
    Thanked 2,232 Times in 1,020 Posts
    Blog Entries
    23
    Rep Power
    638
    What errors are you getting in the logs? Or is the service just crashing?
    Also, what version of server are you using (I know it's in the 2000/2003 thread but we have to check)?

  3. #3

    Join Date
    Apr 2010
    Posts
    2,073
    Thank Post
    85
    Thanked 189 Times in 156 Posts
    Rep Power
    84
    I had this. I found that after the update the dhcp bindings had been removed. I re-ticked the bindings (in DHCP) and bingo all working.

  4. #4

    Join Date
    Apr 2010
    Posts
    2,073
    Thank Post
    85
    Thanked 189 Times in 156 Posts
    Rep Power
    84
    Did you fix the issue?

  5. #5
    Andie's Avatar
    Join Date
    Sep 2006
    Location
    Cambridgeshire
    Posts
    797
    Thank Post
    167
    Thanked 66 Times in 49 Posts
    Rep Power
    30
    Quick query about your issue, as we have a batch of Windows 7 machines that have just started failing to connect to the Internet. They can see the server (2003) but can't get out beyond. Strange IP address on wireless network connection, starting with 169 that I've been told is a default Windows 7 address, used when the network fails to get an address using DHCP. We appear to have enough free IP leases. The affected machines were fine up until a week ago. XP clients don't have the same problem. Wouldn't be a server update issue here though....? Is this similar to your problem...?

  6. #6
    Unvalidated User
    Join Date
    Jan 2012
    Location
    Bromley
    Posts
    3
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    The issue has been fixed. After some investigating we found that for some reason the firewall decided to block 2 ports that were blocking DHCP, no idea why? Once we set up some exclusions for the firewall, ip address started to be leased out.

    Any idea why this could happen?

  7. #7

    Dos_Box's Avatar
    Join Date
    Jun 2005
    Location
    Preston, Lancashire
    Posts
    9,065
    Thank Post
    629
    Thanked 2,232 Times in 1,020 Posts
    Blog Entries
    23
    Rep Power
    638
    What make/model of firewall is it, and why is the internal network going via a firewall?

  8. #8
    Unvalidated User
    Join Date
    Jan 2012
    Location
    Bromley
    Posts
    3
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Sorry my mistake, i meant Windows Firewall. Do you think this could have been by a windows update?

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 18
    Last Post: 12th September 2013, 05:44 PM
  2. Windows Update causing BSOD!
    By TechSupp in forum Windows
    Replies: 3
    Last Post: 9th February 2011, 04:43 PM
  3. Replies: 0
    Last Post: 13th December 2007, 07:46 PM
  4. Replies: 11
    Last Post: 20th October 2006, 04:14 PM
  5. Replies: 18
    Last Post: 14th October 2005, 09:28 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •