server issue....

[E.J.FUDD]

ok ever since the lighting hit, there is one thing that will not fix itself and im unsure of where this problem resides at.

...were the issue raises its ugliness is one of the workstations cannot connect to the file and print server....it cant even see it on the network, (though some applications can and do correspond with the file and print server.

i can ping fine back and forth

i ahve tried it reverse from the file and print server but ..it says it cant.

when i go to look at the network it fails, i can read and change the active directory but the errors say differntly...


errors in log file

windows cannot query for the list of group policy objects

windows cannot find the local machine account

the security system could not establish a secured connection with the ldap

dynamic registration or deregistration failed for one or more of the dns records


 and this one too.....................


The DNS server was unable to open the Active Directory.  This DNS server is configured to use directory service information and can not operate without access to the directory.  The DNS server will wait for the directory to start.  If the DNS server is started but the appropriate event has not been logged, then the DNS server is still waiting for the directory to start.

[MuffDiver]

right, I saw the ones about dns and active directory, I think you need to dcpromo the file server back down to a member server.  I really don't understand how the network was designed to function.  I would have set services up a little differently if it were my network.  This could require one morning or afternoon where you could backpup all the files on the file server and make them available on the main DC.  Configure a DFS and share files there. This would give you time to fix any HIPPA things that are not setup 100% compliant.  Making a backup and then making the backedup info available will prevent and down time due to no data access.

Not sure how much you wanna try to do, or how large your file server is, but It would fix a lot of things if you wipe it out and start fresh.

[E.J.FUDD]

its down to the netlog on error...

the loopback is set to 10.10.10.1

cookie looked at it and we found were someone else had the same errors and set the loopback to 127.0.0.1 and that solved the error....this would be cool and all IF we knew where the hell to change the loopback AT.

cookie being more technically proficient can explain further. but thats about the skinny of the situation.

[Balaso]

Open your hosts file, located under %WINDIR%\System32\drivers\etc

I used notepad, in it you should see: 10.10.10.1       localhost

change it to: 127.0.0.1       localhost


That line resolves locahost to the loopback IP address


Also check the networks file in the same directory.

[MuffDiver]

damn it balaso.... you beat me to it...I need to check the boards more thuroughly when I get on here.. I missed fudds reply.


this also points out what I said about not knowing what someone else did before you got there and the mistakes, or methods to their madness they used.

[Balaso]

damn it balaso.... you beat me to it...I need to check the boards more thuroughly when I get on here.. I missed fudds reply.

Well somebody has to pick up your slack! LOL

No really, It was good for me, I didn't know the answer before I saw this post so I got to research and learn something new.