- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Networking
- >
- Unable to browse the network.
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-26-2005 08:33 PM
тАО07-26-2005 08:33 PM
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.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2005 10:31 AM
тАО07-28-2005 10:31 AM
Solutionnet 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2005 03:56 AM
тАО08-03-2005 03:56 AM
Re: Unable to browse the network.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2005 07:11 AM
тАО08-03-2005 07:11 AM
Re: Unable to browse the network.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2005 07:20 AM
тАО08-03-2005 07:20 AM
Re: Unable to browse the network.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2005 07:25 AM
тАО08-03-2005 07:25 AM
Re: Unable to browse the network.
nbtstat -a server_ip
What do you get?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2005 09:09 PM
тАО08-03-2005 09:09 PM
Re: Unable to browse the network.
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-03-2005 10:33 PM
тАО08-03-2005 10:33 PM
Re: Unable to browse the network.
does anyone know what these folders mean?
_private
Document Library
Image Library
images
Lists
Repositorio SRC
default.aspx
that would help.
regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2005 01:48 AM
тАО08-04-2005 01:48 AM
Re: Unable to browse the network.
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-04-2005 02:17 AM
тАО08-04-2005 02:17 AM
Re: Unable to browse the network.
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.