Absolute going NUTS! Cannot PING/Browse files folders in Home Network

  • Thread starter Thread starter soum.paul
  • Start date Start date
S

soum.paul

Hi,

I have grown half bald in trying to figure out this problem.

My home network consists of an XP-SP2 machine, which works as the
internet gateway (running DHCP). This then also connects to a hub,
which in turn has an:

iBook,
a Windows XP-SP1,
2 Windows XP Laptops

All the computers can surf the internet. Sometimes I also connect a
wireless router with the hub, to be able to use Airport Extreme. I have
disabled the DHCP in the router.

There are two problems that I am facing:

1. Cannot browse Files and Folders from XP-SP1 (need it badly)

The iBook and other XP laptops can see and browse the files on the
gateway server (which serves as a backup server with huge disk space as
well...), BUT they cannot browse using the hostname, but only the IP
(192.168.0.1). The XP-SP1 desktop, however, cannot even browse using
IP. Its files and folders are not visible to the gateway comp, or any
other computers in the network.

2. Cannot ping anything from XP-SP1 (though other computers can ping
it)

The ping works between all computers except the XP-SP1. Other computers
can ping the XP-SP1 (which has a DHCP assigned IP). XP-SP1 cannot ping
ANYONE... neither gateway or any of the computers. Not even yahoo or
google.

There is no firewall running. The only anti-virus software is AVG, and
that, I believe, doesn't have an internet security component like
Norton.

I have used Browstat.exe

Both on Gateway and XP-SP1, it gives the following message: "Browsing
is NOT active on domain"

I am close to running out of disk space on the XP-SP1 and I need to
backup the folders on the server. Unfortunately, its an editing
machine, and without that functionality, I am kinda screwed.

Can someone help me?

Thanks,
Soum
 
Well, as you can imagine, it gets pretty difficult to diagnose a problem of
this nature via the NG, afterall, it only takes one small configuration
error and you end up w/ lots of problems. Successful diagnosis also depends
on conveying all the relevant information. It would have been helpful, for
example, to see your PC IP configurations (e.g., ipconfig.exe).

However, let's assume this proves difficult to solve, I do have a sort of
temp (perhaps permanent) solution, one I use in desparation when all else
fails.

Nothing stops you from installing NetBEUI on your Window PCs. NetBEUI is
being phased out in leu of TCP/IP, but before MS went ALL TCP/IP, MS
networks relied exclusively on NetBEUI for local network communcations.
TCP/IP was only used as a routeable protocol for OUTSIDE the local network
(e.g., Internet). TCP/IP, technically, is not really necessary for local
network traffic. It's only used as a convenience by MS since it's means
NetBEUI is one less protocol they need to support, hence they've placed
NetBEUI on the path to obscurity. But that doesn't prevent you from
installing NetBEUI anyway, and thereby bypassing all this TCP/IP crap for
what amounts to a local network problem.

Can't remember exactly, but I know on the XP install CD there's a folder
(under Addon or something) where the NetBEUI drivers can be located and
installed. If you do, then your local network can be configured for NetBEUI
and bypass all these TCP/IP hurdles you seem to be facing. NetBEUI is a
heck of a lot simpler to configure, in fact, there's nothing to configure
per se. It's all based on non-routeable NetBIOS broadcasts, which simplies
the process of locating other PCs by name.

Granted, you may eventually find the answer to your TCP/IP based problems,
but if you're desperate for local network communications, this is one such
avenue. Don't underestimate the value of NetBEUI, *many* older Windows
installations (NT, Win98, etc.) still uses NetBEUI for local network access,
it's alive and well in these environments. This phase out of NetBEUI is a
relatively recent change by MS, so many older networks continue to use both
protocols. IOW, we're not really doing anything all that unusual here.

Just something to consider. If it doesn't help, you can always uninstall it
and be no worse off.

Jim
 
Hey Jim,

Thanks for responding and the help.

I have considered installing NetBUI, but I have been hearing so much
about NetBUI related problems, that I tried to keep is simple TCP/IP.
But I guess I will try that option today.

But aside from that, I still wish to figure out this bizarre issue for
just purposes of understanding where I am going wrong -- check this
ipconfig output



Windows IP Configuration



Host Name . . . . . . . . . . . . : mypc
Primary Dns Suffix . . . . . . . : MSHOME.NET
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : MSHOME.NET

Ethernet adapter Local Area Connection 6:

Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : Realtek RTL8139/810x Family
Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-E0-7D-CB-72-97
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.246
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Friday, December 02, 2005
1:40:08 PM
Lease Expires . . . . . . . . . . : Friday, December 09, 2005
1:40:08 PM

----

Someone suggested that I work in safe mode with networking to remove
the possibility of any other program interfereing. So, I am in Safe
Mode, but I still can't see home network, or ping any of the computers.


Another related issue - yesterday I ran an FTP server at the gateway,
and tried uploading using that - gave me speeds of 4-8KBps.

Geez. I am going to give by night if nothing works out... and try
NetBUI instead.

Thanks...

ps: Browstat.exe gave:

Browsing NOT active on Domain

Tracert says timed out. Though it can recognize the gateway's hostname.
Same problem with ping - I DO get yahoo's hostname and IP resolved.. I
just can't ping it.
 
Hey Jim,

Thanks for responding and the help.

I have considered installing NetBUI, but I have been hearing so much
about NetBUI related problems, that I tried to keep is simple TCP/IP.
But I guess I will try that option today.
Click to expand...

Problems? Hmm, not sure what problems you're referring to, but NetBEUI is
about as trouble free as it gets. It's been around for a heck of a long
time. Not aware of any particular problems associated with it. Millions
use it every day.

If nothing else, if you install NetBEUI and still can't communicate, you
KNOW it's not a TCP/IP issue. That's a valuable clue in itself!

Jim
 
Back
Top