RE: cannot network client to 2003 server
From: TJ Campana [MSFT] (tcampana_at_online.microsoft.com)
Date: 04/12/04
- Next message: Bob: "New W2K3 Server And Hanging Network"
- Previous message: Michael Holzemer: "Re: SMTP command line interface"
- In reply to: Joe: "cannot network client to 2003 server"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 12 Apr 2004 14:19:37 GMT
--------------------
>Content-Class: urn:content-classes:message
>From: "Joe" <anonymous@discussions.microsoft.com>
>Sender: "Joe" <anonymous@discussions.microsoft.com>
>Subject: cannot network client to 2003 server
>Date: Mon, 12 Apr 2004 05:43:38 -0700
>Lines: 8
>Message-ID: <187e101c4208b$c6d494e0$a601280a@phx.gbl>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="iso-8859-1"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
>Thread-Index: AcQgi8bUhUaxVPAoT8+L81IX6E2hqA==
>Newsgroups: microsoft.public.windows.server.networking
>Path: cpmsftngxa06.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.networking:11496
>NNTP-Posting-Host: tk2msftngxa14.phx.gbl 10.40.1.166
>X-Tomcat-NG: microsoft.public.windows.server.networking
>
>I keep getting a private I.P address assigned on a xp pro
>client , whenever I try to release and renew ip
>parameters the does not release and reassign the new IP
>address. I checked DHCP, AD, and even assigned it a
>reserved address hoping that it will resolve the issue.
>Any suggestions? Humbly grateful.
>
>Joe
>
Joe,
Are you getting a private IP Address (192.168,x.x 172.16-31.x.x, or 10.x.x.x) or are you getting an APIPA (Automatic Private IP Address
(169.254.0.0-169.254.255.255)) address? If you are getting a private IP then you will only get that from an DHCP Server set to hand out
addresses in that range, so i am assuming that you are referring to an APIPA address.
Is the client that is requesting the addresses in the same broadcast domain as the DHCP Server? That is to say will a broadcast sent from
the client ever reach the DHCP Server. DHCP is all broadcast based so if the client is configured for DHCP and it is getting an APIPA
address then the DHCP is not responding. Are thee any other clients on this network that are failing to get the address? If not, then we are
really looking at the XP machine as the issue here. I would check Subnet Mask of this system to be sure it thinks that it is in the same
network as the DHCP server. Also make sure that the Internet Connection Firewall is not enabled on this system.
If you assign a Static IP Address to this system does the client function normally on the network? If the DHCP Server is not on the same
subnet then you will need to use a DHCP Relay Agent or other mechanism like IP Helper to get the broadcast for DHCP across the
network device that is blocking.
232703 How to Use DHCP to Provide Routing and Remote Access Clients with
http://support.microsoft.com/?id=232703
220874 How to Use Automatic TCP/IP Addressing Without a DHCP Server
http://support.microsoft.com/?id=220874
T.J. Campana [MSFT]
Microsoft EPS Networking
-- This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
- Next message: Bob: "New W2K3 Server And Hanging Network"
- Previous message: Michael Holzemer: "Re: SMTP command line interface"
- In reply to: Joe: "cannot network client to 2003 server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
