Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 194
  • Last Modified:

Reboots take 10-15 minutes "establishing network connection" - networking to LOCAL SUBNET does not work!?

I built this server and took it into the server room. Put it on the network and everythign seemed to work.  Joined the domain, made it a domain controller, took primary on all the FOMC (schema, infrastructure, pdc, etc...), made it a catalog server, enabled caching of universal account stuff....

The secondary controller, for some reason, would not "demote".  That should have been my first clue, I guess.  Kept saying that it could not find the domain controller with it's computer name in it...

But on this new server (server2), internet browsing was fine, the Active Directory tree was fine, everything  looked exactly as it should...

So I proceded to copy all the files I needed and re-create the shares...  then I shut down the old primary (Server 1).

With server 1 off line, user accounts would not find their profile or home directory.
Then I discovered that the DNS on Server 2 was not enabled - it had "replicated" the zone, but was not responding.  I went through the configuratino / activation wizard and that all seemed to work - but still no profiles.  And so it went... troublshooting for 3 hours...

Server network card is set up perfectly.  I can surf the web, ping the default gateway, but I can't ping workstations.  So I added a reverse zone.  No luck.  Workstations can ping SERVER2 by IP, but not always by name...

Something seems broken in the DNS component... so, any help here?  Do I have to just reinstall the entire thing? (probably would have saved myself about 3 hours!)
0
Bigjohn-s
Asked:
Bigjohn-s
  • 5
  • 3
1 Solution
 
jar3817Commented:
what resolvers do you have set in server2 and in your clients? They should all be set to the domain controllers with no outside (isp) nameservers listed. I have a feeling that your clients are trying to use the old server as a dns server (given the address via dhcp or static). Server2 should also be set to use itself as the dns server for resolving.
0
 
Bigjohn-sAuthor Commented:
All machines contain static IP and DNS...
I set server2 to use 127.0.0.1 and also it's IP address....
0
 
jar3817Commented:
and those static DNS settings in the clients point to the ip of server2?
0
Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

 
Bigjohn-sAuthor Commented:
yes.

server2 IP = 192.168.0.36

Static DNS entry for workstations:
192.168.0.36

Server2 static DNS entry = 127.0.0.1

one other thing of note, perhaps -
I removed and reinstalled the DNS service, and ensured that the network drivers are fully up to date wtih all power save featured turned off.

On the SERVER, I cannot even PING the workstation by IP!?

but I can ping the main router, default gateway, and the entire internet....

configuration is:
netmask: 255.255.255.0

The workstations CAN ping the server by IP.  The server cannot ping them...

Just ODD.

The key problem, here, is that the SERVER (server2) when it reboots, sits on the reboot / configuring network connections screen for 10-15 minutes...  and after it boots, workstations can ping, but the server can't ping the workstation, even by IP...
0
 
jar3817Commented:
Maybe a routing problem. Is the server in the same subnet as the workstations? What are the default gateways of the clients and the server? Are there any routers in between then?
0
 
Bigjohn-sAuthor Commented:
This is a tiny network.  1 server 3 workstations 2 networked printers.

192.168.0.x
255.255.255.0 net mask

there is ONE router connected to the external T1 that supplys NAT for the network.
0
 
Bigjohn-sAuthor Commented:
Ok.
One of the OLD client workstations, running win2k, can login properly and access the network drives...

The new workstation, with XP Pro is the one with the issue... I have to think that maybe there is something in the XP Firewall  I'll have to check that out...

Of course, additonal feedback is always welcome gents!  come get some points.
0
 
Bigjohn-sAuthor Commented:
Something went wrong in the demotion / promotion process, even though I've followed the steps recommended here on this site and by microsoft.
So, I reinstalled the OS and the domain.
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

Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now