• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 172
  • Last Modified:

HELP! W2K dual boot ... Urgent!

I have a couple machines that I am experiencing this problem with now.  At first I thought it was only with 1 computer... but now it has spread.

I have dual boot 2k machines that are running different language install's (yes I know, I could use multi-language, but that's not how I started the project).

The installs are on different partitions.  You can run one instance, log onto the domain and everything is dandy.  If you restart and try to log the other instance on to the domain, it will not let you... some generic error about not being able to contact the DC.   But, if I log on locally to that machine, then force it to join the domain again... it is happy and will work... but the other install stops working!

I have tried different NetBIOS names for the computers, I have tried issuing different IP addresses and logging on as different users... none of which have solved this problem.

I have not tried installing one of the 2k instances on another drive rather than another partition, but that is what I would consider an extreme measure since the person already has quite a bit of data on both installs.

This has happened with Japaneese and Korean language installs...

HELP!  This is becoming a production inhibitor and my boss is getting tired of the end user complaining (as am I).

Help!

Thanks,
Jay
0
blood
Asked:
blood
  • 6
  • 5
  • 2
  • +1
1 Solution
 
bloodAuthor Commented:
Oh, and the machines are all up on their shots and vaccinations.  So all updates have been applied... short of SP2... and I don't think there are Multi-language SP2's currently.
0
 
stevenlewisCommented:
are the machine names different? you can't use the same names, as the sid's are different, and it will confuse the dc. try using differnet comp names like comp1 and comp2
0
 
bloodAuthor Commented:
I have tried that, and it does not seem to work.  Should I wait for some kind of AD refresh or something ?

Thanks!
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

 
stevenlewisCommented:
do you have both machines accounts (names) added to the AD?
also are you using dhcp? if so, I think this may be a problem, as dhcp uses the MAC address of the NIC, and while the sid will be different, the MAC will be the same
0
 
SysExpertCommented:
stevenlewis is right that the machine may be identified by the MAC address, so there is no easy work around, unless you  can design a script to automatically join the Domain.

Other options are to use Fixed IP's for this machine, with different NetBIOS names.

I hope this helps !
0
 
geoffrynCommented:
What is the default language of your DC?
0
 
bloodAuthor Commented:
If this is all MAC based, as you are suggesting, then I think the best solution would be to install a second nic on the machine and have each install use a specified NIC and then disable the alternate nics in each install.

This would be alot more painless than setting up some kind of script that runs on boot to rejoin the domain (since that would require another reboot after it was done).

I will try that...

geoff > the DC is english, but has language support (region) for Japan and Korea.

Thanks a ton,
Jay
0
 
geoffrynCommented:
M$ has had issues logging on to DC that has a default language different than the workstation.
0
 
stevenlewisCommented:
Jay, try the NIC thing on one machine only first to see if it helps. If it doesn't you won't be spending a lot of money chasing shadows
0
 
stevenlewisCommented:
a cheaper easier test would be to statically assign the ip to one of the machines and test it (one to each OS/boot)
0
 
bloodAuthor Commented:
are you talking about _with_ 2 nics or not?
0
 
stevenlewisCommented:
NO, with one NIC, statically assign one different ip address for each boot, and see if that resolves the problem. If it does, then you can try two NIC's
0
 
bloodAuthor Commented:
I have tried that... and to no avail.

If it is MAC based, that solution wont help... becuase the MAC will be the same no matter what IP I am using.  If it was IP based, that would be a little freaky since clients that are configured for DHCP would constantly have to have their SID updated.

Thanks though, I will move on to the dual nic.

-Jay

0
 
bloodAuthor Commented:
I have been in conversations with Microsoft about this problem.

They have acknowledged that the Japanese system has some strange problem.

The Korean system is acting fine now, for some reason changing the NetBIOS name didn't work _right_ away, but after *exactly* 3 hours, it logged on.

I really don't know what to do with this Question.

Is it resolved?  Is it still up in the air?  

-Jay
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

  • 6
  • 5
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now