Windows 2000 Server needs a DNS Server installed and running, this is a [COLOR=red]must[COLOR=black]. Without you can not work correctly. Please, install and configure the DNS Server before continuing.
Pino
Uhmmm... you wrote "I recently bought a router. It provides IPs for all the machines so I uninstalled the DHCP service on the server" ... this is the mother of your problem. Now you have 2 DHCP server I think: your router and your server. When the the server assigns a IP of the...
Sorry... I've tested a lot of other product but the only that work fine are not cheaper than ISA. The only other way is to install a Linux machine between your network and the internet.
Pino
Ok,
if you have checked the issue http://support.microsoft.com/?kbid=258296 (see Aslamvs post) and all is ok, the next step must be the check of the DNS config.
If your machine is (on the primary net adapter) myserver.mydomain.com, having IP address 172.25.25.251, your nslookup (direct and...
OK, so then your domain is not so clear to me... your server name is galilee1.sogetel.net? Not think.... here a normal response for a server named serverw2k.renord-mi.locale having the IP Address 172.18.76.195:
C:\>nslookup serverw2k.renord-mi.locale
Server: serverw2k.renord-mi.locale
Address...
ok, from the server session are you able to do nslookup to the fully qualified name of the server itself? And nslookup using the IP address? the server respond correctly?
Pino
Ok, the 128bit is installed both on clients AND server? If not, you must do it. Also binkin's tip can help.
Surely you should apply also IE6 upgrade to be sure that all systems are up to date... but be careful to work at the same encryption level.
Uhm... in my memory I've found just one similar issue, and the problem was that on the clients was present IE with Hi Encryption. Are both (clients and server) at the same Encryption level?
This is really a strange issue... have you tryed to add (if is not installed) IPX protocol? If also whith IPX installed both on server and clients nothing changes you should provide the standard diagnostic files to understand the problem.
Ok, I've understand: the correct domain name you must type in the w2k clients is DU-RE (the netbios name) and not the full AD domain DU-RE.COM. In XP clients the domain is asked 2 times: the first one you must type the AD domain name, the second the NetBios name. Try this... should be your...
so try this and pray:
http://www.microsoft.com/downloads/details.aspx?FamilyID=432ea30d-41d6-4f5d-a6a8-e6149168058f&DisplayLang=en
the only other choice is to do a in-place upgrade, see:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;306952...
If the domain name is changed during the upgrade you should preoceed like a new domain installation, so you should change the Net-Id, leaving the old domail and joining the new one. You find the wizard from right-clicking on My Computer then Property then the button "Network ID".
Great! never seen! Is your server up tu date with Windows Update? In your place I'll try to apply the Microsoft security rollout pakage and then retry.
You have this message from a special action? Have you imported any policy template (it seems)? If yes is a well known issue but is a dangerous procedure. Please detail the problem. Is your server a PDC? is AD active? How many templates have you imported from mmc policy snap-in?
This warning may origin from a lot of name resolution or kerberos issues depending on your configuration.
This can help:
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b316710
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b263208
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.