XP SP2 - W2K Server problems

[ed baker]

On a W2K domain the ip is as follows

IP 101.101.101.50
SNM 255.255.255.0
Gateway 101.101.101.90 (cable router)
DNS 101.101.101.90

On all workstations running XP Sp1 and fixes -

IP is

IP 101.101.101.x
SNM 255.255.255.0
Gateway 101.101.101.90
DNS 101.101.101.90

all see the domain and run absolutely fine and dandy thank you

XP SP2 is configured exactly the same (auto update from net - AND new
machines too)

they connect to the Domain and when they next log on the domain is
completely inaccessible no shares- printers or anything

ping is fine but dns is not set up on the w2k server so pinging for
server.domainname never did work.

ping for external internet / email names is fine too.

driving me mad - what are the suggested solutions

(other than spending 500 quid on w2003server.

thanks

Ed

[news.rr.com]

I doubt your cable router *really* has Active Directory compatible dns
functionality? Why not just set up DNS (and optionally DHCP) on the win2k
server? Just remember to disable DHCP on the router if you do it on the
server.


"ed baker" > wrote in message
k...
On a W2K domain the ip is as follows

IP 101.101.101.50
SNM 255.255.255.0
Gateway 101.101.101.90 (cable router)
DNS 101.101.101.90

On all workstations running XP Sp1 and fixes -

IP is

IP 101.101.101.x
SNM 255.255.255.0
Gateway 101.101.101.90
DNS 101.101.101.90

all see the domain and run absolutely fine and dandy thank you

XP SP2 is configured exactly the same (auto update from net - AND new
machines too)

they connect to the Domain and when they next log on the domain is
completely inaccessible no shares- printers or anything

ping is fine but dns is not set up on the w2k server so pinging for
server.domainname never did work.

ping for external internet / email names is fine too.

driving me mad - what are the suggested solutions

(other than spending 500 quid on w2003server.

thanks

Ed