Showing results for 
Search instead for 
Do you mean 

Unable to browse the network.

SOLVED
Go to Solution
Esteemed Contributor

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".

However, XP Clients can map network drive by typing: \\dstdcDEV01\dev

they run net use afterwards, and this is displayed:

State Local Remote Network

-----------------------------------------------Disconnected P: \\Dsttrkcluster\Usuarios\jgomez
Microsoft Windows Network

Connected T: \\192.168.91.223\desarrollo Red de Microsoft Windows
Disconnected U: \\dstdcdev01\desarrollo Web Client Network

u: and t: seem to point to different locations.
However, dstdcdev server has only 1 NIC, with 192.168.91.223 IP address shown above.

Anyone has any idea how I can fix this?

regards.
28 REPLIES
Honored Contributor

Re: Unable to browse the network.

Open a command prompt and run the command:

net start

Post the results
Verify that that the workstation service, browser, RPC, netbios over TCP/IP has been started.

It seems that you speak spanish. Asi que el resultado del comando deberia ser como sigue:


Actualizaciones automáticas
Administración de aplicaciones
Administrador de conexión de acceso remoto
Administrador de cuentas de seguridad
Administrador de discos lógicos
Agente de directivas IPSEC
Almacenamiento protegido
CA License Client
Cliente de seguimiento de vinculos distribuidos
Cliente DHCP
Cliente DNS
Cola de impresión
Conexiones de red
Configuración inalámbrica
Estación de trabajo
eTrust Antivirus Job Server
eTrust Antivirus Realtime Server
eTrust Antivirus RPC Server
Event Log Watch
Examinador de equipos
Exten. controlador Instrumental de admon. de Windows
Firewall Client Agent
Horario de Windows
HP Asset Remote Execution Agent
Inicio de sesión en red
Instrumental de administración de Windows
Llamada a procedimiento remoto(RPC)
Medios de almacenamiento extraíbles
Mensajero
Notificación de sucesos del sistema
Plug and Play
Programador de tareas
QoS RSVP
Registro de sucesos
Servicio de ayuda TCP/IP NetBIOS
Servicio de Registro remoto
Servicio de transferencia inteligente en segundo plano
Servicio RunAs
Servidor
Sistema de sucesos de COM+
Telefonía
Unicenter Software Delivery

Se ha completado el comando correctamente.

Verifica que el servidor DNS tiene configurada de forma correcta el registro A y el PTR para el equipo dstdcDEV01.

Verify that the DNS server has configured the appropiate A and PTR resource record for dstdcDEV01.

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

Re: Unable to browse the network.

Thanks Ivan for being there.
It's been over a week now that I'm dealing with this w/o any success...

Yes, I do speak spanish.
This is the result of the net start command.

see attached.

regards.
Honored Contributor

Re: Unable to browse the network.

It seems that the services are ok.

The first thing you should do is this:

http://support.microsoft.com/default.aspx?scid=kb;en-us;170336

Then verify if the computer has no viruses.

Then verify the DNS and WINS configuration.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Honored Contributor

Re: Unable to browse the network.

Sorry, the last microsoft link is for windows NT. Don't use it.

You should verify that you have netbios over TCP/IP enabled on the network adapter.

Did you run the server configuration wizard? All service are disabled until you run IT. You need to enable the file and print server role.

Verify if you don't have enabled the ICF (firewall) on the network properties too.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Honored Contributor

Re: Unable to browse the network.

One more question, if you run from the command prompt:

nbtstat -a server_ip

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

Re: Unable to browse the network.

Ivan,

Just to make sure you understand.

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

Server2 is a DC in DEV.G.com domain
Windows 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.com
But 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 Places
Entire Network
Web Client Network
and 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.
Esteemed Contributor

Re: Unable to browse the network.

BTW,
does anyone know what these folders mean?

_private
Document Library
Image Library
images
Lists
Repositorio SRC
default.aspx

that would help.
regards.
Honored Contributor

Re: Unable to browse the network.

I'm confuse now. First you said:

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".

Now you say:

Server1 can map a network drive at Server2.DEV.G.com without any problem. But the source is not the same.

Asuming that the A and PTR DNS record is right on the DNS server, aren't you having and IP conflict?

The arp -a command displays the same information at the server and the clients?. Or the pathping shows the same information if you are routing?

Are you using distributed file system DFS?

Are the shares published in the Active Directory?

Please tellme if i understood.

The XP clients can connect to \\192.168.91.223 and shows a lists of shares.

Server1 connects to \\192.168.91.223 and see another different list of shares?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Esteemed Contributor

Re: Unable to browse the network.

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


XP clients
net use y: \\dstdcdev01\desarrollo
net use n: \\192.168.91.23\desarrollo
I run net use again and get this:
Conectado N: \\192.168.91.223\desarrollo
Red de Microsoft Windows
Conectado Y: \\dstdcdev01\desarrollo
Web Client Network
You see what I mean?
y: is a Web Client Network resource type
n: is a Microsoft Windows Network resource type

If I connect to n: I only see 1 file
If 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.223
Haciendo 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

I know it may seem weird...
thank you.
Regards.
Honored Contributor

Re: Unable to browse the network.

I think i finally understood.

So, these are my recommendations:

Change the order of network providers
1. 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?
Esteemed Contributor

Re: Unable to browse the network.

Tahnk you.
I was currently going thru the network providers issue.
I didn't want to edit the registry.

So, I tried your first option but I right clic on My Network Places, all I get is shortcut properties.

WebDav extension in IIS was already disabled.
Not sure how to verify virtual folder configuration.

thank you.
regards.
Esteemed Contributor

Re: Unable to browse the network.

I found that under my network places I only have 2:
Windows Locator
DCE Cell Directory service
thank you.
what next?
Honored Contributor

Re: Unable to browse the network.

Lets continue.

The above was for XP clients.

For the server:

Just to be sure, the webdav extension should be disabled on ISS of the "target server", not the "source server" or client.

Verfity that you have the "WebClient service" disabled on the "source server".

The virtual directory configuration you should check on the "target server", in the shared folder properties or IIS. See attached zip file.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Esteemed Contributor

Re: Unable to browse the network.

WebDav extension was already disabled in IIS on both servers.
WebClient service was already disabled on both servers as well.

thank you.
I'm still searching for a solution to this.
I'll let you know any outcome.
Honored Contributor

Re: Unable to browse the network.

If you search for the shared folder on the active directory, do you find it?

If you browse "my network places", then "web client network", do you see something?, delete any site if added.

What if you stop IIS, can you stop it on the tarjet server?

Did you tried with another windows 2003 server, do you get the same results?
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Esteemed Contributor

Re: Unable to browse the network.

Ivan,

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.

thank you.
regards.
Honored Contributor

Re: Unable to browse the network.

You get this error:

"Unable to browse the network.
The network is not present or not started."


Because the web client service is stopped and maybe disabled.

In services, enable the "web client" service and start it, you should be able to browse the network.

When I say can you find if you search in the AD, means that in active directory users and computers, you can create shared folders, and then, these shared folders can be searched.

See:

http://www.microsoft.com/resources/documentation/Windows/XP/all/reskit/en-us/Default.asp?url=/resources/documentation/Windows/XP/all/reskit/en-us/prde_ffs_stbj.asp

Now, do you rally want to access these shared folders via web client network?

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.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Honored Contributor

Re: Unable to browse the network.

Hi Edgar,
at first glance you have a firewall trouble as explained by follow article
http://support.microsoft.com/default.aspx?scid=kb;en-us;298804

Here there are some other help, perhaps you know
http://support.microsoft.com/default.aspx?scid=kb;en-us;325487
http://support.microsoft.com/default.aspx?scid=kb;en-us;323357

Antonio Vigliotti
Antonio Maria Vigliotti
Esteemed Contributor

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.
Esteemed Contributor

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.
Honored Contributor

Re: Unable to browse the network.

Two more questions.

With IIS UP on 192.168.91.223, using a web browser, if you type in the following URL:

http://192.168.91.223/desarrollo

Can you connect?

What is the ouput of:

net view \\192.168.91.223

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

Re: Unable to browse the network.

I type http://192.168.91.223/desarrollo and the URL automatically changes into the following:
http://192.168.91.223/Desarrollo/default.aspx

attached is the right pane of the result:

And this is the output of net view \\192.168.91.223:

D:\Documents and Settings\Administrator>net view \\192.168.91.223
Shared resources at \\192.168.91.223



Share name Type Used as
Comment

-------------------------------------------------------------------------------
DESARROLLO Disk

HPLaserJ Print
HP LaserJet 2200 Series PCL
NETLOGON Disk
Recurso compartido del servidor de inicio de sesión
ramonEZL Disk

SISTEMAS Disk

SYSVOL Disk
Recurso compartido del servidor de inicio de sesión
The command completed successfully.
Honored Contributor

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?
Esteemed Contributor

Re: Unable to browse the network.

I am checking the IIS configuration.

I deleted the desarrollo folder.
from an XP client I am still able to browse one folder named desarrollo at the same server.

You see? My point is it doesn't matter the desarrollo folder is shared or not. The contents are not the same.

Thank you for your support.
This is just a desperating issue.
I'll keep searching.
regards.
//Add this to "OnDomLoad" event