Auto IP Problem

  • Thread starter Thread starter Michells
  • Start date Start date
M

Michells

Hello All,

Currently I have built an Customised OS Image with Minlogon. I have a
DUA component added along with EWF. ever thing is working fine except
Auto IP addressing.

Scenario:

I connected the target PC with the other PC through Ethernet Crossover
cable.first time both the PC was provided with Static IP, then
everything was working fine.(Communication established)
Later my PC was provided with Auto IP and I was getting an IP address
(168.153.133.19) but when Auto IP was enabled in my target PC status
was "Acquiring Network address"
I restarted my target PC to take effect even then the same status.

With same configuration in Winlogon it was working fine i.e : Target PC
was providing an auto IP.

My Question :

Y my target PC is not providing auto IP in Minlogon ?
Which component needs to be added so that my target PC gives auto IP??

Regards
Michells
 
Michells,
Can you define precisely what you mean by "auto IP?" Do you mean the
process by which if the network interface is configured to obtain its IP
from DHCP and that process fails (e.g. there is no DHCP server on the
network) then the machine automatically configures itself with a 169...
address (you mentioned 168...)? Or is "auto IP" your way of referring to
DHCP address assignment?

DD
 
Hello Dawson,

Thanks for your reply. I am happy to tell that the problem got resolved
yesterday.

AUto IP basically mean nothing but the IP address provided by the
system in absence of DHCP server. U were right IP address was 169.. not
168 :-).

Solution:

The problem was I did not add "Client for MIcrosoft Network" Component.
When I added that component and auto resolved then few other dependent
component got added and I was able to resolve my problem.

Regards
Michells
 
Back
Top