- Dec 5, 2004
- 55
- 0
- 0
After some googling I narrowed it down to DNS problem. The solution offered by people was to manually set primary DNS address on clients to DC's IP and secondary to DSL/Cable ISP Primary DNS IP. That is assuming DC is running DNS server. The one I am talking about is not yet.
Now, folks that I am helping to set up Server 2003 R2, (I am new at this but gotta learn) run of building's T1, and they are sitting on 192.168.29.x subnet with about 7 XP machines (2 Home unfortunately). The server itself is getting dynamic IP, so obviously every time I try to start setting up DNS server it urges me to assigns static IP because of the know reasons, but I can not do that. Should I just go ahead and set up DNS server anyways?
So far the errors are random but happend a least couple times a day. I really don't want every client to log on and off few times a day to fix this annoying issue. Help would be really appreciated. Thank you.
Now, folks that I am helping to set up Server 2003 R2, (I am new at this but gotta learn) run of building's T1, and they are sitting on 192.168.29.x subnet with about 7 XP machines (2 Home unfortunately). The server itself is getting dynamic IP, so obviously every time I try to start setting up DNS server it urges me to assigns static IP because of the know reasons, but I can not do that. Should I just go ahead and set up DNS server anyways?
So far the errors are random but happend a least couple times a day. I really don't want every client to log on and off few times a day to fix this annoying issue. Help would be really appreciated. Thank you.