PC Mac address blocked by Server

I struggled with the title for this request for help. I have server 2003 running and recently I had to rebuild 2 of the desktops attached to it. Before I did the rebuilds I removed them from the domain through the computers themselves and then I deleted them from the AD and added them back. After I rebuilt them I was able to rejoin the domian however I could never add a user to the system using the usual procedure through the user interface. I would get messages indicating the Domian could not be found etc. To compund things I could login as any user but they were always limited to 'user". I could login as administrator with full rights. I discovered that if I used a new NIC on each computer all this was avoided and I could add the user normally to the computer and they would have full rights.

So I figure the issue is tied to the mac address of the destop Nic and that someplace in the server AD I have to clear it. Can anybody shed a light on this for me?

Let me finish up by saying that at the same I added a new computer to the network and it joined and allowed user names perfectly. I have never seen this before.

Thank you

Chris

The server doesn't care about the MAC, inless you use DHCP. But if you're getting a correct IP then it's working fine.
Logging in a user on a machine will give that user limited rights by default, unless your user is in a domain group that is allowed more.
I have a feeling you don't know exactly what you are doing...

Quote:

---

Originally Posted by CeeBee

I have a feeling you don't know exactly what you are doing...

---

Gosh, CeeBee, give yourself a pay raise! Dang! All this time I thought that this support forum was just about re-enforcing stuff the posters already knew!

Holy Crap! If you assume that the posters actually need help and advice, that puts things in a whole new light! You are very knowledgeable and competent, but you are such a dick!

In fact, the server probably doesn't care about the MAC address even if it has DCHP enabled. A router might screen MAC addresses, but I don't think changing a network adapter would fix the issue, so I would suspect a damaged user profile. Of course, you have a lot more serious network experience than I do, if you could be bothered to take your head out of your butt for a minute or two.

Merry Christmas.

Randomly messing with things can have serious consequences.
We aren't talking about a home PC where data loss means having to re-download 500GB of porn, we are talking about an AD environment and someone who seemingly lacks basic knowledge of servers and networking.
There are times when calling a consultant who knows WTF is going on and how things should be done is in order. This is one of those times.