WIN XP Pro unable to browse Win 2003 domain

Server: Win Srv 2003 Std Ed.
Workstation: Win XP Pro
Network Protocals: TCP/IP
all software updates have been applied.
Connectivity: Workstation and server are directly
connected to the same hub
3' apart.
ICF is OFF
This is an internal network

Server configured with AD, DHCP, DNS, WINS, NetBIOS
enabled via DHCP.
The Server can ping the workstation and the workstation
can ping the server.
The server does show the Master Browser is active.
Server Options 046 WINS is installed and configured.

The workstation can login to the server without issue as
a network admin as well as a user.

The server does show that the workstation is logged in
and IP addressing has been passed to the workstation.

Problem: When attempting to browse the network from My
Network Places,Entire Network, Microsoft Windows Network,
an icon displays representing the domain that the
workstation is logged into. However clicking on the domain
icon only returns an error box indicating "The list of
servers for this workgroup is not currently available.
You might not have permission to use this network
resource."

This error msg appears no matter who I am logged into the
network as. I see no Group Policy issue.

Searching the network for the server "Eagle1" gets a good
return and shows that Eagle1 is on the domain. I am then
able to click on the Eagle1 server icon and access the
shared folders and devices.

According to what I have been able to source on the
problem including Microsofts' knowledge base and other
tech websites. This problem has been documented
with Win Srv 2000, NT, Win XP Pro clients, and downlevel
clients. In the case of downlevel clients the problem is
asscociated with WINS and NETBIOS. In cases of XP the
problem has been associated with ICF and Print and File
sharing not being installed/enabled. I have as a matter
of course looked at this area just to make sure that they
are not the problem source although WINS is not used by
XP. And I have uninstalled and reinstalled print and file
sharing on the workstation.

Any thoughts on this issue would be greatly appreciated.
In order for my critical application to work, this
problem needs to be solved.

Thanks in advance.

Not sure if you've already looked at this, but make sure you have no
external IP addresses in any server or computer's DNS config settings. All
servers and workstations should specify *only* the internal AD-integrated
DNS server's IP address in their network settings. The AD-integrated DNS
server should be set up with forwarders to your ISP's DNS servers for
external resolution. See
http://support.microsoft.com/default...b;en-us;300202 for more
info.

If that's already the case, post back...

Don wrote:
> Server: Win Srv 2003 Std Ed.
> Workstation: Win XP Pro
> Network Protocals: TCP/IP
> all software updates have been applied.
> Connectivity: Workstation and server are directly
> connected to the same hub
> 3' apart.
> ICF is OFF
> This is an internal network
>
> Server configured with AD, DHCP, DNS, WINS, NetBIOS
> enabled via DHCP.
> The Server can ping the workstation and the workstation
> can ping the server.
> The server does show the Master Browser is active.
> Server Options 046 WINS is installed and configured.
>
> The workstation can login to the server without issue as
> a network admin as well as a user.
>
> The server does show that the workstation is logged in
> and IP addressing has been passed to the workstation.
>
> Problem: When attempting to browse the network from My
> Network Places,Entire Network, Microsoft Windows Network,
> an icon displays representing the domain that the
> workstation is logged into. However clicking on the domain
> icon only returns an error box indicating "The list of
> servers for this workgroup is not currently available.
> You might not have permission to use this network
> resource."
>
> This error msg appears no matter who I am logged into the
> network as. I see no Group Policy issue.
>
> Searching the network for the server "Eagle1" gets a good
> return and shows that Eagle1 is on the domain. I am then
> able to click on the Eagle1 server icon and access the
> shared folders and devices.
>
> According to what I have been able to source on the
> problem including Microsofts' knowledge base and other
> tech websites. This problem has been documented
> with Win Srv 2000, NT, Win XP Pro clients, and downlevel
> clients. In the case of downlevel clients the problem is
> asscociated with WINS and NETBIOS. In cases of XP the
> problem has been associated with ICF and Print and File
> sharing not being installed/enabled. I have as a matter
> of course looked at this area just to make sure that they
> are not the problem source although WINS is not used by
> XP. And I have uninstalled and reinstalled print and file
> sharing on the workstation.
>
> Any thoughts on this issue would be greatly appreciated.
> In order for my critical application to work, this
> problem needs to be solved.
>
> Thanks in advance.

Thanks for the thoughts.

I've taken a look at the KB article and found nothing out
of line. For clarification I only indicated that "Server
Options" under DHCP had 046 installed. This was actually
under Scope Options.

Notwithstanding I now have installed under Scope Options
and Server Options the following with the same values:
003 Router
004 Time Server
006 DNS Servers
015 DND Domain Name
044 WINS/NBNS Servers
045 NETBIOS over TCP/IP NBDD
046 WINS/NBT Node Type as 0x8

There are no external IP addresses configured under DHCP
or DNS with the exception of "Forwarding" which
references my ISP.

The actual msg that appears is: "domain name" is not
accessable. You might not have permission to use this
network resource. Contact the administrator of this
server to find out if you have access permissions.

The list of servers for this workgroup is currently not
available."

With that said, I keep keying on the term workgroup in
the last sentence. I don't recall any "workgroup" field
on the server like you have in a non-domain environment.
However there is a workgroup field on the workstation. I
have attempted to leave this field blank but it will not
let me even though the workstation is setup for the
domain.

Any other thoughts would be appreciated.
Thanks again.

>-----Original Message-----
>Not sure if you've already looked at this, but make sure
you have no
>external IP addresses in any server or computer's DNS
config settings. All
>servers and workstations should specify *only* the
internal AD-integrated
>DNS server's IP address in their network settings. The
AD-integrated DNS
>server should be set up with forwarders to your ISP's
DNS servers for
>external resolution. See
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;300202 for more
>info.
>
>If that's already the case, post back...
>
>Don wrote:
>> Server: Win Srv 2003 Std Ed.
>> Workstation: Win XP Pro
>> Network Protocals: TCP/IP
>> all software updates have been applied.
>> Connectivity: Workstation and server are directly
>> connected to the same hub
>> 3' apart.
>> ICF is OFF
>> This is an internal network
>>
>> Server configured with AD, DHCP, DNS, WINS, NetBIOS
>> enabled via DHCP.
>> The Server can ping the workstation and the workstation
>> can ping the server.
>> The server does show the Master Browser is active.
>> Server Options 046 WINS is installed and configured.
>>
>> The workstation can login to the server without issue
as
>> a network admin as well as a user.
>>
>> The server does show that the workstation is logged in
>> and IP addressing has been passed to the workstation.
>>
>> Problem: When attempting to browse the network from My
>> Network Places,Entire Network, Microsoft Windows
Network,
>> an icon displays representing the domain that the
>> workstation is logged into. However clicking on the
domain
>> icon only returns an error box indicating "The list of
>> servers for this workgroup is not currently available.
>> You might not have permission to use this network
>> resource."
>>
>> This error msg appears no matter who I am logged into
the
>> network as. I see no Group Policy issue.
>>
>> Searching the network for the server "Eagle1" gets a
good
>> return and shows that Eagle1 is on the domain. I am
then
>> able to click on the Eagle1 server icon and access the
>> shared folders and devices.
>>
>> According to what I have been able to source on the
>> problem including Microsofts' knowledge base and other
>> tech websites. This problem has been documented
>> with Win Srv 2000, NT, Win XP Pro clients, and
downlevel
>> clients. In the case of downlevel clients the problem
is
>> asscociated with WINS and NETBIOS. In cases of XP the
>> problem has been associated with ICF and Print and File
>> sharing not being installed/enabled. I have as a matter
>> of course looked at this area just to make sure that
they
>> are not the problem source although WINS is not used by
>> XP. And I have uninstalled and reinstalled print and
file
>> sharing on the workstation.
>>
>> Any thoughts on this issue would be greatly
appreciated.
>> In order for my critical application to work, this
>> problem needs to be solved.
>>
>> Thanks in advance.
>
>
>.
>

My mistake on the workstation having a "workgroup" field.
I must be loosing it.

Any way any more thoughts on this would be appreciated.
Don
>-----Original Message-----
>Thanks for the thoughts.
>
>I've taken a look at the KB article and found nothing
out
>of line. For clarification I only indicated that "Server
>Options" under DHCP had 046 installed. This was actually
>under Scope Options.
>
>Notwithstanding I now have installed under Scope Options
>and Server Options the following with the same values:
>003 Router
>004 Time Server
>006 DNS Servers
>015 DND Domain Name
>044 WINS/NBNS Servers
>045 NETBIOS over TCP/IP NBDD
>046 WINS/NBT Node Type as 0x8
>
>There are no external IP addresses configured under DHCP
>or DNS with the exception of "Forwarding" which
>references my ISP.
>
>The actual msg that appears is: "domain name" is not
>accessable. You might not have permission to use this
>network resource. Contact the administrator of this
>server to find out if you have access permissions.
>
>The list of servers for this workgroup is currently not
>available."
>
>With that said, I keep keying on the term workgroup in
>the last sentence. I don't recall any "workgroup" field
>on the server like you have in a non-domain environment.
>However there is a workgroup field on the workstation. I
>have attempted to leave this field blank but it will not
>let me even though the workstation is setup for the
>domain.
>
>Any other thoughts would be appreciated.
>Thanks again.
>
>>-----Original Message-----
>>Not sure if you've already looked at this, but make
sure
>you have no
>>external IP addresses in any server or computer's DNS
>config settings. All
>>servers and workstations should specify *only* the
>internal AD-integrated
>>DNS server's IP address in their network settings. The
>AD-integrated DNS
>>server should be set up with forwarders to your ISP's
>DNS servers for
>>external resolution. See
>>http://support.microsoft.com/default.aspx?scid=kb;en-
>us;300202 for more
>>info.
>>
>>If that's already the case, post back...
>>
>>Don wrote:
>>> Server: Win Srv 2003 Std Ed.
>>> Workstation: Win XP Pro
>>> Network Protocals: TCP/IP
>>> all software updates have been applied.
>>> Connectivity: Workstation and server are directly
>>> connected to the same hub
>>> 3' apart.
>>> ICF is OFF
>>> This is an internal network
>>>
>>> Server configured with AD, DHCP, DNS, WINS, NetBIOS
>>> enabled via DHCP.
>>> The Server can ping the workstation and the
workstation
>>> can ping the server.
>>> The server does show the Master Browser is active.
>>> Server Options 046 WINS is installed and configured.
>>>
>>> The workstation can login to the server without issue
>as
>>> a network admin as well as a user.
>>>
>>> The server does show that the workstation is logged in
>>> and IP addressing has been passed to the workstation.
>>>
>>> Problem: When attempting to browse the network from My
>>> Network Places,Entire Network, Microsoft Windows
>Network,
>>> an icon displays representing the domain that the
>>> workstation is logged into. However clicking on the
>domain
>>> icon only returns an error box indicating "The list of
>>> servers for this workgroup is not currently available.
>>> You might not have permission to use this network
>>> resource."
>>>
>>> This error msg appears no matter who I am logged into
>the
>>> network as. I see no Group Policy issue.
>>>
>>> Searching the network for the server "Eagle1" gets a
>good
>>> return and shows that Eagle1 is on the domain. I am
>then
>>> able to click on the Eagle1 server icon and access the
>>> shared folders and devices.
>>>
>>> According to what I have been able to source on the
>>> problem including Microsofts' knowledge base and other
>>> tech websites. This problem has been documented
>>> with Win Srv 2000, NT, Win XP Pro clients, and
>downlevel
>>> clients. In the case of downlevel clients the problem
>is
>>> asscociated with WINS and NETBIOS. In cases of XP the
>>> problem has been associated with ICF and Print and
File
>>> sharing not being installed/enabled. I have as a
matter
>>> of course looked at this area just to make sure that
>they
>>> are not the problem source although WINS is not used
by
>>> XP. And I have uninstalled and reinstalled print and
>file
>>> sharing on the workstation.
>>>
>>> Any thoughts on this issue would be greatly
>appreciated.
>>> In order for my critical application to work, this
>>> problem needs to be solved.
>>>
>>> Thanks in advance.
>>
>>
>>.
>>
>.
>