Re: Unable to connect client to server - DHCP not assigning an IP to clients

Jerry,

I will attempt to answer your queries, apologies if I have
interpereted your request incorrectly.

1. I reviewed the event viewer - there is one warning after startup
Event ID: 20169 - Remote access
Unable to contact a DHCP server

2. Ipconfig/all
Server: Windows IP Configuration


Host Name . . . . . . . . . . . . : SERVER
Primary Dns Suffix . . . . . . . : techengineering.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : techengineering.local

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 S Server
Adapter #2
Physical Address. . . . . . . . . : 00-0E-0C-6D-54-B5
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


Client:
Host Name . . . . . . . . . . . . : JUSTINW01
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 Ve Network
Connection
Physical Address. . . . . . . . . : 00-07-29-7c-29-39
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.184.43
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . :

3 Run Internet Connection wizard - no difference

4. To my knowledge no changes were made to the SBS before the DHCP
failure.

5. Restared DHCP service - no change

6. Release and renew IP on client
Following error resulted:
Windows IP configurator
An error occured which renewing interface Local Area Connection:
unable to contact your DHCP server. Request has timed out

7. Disable firewall software - not sure how to do this - no firewall
hardware, client is WinXp SP2 with firwall enabled, not sure whats on
the server whatever comes with SBS

8 Just Server, 1 client connected to server currently on the network
- no other device present which could assign IP

9. Yes, when I attempt to connect another workstation to the network
same result

I also checked out the hardware and was able to connect 2 workstations
together (for testing purposes only) without any problesm




v-jerryz@xxxxxxxxxxxxxxxxxxxx (Jerry zhao (MSFT)) wrote in message news:<3XPWXL$PFHA.3136@xxxxxxxxxxxxxxxxxxxxx>...
> Hi Wallace,
>
> Thanks for your posting.
>
> Before we start, I'd like to gather the following information:
>
> 1. Are there any event logs related to this issue?
>
> 2. Run ipconfig /all on the server and the client, post the output in the
> newsgroup
>
> 3. Re-run the CEICW and see if there is any help.
>
> 4. Did you make any change on the SBS server before the DHCP fail to work?
>
> 5. Stop and then restart the DHCP service in the service console, any
> change?
>
> 6. Run "ipconfig /release", "ipconfig /renew" on the client, let me know
> the error messages you get.
>
> 7. Disable any firewall devices or software, see if there is any change.
>
> 8. Make sure that there does not have multiple DHCP servers running in the
> network.
>
> 9. Does this issue happen for all the workstations?
>
> If you have any concern on this thread, I am glad to be of further
> assistance. We look forward to hearing from you.
>
> Best regards,
>
> Jerry Zhao (MSFT)
>
> Microsoft CSS Online Newsgroup Support
>
> Get Secure! - www.microsoft.com/security
>
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
.

Relevant Pages

  • Re: Application Hang
    ... Back to DHCP, what about the client ipconfig without the DG ip address? ... When the old server crashed, it required a new motherboard and CPU. ... You should see at least,006 DNS servers, 003 Router. ...
    (microsoft.public.windows.server.networking)
  • Re: Windows Server 2003 DHCP server - Does not release IP Addresses
    ... on the SWITCH or the ROUTER. ... the clients will not know which server to go for DHCP REQUEST. ... And, if that Switch had some issues, how will the other DHCP server ... This error is usually received when the client booting up via PXE is ...
    (microsoft.public.windows.server.general)
  • Re: DHCP handles Naks one one vlan differently
    ... If the problem is on the network with the DHCP server, ... Frame 156 ... Your (client) IP address: 0.0.0.0 ...
    (comp.dcom.sys.cisco)
  • Re: Sending hostname with DHCP
    ... default route and the default dns host. ... Below is my /etc/resolv.conf created by the dhcp client. ... > This seems to depend on the client as much as the server. ...
    (Fedora)
  • Re: DHCP and companyweb problems
    ... If the DHCP traffic is being denied by ISA which rule is it showing that is ... SBS FTP Server Access, RDP Server Access, RDP Outbound disabled. ... Client name is correct ...
    (microsoft.public.windows.server.sbs)
Loading