G
Gary
Hi,
I have XP Pro connected to a hub. The network also
contains Windows Server 2003 (connected to a cable modem).
As far as I can tell 2003 is configured correctly for DNS
and Routing to allow it to be the gateway to the internet
for other networked machines.
The problems are that XP can't get through to the Web and
Netlogon service won't start so I can't logon to the
domain.
I keep getting error messages saying that the TCP/IP
network service is not working. I tried doing the usual
stack clearing exercises (winsock registry entries, etc),
which got rid of the problem, but then it just came back
again.
I can ping the server using the NetBios name, but not
using machinename.domainname.local.
Both machines can happily communicate and view shared
folders etc.
I'm really at a complete loss.
I did have ZoneAlarm previously installed (from when the
cable modem was plugged into XP) and McAfee Virus Scan is
on there.
How can I fix this mess without reinstalling XP???
Gary
I have XP Pro connected to a hub. The network also
contains Windows Server 2003 (connected to a cable modem).
As far as I can tell 2003 is configured correctly for DNS
and Routing to allow it to be the gateway to the internet
for other networked machines.
The problems are that XP can't get through to the Web and
Netlogon service won't start so I can't logon to the
domain.
I keep getting error messages saying that the TCP/IP
network service is not working. I tried doing the usual
stack clearing exercises (winsock registry entries, etc),
which got rid of the problem, but then it just came back
again.
I can ping the server using the NetBios name, but not
using machinename.domainname.local.
Both machines can happily communicate and view shared
folders etc.
I'm really at a complete loss.
I did have ZoneAlarm previously installed (from when the
cable modem was plugged into XP) and McAfee Virus Scan is
on there.
How can I fix this mess without reinstalling XP???
Gary