Win2K SP3 woes
This is a discussion about Win2K SP3 woes in the Windows Software category; Hi all, I wonder if anyone can shed any light onto a problem i now have after applying SP3 to a server. Since the upgrade I am now nolonger able to resolve host's via DNS at all. The appropriate services are started, and if need bee i can roll back to SP2 however i would rather not do this.
Hi all,
I wonder if anyone can shed any light onto a problem i now have after applying SP3 to a server. Since the upgrade I am now nolonger able to resolve host's via DNS at all. The appropriate services are started, and if need bee i can roll back to SP2 however i would rather not do this. Thi s problem has only come since applying this SP.
Has anyone else experienced this?? Has anyone got any ideas for a fix?
Antony
I wonder if anyone can shed any light onto a problem i now have after applying SP3 to a server. Since the upgrade I am now nolonger able to resolve host's via DNS at all. The appropriate services are started, and if need bee i can roll back to SP2 however i would rather not do this. Thi s problem has only come since applying this SP.
Has anyone else experienced this?? Has anyone got any ideas for a fix?
Antony
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
Responses to this topic
If I remember correctly, there was a very similar problem reported with Win2k SP1 when it first surfaced, and the fix was just to uninstall the TCP/IP protocol and reinstall it. Give that a spin...
tcr 8)
tcr 8)
