From: "Hrvoje Mesing" 


"John Beckett"  wrote
in message news:v0rqh19ch5qjp5k6mr5dv87dtoqicshqpt{at}4ax.com...

> I'm not quite sure what you mean (the arp table as shown by 'arp -a' at
> command prompt?). However, I think that disabling the scope on a DHCP
> server is a bad idea. You will probably find that the DHCP server is
> listening, but since it has nothing to offer clients it sends a NAK
> (negative acknowledgement), telling them to go away. I think it would be a
> little bit of luck, depending on timing etc, as to whether the second DHCP
> server provides the required lease. You certainly won't get a good result.
>
> On the DHCP server with the disabled scode, at command prompt:
> netstat -an | find ":67"
>
> I expect you will see that the server is listening on UDP port 67 (despite
> the fact that it has no IP settings to offer clients).
>
> I believe you need to disable the DHCP service to temporarily turn it off.
> I have done this ... can't quite remember ... I think I just found the
> DHCP service in services.msc and stopped it and set Startup = Disabled.


-+-

You are right about: if scope is disable, dhcpD IS still running :) Still,
that is not what is making problems, nor problems are driven by static arp
entries (yes, arp -a). If static arp and ping goes, there is a pretty good
chance that I could get CIFS working. Still, if there is a
"strange" static map then I cannot nor ping nor map the other
host.

Ok, so, I had this:

First DC: dhcp
Second DC: 3com pxe boot server, File Server (map roaming profiles and
network stuff), Print Server, GhostCast server

- 3Com PXE Boot services + Symantec GhostCast server.
- configured GhostCast boot loader for Intel net cards.
    : static arp entry - pingable, can map
    : All of the machines get the dhcp ip, pxe boot image, loader and
everything else.

+ tried with computer that had broadcom net card
    : machine got ip from dhcp, cannot load ghost and connect to the
ghostcast server
    : static arp entry - cannot ping, cannot map

-+-

- standard (same scope) dhcp, already installed clients (WinXP)
    : client not connected to the network for 30 days
    : taken ip from dhcp, static arp entry on DC (File Server DC), cannot
ping, cannot map same DC (I can see all other machines! - including DHCP DC)

- same situation, normal DHCP giveaway IP, can ping everything, can map
everything situation from WinXP.


-+-

Strange, sometimes same clients wont work as they get static entries in arp
cache on the File Server DC.
Could not catch anything interesting with network monitoring.

-+-
M.

--- BBBS/NT v4.01 Flag-5