2003 Server cannot browse network
|
Original Message
|
Name: Thierry
Date: June 22, 2004 at 03:29:22 Pacific
Subject: 2003 Server cannot browse network
OS: 2003 SBS
CPU/Ram: Xeon
|
Comment: We have 2003 servers on 5 sites, and since last week one server cannot browse the network anymore, we get this message :
"xx_domain is not accessible. You may not have permission to use this network resource. Contact the admin of this server to find out if you have access permissions. The list of servers for this workgroup is not currently available".
However, NET USE works fine, ADS replication is OK, WINS & DNS too. TS
Report Offensive Message For Removal
|
|
Response Number 2
|
Name: Thierry
Date: June 22, 2004 at 23:32:45 Pacific
Subject: 2003 Server cannot browse network
|
Reply: (edit)Yes.
Everything worked OK for a month, and then suddenly browsing became impossible.
No changes in security strategies.
I have 4 other servers in the domain and they don't have any problems. Network monitoring tool reveals this : the server asks for a browser backup list and gets a response from the PDC : in the list you see 2 XP stations which are not on the site anymore. Then he asks for a browser election and nobody replies.
 Report Offensive Follow Up For Removal
|
|
Response Number 3
|
Name: ducklips
Date: June 24, 2004 at 11:33:59 Pacific
Subject: 2003 Server cannot browse network |
Reply: (edit)Is that server (the problem server) a domain controller? I ran "dcpromo" on mine and fixed a bunch of problems. As for the two XP systems, you might want to delete those from the server management, under computers - also under sbs computers.
"i woke up this morning and all of my stuff was stolen and replaced with exact duplicates."
Report Offensive Follow Up For Removal
|
|
Response Number 4
|
Name: Thierry
Date: June 30, 2004 at 01:27:13 Pacific
Subject: 2003 Server cannot browse network
|
Reply: (edit)The problem was a WINS conflict. During setup we changed the ip address of the server, and somehow it came back in wins a month later, causing a duplicate entry on the name and two different ip addresses.
After lots of cleaning up and a few reboots everything came back in order.
Thanks for your help Thierry
Report Offensive Follow Up For Removal
|
Use following form to reply to current message:
