XPPro networking woes

[xakep]

There is a network based on a server Win2K, half of the stations XPro, the rest 98e.

They bought a XPro. We are changing to another PC support company, and I am filling in with an educated amateur's experience.

The network has recently upgraded and also went from a domain name xyz to xyz.com

I set up the new PC, but when I get to include this

machine into the network there is a dead end.

Did I hurry a bit when I changed the name of the PC before going to

the System-PC Name-Network ID and use the network wizard? I did also

change the name of the workgroup to what they have at the office.

I saw that the PC responded to the LAN signals. I thought XPro did

everything automatically. I see nothing in My Network places, nothing

seeen in Other Computers Around Me. I did not map anything in the

Explorer.

I went into the Network ID to use the wizard. As it told me, I went to

get the name of the workgroup, the IPs, the DNSs etc, AND the domain

name xyz.com, But it went nowhere.

Should anything be done first on the server?

What are your thoughts?

[homecomputeraid]

Is this an Active Directory Domain?

[xakep]

I don't know. What are the options for the case if it is or not?

[homecomputeraid]

When you say upgraded, what do you mean? Did you recently put in a Windows 2000 Domain Controller and switch from a Windows NT Domain to an Active Directory Domain? How many clients and servers on your network?

It sounds to me like any of the changes you want to implement should be done through your Actve Directory Controller, and you shouldn't have to touch the clients much, unless you've already done something to all of the clients.

I suggest stepping up to the plate and getting professional help with your network situation. If you choose to try and do this through the forum here, I will do my best to help.

As a consultant, I can't tell you how much more expensive it can be (and more difficult for the person you finally call) to fix mistakes made by well intentioned, but inexperienced people.

[xakep]

Well, time was in short supply. I did open the Active Servers Directory console, and using eductaed guess and what the server was seeing, entered the Properties and from there it was luck. In a way your post helped.

[homecomputeraid]

I'm glad you were able to figure it out! I hope you're able to have someone give you a hand with the network soon. Everything's ok for the time being then?

[xakep]

Everything is working swimmingly. But to be prepared, I'd like to make sure there are additional ways of looking at the network. For example, does the active server directory show IP of each PC on the network?

What other tricks can one do with the Active Server console?

I don't understand how the printers got connected - are they allways conencted automatically?

[homecomputeraid]

On your Active Directory Server, if you want to see what IP Leases are currently assigned, you can go to Start, Programs, Administrative Tools, DHCP. In the DHCP Management Console, click the + next to Scope for the subnet you want to look at, then Address Leases. The currently assigned IP Addresses will populate the right hand side of the Management Console.

Your printer configuration depends on how your printers are networked. Do they have built in Network Interface Cards (NIC's), or Jet Direct boxes (or devices from some other vendor) that take a parallel cable, or USB cable and "convert" the signal to Ethernet for you? If so, they are probably managed and queued on the Print Server(s).

Another way to share a printer on a network is to attach it directly to a computer, and share it from that computer.

If things are working, you could look at whatever you want, but you might not want to make many (any?) changes. Just make sure that if you make a change, you write down the exact steps you used so it can be undone if necessary.

[homecomputeraid]

Who knows xakep, maybe you've found yourself a new career? :)

[xakep]

Looks like it. The fun never stops.

There's more of it: another coworker reports that he can't access a PC with important file folders. The previous network manager and a new employee have created too many users and with them messed up the folders' permissions. What are your thoughts while I take a day off?

The mess never stops.

[homecomputeraid]

The preferred method of controlling folder access in Windows 2000 Active Directory is to put users into groups, and give groups rights to the folders. Have you been doing that on your network, or have you been assigning rights to folders on a per-user basis?

[xakep]

The PC with the folders is NOT on the network(to make sure it never goes on Internet, but is connected by a separate connection to a network PC.

[homecomputeraid]

Sorry, I don't understand. Is it connected using a Network Cable directly to another PC (back to back), or is it on your Local Area Network, but somehow restricted from accessing the Internet?

[xakep]

Back to back, without Internet sharing or the like, eight to a PC that IS on the network. Only this networked PC can browse the isolated computer.

[homecomputeraid]

What's the physical topology? How is the networked PC able to browse the isolated PC?

[xakep]

On your Active Directory Server, if you want to see what IP Leases are currently assigned, you can go to Start, Programs, Administrative Tools, DHCP. In the DHCP Management Console, click the + next to Scope for the subnet you want to look at, then Address Leases. The currently assigned IP Addresses will populate the right hand side of the Management Console.

On the 2000Server I found Admin Tools->DNS. It had something like Internal and External, I think, categories, I chose Internal and found the IP lists. However, I studied those Admin consoles and found that 99.9% policies of the server are not set, disabled, or not available.

I thought a server could do more than a rank and file PC could, i.e., change that PC's name, override username and synchronize it, do real cool stuff (without the need to go into individual PC) but I'm learning the reality - it must be the real bare bone server.

The most unexpected difficulty was straightening the e-mail accounts on affected PCs for the users affected. The solution was precise spelling and capitalization, and duplicating the work on the server.

Thanks for the help.

[homecomputeraid]

How many Active Directory Domain Controller's do you have? One of them should be your DHCP Server. That's where changes should be made, not on your DNS Server. Those changes should propagate throughout your network from the DHCP Server, and will update onto your DNS Server. For changing host names, I recommend doing that on the PC concerned.