Solved

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

Posted on 2008-06-23
8
185 Views
Last Modified: 2013-12-23
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
Comment
Question by:Bigjohn-s
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 3
8 Comments
 
LVL 26

Expert Comment

by:jar3817
ID: 21845517
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
 
LVL 2

Author Comment

by:Bigjohn-s
ID: 21846001
All machines contain static IP and DNS...
I set server2 to use 127.0.0.1 and also it's IP address....
0
 
LVL 26

Expert Comment

by:jar3817
ID: 21846495
and those static DNS settings in the clients point to the ip of server2?
0
Flexible connectivity for any environment

The KE6900 series can extend and deploy computers with high definition displays across multiple stations in a variety of applications that suit any environment. Expand computer use to stations across multiple rooms with dynamic access.

 
LVL 2

Author Comment

by:Bigjohn-s
ID: 21846674
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
 
LVL 26

Expert Comment

by:jar3817
ID: 21846708
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
 
LVL 2

Author Comment

by:Bigjohn-s
ID: 21848120
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
 
LVL 2

Author Comment

by:Bigjohn-s
ID: 21855959
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
 
LVL 2

Accepted Solution

by:
Bigjohn-s earned 0 total points
ID: 21969136
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

Featured Post

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Windows 2008 set profile 9 62
Manage Wireless Networks (Advanced) on Windows 10 7 90
BgInfo help 5 106
Mail Exchanger (MX) Record 5 85
Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
Trying to figure out group policy inheritance and which settings apply where can be a chore.  Here's a very simple summary I've written which might help.  Keep in mind, this is just a high-level conceptual overview where I try to avoid getting bogge…
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question