Originally Posted by amit_bngn
I am trying to log in with Administrator account.Now how can i join my laptop in the domin if its only getting a 169 ip whereas my network runs on 192 ip.
and if u say that put an static ip in the laptop and then join it in the domain and then again check whether i am getting ip automatically or not.
Let me inform you that i alredy perform this step but trying to get a ip automatically from dhcp server is not resolved
---------- Post added at 13:15 ---------- Previous post was at 13:09 ----------
I m simply using a dhcp server on win 2003 nothing more than that no nac no authentication no firewall nothing.
so your saying (as a test), you have manually assigned them a static IP ,gateway,DNS address etc and THEY THEN WORK FINE?
you can then get on the LAN and do as you expect etc.....you need/want them to also work with DHCP as they should do already.
right, its not possific to your problem as such, but iv seen this work for the VM cable modem to wired ethernet MAC No.s that are set for a generic 00.00.00.00 and getting this windows OS 192 ip problem every time, so it will potentially work as a fix for your windows domain problem too
the windows OS has some form of errata as related to this wired 00.00.00.00 MAC, iv never worked out exactly why, but heres potentially a simple fix you can try.
check your problem cards(s) are of the generic 00.00.00.00 MAC type and simply give/assign them another MAC No. instead
some wired ethernet cards than are using 00.00.00.00 as their generic MAC dont seem to talk in the official spec, it only seems to effect wired Ethernet cards as all the 00.00.00.00 USBto ethernet bridges sticks iv tryed perfectly work fine with the VM cable modem in gettign a valid DHCPd given IP No etc.
its assumed this windows DHCP/d problem goes far deeper, so just change the base MAC No. in the registry to something better but valid and report back if it fixed this problem for you?, if it did, then MS need to work out why their code is breaking DHCPd requests and fix it.
you can boot and use a simple Slax liveCD with these RTL 8139 for a quick test, and you should see them connect to your domain, send the Multicast request and get it given back with your valid DHCP packets etc.
and the slaxCD will give you a valid new MAC to use at the same time as it overrides/replaces the default wired 00.00.00.00 MAC No. as a default action so you dont have to make your own up.
boot, log in as root
, password as toor
iv mentioned this VM CM problem many times before and changing its default MAC has never failed me yet to resolve the very common windows OS 169 ip problem, perhaps it will also solve your windows faulty app/OS code problem.