Sign in with
Sign up | Sign in
Your question

Man, did i f up my network... help!!

Last response: in Windows 2000/NT
Share
October 18, 2002 12:21:58 PM

my home network, nuthin really important... but heres what i did. i had an nt server and 5 2k clients. i also had a 2k server that was just being used as a client. anyway, i hated the nt server, so i removed it and promoted the 2k server in a different domain and then i went to each client and changed their doamin. now it is incredibly slow and when i boot up with one of the clients, i have no admin rights. there is only one account (tdean) on the entire network, and it is the admin acct on the 2k server. i know i should have put nt on the 2k server and promoted it that way, then reinstalled 2k, but i didnt feel like it. how the hell do i fix this?

....the crows seemed to be calling him, thought caw....

More about : man network

October 18, 2002 1:51:51 PM

didn't we go through this a while back, I seem to remember telling you something about sticking with the "administrator" account instead of trying to change it to another name. Anyway, where exactly is it EXTREMEMLY slow? Just logging onto the domain, or everything afterwards as well? Also, did you double check the tdean account in the new domain to see if it indeed does have admin rights (maybe you were just remembering it from the old domain)?

<i>It's always the one thing you never suspected.</i>
October 18, 2002 2:07:02 PM

lol.... yeah, you did tell me that before, and i did it. it worked. this is a seperate f up. the "extremely slow" part is the logon. it takes ~5 minutes. i did check the tdean account, and it does have admin rights. i rebooted all the systems, server first, just in case they were still looking for a different domain controller or something.

....the crows seemed to be calling him, thought caw....
Related resources
October 18, 2002 2:55:36 PM

so the original NT PDC is totally off the LAN, you have a new 2K PDC with a new domain (Let's call the OLD domain TOM and the NEW domain PABST)? You've got (let's simplify it) a 2K machine that you're trying to log into the PABST domain and the login takes 5 minutes? Which step of the login is it hanging on (it usually gives you a status line of what it is doing amongst 5 steps or so on the bottom of the login box)? You definitely added the 2K clients into the domain correctly?

I'm also suspicious of the 2K PDC doing the "right" thing AFA legacy NT domain controller vs. full blown AD controller/server. Problem is I don't know enough about AD to make that determination. Maybe someone else here does. I still have never really USED Active Directory.

<i>It's always the one thing you never suspected.</i>
October 18, 2002 3:50:19 PM

your scenario is correct. i just pulled the original nt system and started from scratch with the 2k. there are 4 other clients as well. i did (as far as i know) add the clients properly. first, i promoted the server to its own domain, then i went to each client and changed the domain (using the tdean acct, which incidentally, no longer has admin rights for some reason) by rt clicking my comp--> props--> identification etc.... did i do something wrong? well, obviously i did, but can you tell what?

....the crows seemed to be calling him, thought caw....
October 18, 2002 8:52:55 PM

sounds like the right thing. Where is it slow?

<i>It's always the one thing you never suspected.</i>
October 18, 2002 9:18:13 PM

well.... im embarassed to say it doesnt seem slow today. think maybe it had something to do with me using a router as dhcp server? i literally just took the old server out by shutting it off. the weird thing, though, is that the "tdean" acct still isnt recognized as having admin rights. when i go to the server, it says it does..... oh well, i guess thats for another time...

....the crows seemed to be calling him, thought caw....
October 20, 2002 6:46:50 AM

I few words here about local versus a domain admin, just in case.
I'll bet the "tdean" account is a local administrator on the new domain controller. If so, that doesn't mean it can necessary do anything on the domain itself.

Are you using the "Active Directory Users and Computers" MMC in 2000 to create/edit the TDean or other accounts? This appears after you install the AdminPak.msi.

-Steve
October 24, 2002 5:42:52 AM

im 95% sure your problem was dns. you said you were using the dhcp from the router? now are you using the dhcp on the 2k server? you need to have the dns setting on the clients set to the ip of the 2k server.

how do you shoot the devil in the back? what happens if you miss? -verbal
October 24, 2002 11:51:19 AM

aaahhhhh..... thats what i was hinting around about. i will try that right when i get home.... thanks to you guys for being patient. im still learning.....

....the crows seemed to be calling him, thought caw....
October 25, 2002 12:35:11 AM

you are right!! the servers system log was full with dns errors.... now, how to fix it.....

....the crows seemed to be calling him, thought caw....
October 25, 2002 2:05:44 AM

all you need to do is set the dns setting to the ip of the server and log on times should return to normal

how do you shoot the devil in the back? what happens if you miss? -verbal
October 25, 2002 2:21:07 AM

im confused. the server gets its ip from the router too. i'll clarify... i have comp1 connected to the modem and server and others, connect into router.

....the crows seemed to be calling him, thought caw....
October 25, 2002 3:22:30 AM

not sure i understand your structure. you have the modem conected to the router and another computer? so you basicaly have two isp ips? server and the rest are behind the router and comp 1 is exposed? is comp 1 the only one having problems?

how do you shoot the devil in the back? what happens if you miss? -verbal
October 25, 2002 12:02:04 PM

ok, i dont think i said that correctly.... they are all behind the router. i have the data line in connected to the modem... then the modem is connected directly to the router along with 2 computers and a hub. the server is one of the computers connected directly. i hope that helps, i think i confused the issue before.

....the crows seemed to be calling him, thought caw....
October 25, 2002 5:46:22 PM

So long as they're all connected behind the router, it's irrelevant whether they plug into the router itself, or the hub which plugs into the router.
First off, make your server a static IP. This will simplify things. It sounds like you need to either setup and configure the dns server on your win2k server, and then add that IP in to your DNS settings on the clients, or simply add the server's dns name to your hosts and lmhosts files on the clients. With a small network both ways work equally well.
October 26, 2002 5:10:12 PM

you did install dns on the ad right?

how do you shoot the devil in the back? what happens if you miss? -verbal
October 29, 2002 8:13:15 PM

im confused.... the isp didnt give me a static ip... how do i assign one to the server?

....the crows seemed to be calling him, thought caw....
October 29, 2002 8:14:35 PM

its installed, but im sure its not correct.... it takes ~5 min to open a mapped drive one room over.

....the crows seemed to be calling him, thought caw....
October 30, 2002 12:44:51 AM

he meant within the LAN, i.e. don't let it obtain an address via DHCP.

<i>It's always the one thing you never suspected.</i>
November 2, 2002 3:01:31 PM

Yes. Your router has two IP's, the public IP, the one you get from your ISP, and it's internal LAN IP. Probably 192.168.1.1 or something. All the computers on the LAN are receiving DHCP numbers like 192.168.1.x. Set your server to not get one via DHCP, but to manually stay at something like 192.168.1.250. I'd choose a high number because with so few clients you know the router will never lease out that high a number and you'll never have a conflict.
!