Printable View
lol, some of those error messages would have to be very interesting indeed.
As far as user account names.. I wasn't aware that Xp prevented you from naming it the same as the machine name. I really appreciate that tidbit. I'd never had a problem because, in the case of the machine I'm working with now, I call it "SalmonPatty2149" and my account log on happens to be my first name.
I have never understood that goofy rule...Drove me bonkers until I learned about it.Quote:
The computer was called ..... Helen. It's now known as jesmond and "User" has been successfully renamed Helen.
So why is it a computer name can't match a user name? Please tell the Wolfman more :)Quote:
Originally Posted by AngelicKnight
I believe it has to do with active directory....it would create duplicates
old school is to use name01 for computername
MLF
But I think this problem occured in Windows 95 when Active Directory was nothing more then a itch in Bill Gates pants.
Ya know I don't thinks that's it. Different OU's and all that.Quote:
Originally Posted by morganlefay
/MUST find out why
Its gotta be a network thing....
an MS network thing
Netbios, wins
MLF
Its WINS...
it keeps track of both USERNAME and COMPUTERNAME
http://technet2.microsoft.com/window....mspx?mfr=true
and exchange 2003 still needs it...
http://support.microsoft.com/kb/837391Quote:
SYMPTOMS
In larger Microsoft Exchange Server 2003 organizations and larger Microsoft Exchange 2000 Server organizations, some operations do not work correctly if NetBIOS name resolution is not working on the network.
Back to the top
CAUSE
Exchange 2003 and Exchange 2000 still have several NetBIOS dependencies. You may have to use NetBIOS name resolution across different subnets for the successful operation of all Exchange components, depending on the network topology.
Back to the top
RESOLUTION
Microsoft recommends that Exchange organizations use Windows Internet Name Service (WINS) and DNS for name resolution. Installations of Exchange 2003 and Exchange 2000 in large and subnetted organizations without WINS have not been fully tested. In large organizations, NetBIOS name resolution through broadcasts may not function correctly. Some Exchange functionality may also be affected.
MLF
Explains the insane machine name pattern at work.
We're using exchange 2003 for most of our workstations.
Our airport code and 24 random number/letters
It's a licensing thing...Helen can't exist in more than one instance on the network. Users and workstations can't share the same name for that reason. The workstation qualifies as a network even if it is just one machine. It makes the Windows environment's head asplode.
O