Unable to browse the network.

Hi,We have a Windows Server 2003 Standard Ed.Whenever I clic on Web Client Network under My Network Places, a message shows up that reads: "Unable to browse the network. The network is not present or not started".

Re: Unable to browse the network.

Server1 is a Member Server in HDQ.G.com domain. Windows Server 2003 Enterprise no SPs.

Server2 is a DC in DEV.G.com domainWindows Server 2003 Standard SP1

Both servers settings use the same local DNS server in our LAN. (which is a DC in HDQ.G.com)

XP clients in HDQ.G.com can connect to the resource at Server2.DEV.G.comBut Server1.HDQ.G.com cannot reach the resource at Server2.DEV.G.com

The thing is, Server1 can map a network drive at Server2.DEV.G.com without any problem. But the source is not the same.XP clients click on the following:My Network PlacesEntire NetworkWeb Client Networkand there it is: Server2 plus several resources (folders). XP Clients can connect to any of these resources.

These resources are not even similar to the resources listed from Server1.

XP Clients see the following subfolders under almost any of the folders listed under the server2 in Web Client Network.

In response to your questions:

- DNS, both servers have the same DNS set.- File & Print server role was already enabled at server2- NetBIOS over TCP/IP was already set at Server1- MCAfee VirusScan Enterprise is totally up to date and reports no viruses.- ICF is not enabled at neither Server1 nor Server2- See attached the result of running the nbtstat -a Servername command

Thank you and regards.

I have been thinking this may have something to do with WEBDAV. Not sure though.I'm still searching.

Re: Unable to browse the network.

Yes, you are a little bit confused.However, this issue is confusing in itself.

XP clientsnet use y: \\dstdcdev01\desarrollonet use n: \\192.168.91.23\desarrolloI run net use again and get this:Conectado N: \\192.168.91.223\desarrolloRed de Microsoft WindowsConectado Y: \\dstdcdev01\desarrollo Web Client NetworkYou see what I mean? y: is a Web Client Network resource typen: is a Microsoft Windows Network resource type

If I connect to n: I only see 1 fileIf I connect to y: I see a whole different list of files and folders.

I am serious, If I run netstat -n this is all I get related to 192.168.91.223: Proto DirecciÃ³n local DirecciÃ³n remota Estado TCP 192.168.91.62:1331 192.168.91.223:445 ESTABLISHED

If I run ping -a I get this:C:\>ping -a 192.168.91.223Haciendo ping a dstdcdev01.dev.grupodetector.com [192.168.91.223] con 32 bytes de datos:

What I meant before is this: I can connect from server1 to a shared folder even as XP clients connect to a Microsoft Windows Network resource type.I can either net use \\dstdcdev01\desarrollo or net use \\192.168.91.223\desarrollo and I will end up at the same location as above XP client ended up with the n: regardless of whether I use IPaddress or servername

Re: Unable to browse the network.

I think i finally understood.

So, these are my recommendations:

Change the order of network providers1. On the desktop, right-click My Network Places, and then click Properties. 2. On the Advanced menu, click Advanced Settings. 3. On the Provider Order tab, in the Network Providers list, click Web Client Network. 4. Press DOWN ARROW so that Web Client Network is the last provider in the list, and then click OK.

Alternatively, you can change the network provider order in the registry. The registry entry is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkProvider\Order\ProviderOrder. The default value of this entry is Microsoft Windows Network,RDPNP,LanmanWorkstation,WebClient.

You can also disable the webdav extension on the IIS server. Verify that the virtual folder configuration is correct.

Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?

Re: Unable to browse the network.

I don't get what you mean by "If you search for the shared folder on the active directory, do you find it?"

I did stop IIS on target server.And after that, XP clients could not browse anything under Web Client Network.Obviously, the W2k3 server douldn't either.

Before that,The Windows Server 2003 cannot browse anything under Web Client Network because a message pops up saying: "Unable to browse the network. The network is not present or not started.For mor information, click Help."

Which I have done several times. But nothing comes up.

XP clients were able to browse Web Client Network resources once I started the WWW Publishing Service.But, not the W2k3.

BTW, We can not try with any other W2k3 server.We only have 2. target and the one with problems.

Re: Unable to browse the network.

I apreciate your efforts in helping me withi this issue.However, none of the proposed solutions worked it out.

There is a change in behaviour however. This is more desperating though.

After starting webclient service, I could finally click on Web Client Network without getting the message "Unable to browse..."There was nothing, no hosts in the Web Client Network.After a while, target server showed up under Web Client Network.I could browse the server and found the folder I expected but again the contents were the same as if I used net use + UNC syntax.I tried with the IP address just in case. Same result.I'll keep searching...regards.

Re: Unable to browse the network.

Ivan,This was a good question you asked.

<Even with IIS down, you should be able to access the shared folder using standard UNC. If you can't then the shared folder is not shared.>>

I don't know whether or not I want to access these FOLDERS (don't know if they are shared) via web client network.All I know is XP clients can net use UNC and get to find what I need to do from the server.When I run "net use" from any of the XP clients, I see the target folder is a Web Client Network resource type. remember?see attached.

Re: Unable to browse the network.

From the ouput i get two conclusions:

1 - The desarrollo directory is shared, like any other share.

2 - There is a missconfiguration on the IIS, maybe a virtual directory (a.k.a. webdav folder of web folder), if you delete o reconfigure the Desarrollo virtual directory on IIS (192.168.91.223), the problem should be fixed.

Attached is a sample of a virtual directory configuration on IIS. This configuration allows the access through webdav and web browser, like you have. But, in your configuration there is something wrong, i thing that the virtual directory Desarrollo is not pointing to the desarrollo directory.

Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?