I was getting the Event 1054 on the Server. I traced the problem down to a registry setting that the OCE technician changed in order to get SMB signing turned off. That basically killed communication between Workstation and Server withing the server itself and brought it down to its knees...
I have a 2003 server with DNS, i'm getting a Event 1054 error and DNS fails so i'm testing things with NSLOOKUP. I type nslookup google.com and it gives me the two ip addresses for google, but when i type nslookup "x.x.x.x" it doesn't tell me that belongs to google. It does resolve...
I already had them in there. The address 192.168.10.2 (which is the server itself) and 192.168.10.1 (which is the router) The current setup is...dhcp gives the client machines the .2 address as DNS, and the server forwards it to the router .1, then the router does the rest I presume since...
I am a newbie to Windows 2003 Server but I setup a server 4 days ago. It runs, AD, DNS, DHCP. I setup 10 user accounts and everything has been working fine. Today I shut it down to plug it into a UPS and when I powered it up, it gave me the USERENV Event 1054 error. I researched it a little...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.