Re: DHCP problem



"yifli" wrote:

No, I haven't been able to get any DHCP offer.
Restarting the Windows Deployment Service dose not help and I actually I
already specified pxeboot.n12 as the boot file.

In network monitor, I noticed something like this:


The table should look like this :
Network Addr 1 1-->2 2-->1 Network Addr 2
-----------------------------------------------------------------------
client MAC 25 *BROADCAST
server MAC 7 6 client MAC
server MAC 6 *BROADCAST



The second line in the table was generated when I was giving command
'ipconfig /renew' on my client machine . And in the network log file, I can
see there're pairs of DHCP request and DHCP ack.

The first and third line was generated when I tried to network-boot my
client machine .

Do you have any ideas what's going on?

thx

Yifei


"Mathieu CHATEAU" wrote:

So you get a dhcp lease now ?

Yes it should include a small file to get by tftp
Restart the service and check for error in the eventlog

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"yifli" <yifli@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:343F6138-8375-4CF7-8359-12BCE16081E5@xxxxxxxxxxxxxxxx
I keep getting the error like this
PXE: no boot file name received

Does this mean my PXE server (WDS service) has some problems?

Yifei
"Mathieu CHATEAU" wrote:

You may also change the port on the hub

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"yifli" <yifli@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D07BF14C-BB53-4C14-933D-084B2D8EECAB@xxxxxxxxxxxxxxxx

One server is running DHCP and another is running Windows Deployment
Service.
I already authorized both servers .

The problem is the workstation can't even get the DHCP offer in the
first
place.
Somehow it can't see the DHCP offer sent by the DHCP server.

I'll try what you suggest and post back with my results.

thx

Yifei

"Mathieu CHATEAU" wrote:

Could you try with another network card / PC / cable ?

If you remove the lease (from previous boot) on the dhcp server and
try
again ?

Is it a RIS Server ? If so, is it still authorized, all services
(remote
installaiton) started ?

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"yifli" <yifli@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F552F22A-4BAB-41D0-854B-F58168D89FA0@xxxxxxxxxxxxxxxx
Thank you for the reply.

In our test environment, we use a hub to connect two servers and one
workstation.
I did not even get prompted to press F12 because the workstation
could
not
get DHCP offer at all.

Yifei


"Mathieu CHATEAU" wrote:

is the port on the switch forced to 100/full duplex or other than
auto
?

So you press F12 but doesn't get a dhcp lease ?

Is it a cisco switch ? It may turn on but block it to evaluate
spanning
tree. It may take 30 secondes, more time than the time to get the
PXE.


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"yifli" <yifli@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5BD8A571-EFE4-41D7-AD96-05435A3FF2E1@xxxxxxxxxxxxxxxx
My network card is PXE enabled. It was working before.

Yifei

"Mathieu CHATEAU" wrote:

hello,

so you are looking to boot from the network (RIS)?
Is Your network card PXE enabled ?

Evaluating Remote Boot Capabilities of RIS Clients
http://technet2.microsoft.com/windowsserver/en/library/5f06b846-0ba9-47b5-9dd9-306065ca18681033.mspx?mfr=true

--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"yifli" <yifli@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D54A4D37-6A98-4FC0-BE64-D8D97A965F4A@xxxxxxxxxxxxxxxx
Hi,

My Windows XP Pro with SP2 box couldn't get DHCP offer when I
tried
to
boot
it from network. But it does not have problem with getting
DHCP
offer
from
the same DHCP server after the OS is up and running.

I looked at Windows Network Monitor when I tried to
network-boot
the
machine, I saw the machine sent a DHCP request and the DHCP
server
replied
with a correct DHCP offer, but somehow the machine did not get
that
offer.

Could anyone help me out?

thx

Yifei










.

Relevant Pages

  • Re: DHCP problem
    ... I checked the meaning of PXE-E53: it means the client did get a DHCP offer ... "Mathieu CHATEAU" wrote: ... already specified pxeboot.n12 as the boot file. ... Does this mean my PXE server has some problems? ...
    (microsoft.public.windows.server.general)
  • Re: Static IP Vs DHCP
    ... most of us are not running diskless workstations ... >want to hard code the addresses on several hundred DOS boot disks just ... network, by booting to a floppy, then running a network application that ... >you stated that DHCP had less functionality than static addresses. ...
    (comp.security.misc)
  • Re: DHCP problem
    ... PXE-E53: No boot filename received. ... So the client machine did get a dhcp offer, it just searched for a long at ... "Mathieu CHATEAU" wrote: ... One server is running DHCP and another is running Windows Deployment ...
    (microsoft.public.windows.server.general)
  • Re: Netsh- "Incorrect Function" trying to set IP.
    ... Network is fine since I can map a network drive & ... It shows both NICs configured for dhcp. ... Without touching the PC, so the hardware is unchanged, I boot to my ... run-time image and I get the above situations. ...
    (microsoft.public.windowsxp.embedded)
  • Boot with DHCP
    ... Sorry if is'nt the right group, any network, dhcp, related group is blocked ... Im trying to boot a Sun Fire V240 on a different subnet than the boot ... The boot server is running ISC dhcp. ... But i get address already in use on the Sun Fire V240. ...
    (comp.unix.solaris)