In article <BB93DD40-FEDF-4CCD-9EA2-(E-Mail Removed)>,
"Arno" <(E-Mail Removed)> wrote:
>I have seen a few posts here that somewhat resemble the problem I am trying
>to resolve,
>yet none of those solutions work.
>
>Several computers are networked together, and are able to access the other
>computers,
>and also access them via the \\192.168.1.xxx method from Run in Windows 98.
>The only
>exception is the one computer that cannot access any of the others via
>either of these
>methods, yet the other computers can access it. Some of my findings:
>
>Client for MS Networks:
>Only Logon and restore network connections is checked.
>
>File and Print Sharing:
>Browse Master = Automatic (tried setting it to Disabled,
>reboot, back to Automatic, same problem).
>LM Announce = No
>
>NetBeui:
>Both Client for MS Networks and File & Print Sharing are checked.
>Max=10, NCBS=12
>Default protocol option checked (was unchecked, same problem).
>
>TCP/IP uses DHCP for Wins Resolution
>Bindings Client for MS Netowks and File & Print Sharing both checked.
>
>
>Network Card:
>Network Address is not present (problem???),
>Receive Buffer=64k, Link Speed/Duplex=Auto negotiate
>
>Now things start getting stranger ...
>Network Neighborhood -> Only Entire Network is shown.
>Double click -> Unable to browse the network.
>Properties -> Properties for this item are not available.
>
>Accessories -> System Tools -> System Info
>System file checker ran with no problems.
>MSINFO32.EXE loaded OK, went under Components/Network
>and received error Illegal operation, Invalid page fault
>at 0177:0040267e.
>
>Thus on the outside everything looks ok, yet when I get into
>the nitty gritty, something is just not right, and there are
>no friendly messages or troubleshooting hints to explain why.
Unless you have a specific need for NetBEUI, remove it from all
computers and use only TCP/IP on the network. Installing an extra
protocol on even one computer can make network browsing unreliable.
I've written a web page with details:
Windows XP Network Protocols
http://www.practicallynetworked.com/..._protocols.htm
Make sure that NetBIOS over TCP/IP is enabled on all computers, as
shown here:
Enable NetBIOS Over TCP/IP (NetBT)
http://www.practicallynetworked.com/...hoot/netbt.htm
It can take up to 15 minutes after a computer starts up before network
browsing works. During that time, you should be able to access
another computer by typing the other computer's name in the Start |
Run box preceded by two backslash characters:
\\computer
If that doesn't work, here are two common reasons for the inability to
browse the network:
1. The network settings are configured for user-level access control,
which isn't available in a peer-to-peer network. Go to Control Panel
| Network, click the Access Control tab, and make sure that
share-level access control is selected.
2. The user isn't logged on. Is there a logon prompt when Windows 98
starts? If so, don't cancel it. Complete the logon by entering a
user name and, optionally, a password. If there's no logon prompt,
click Start | Log Off and log back on. If that makes network browsing
work properly, the most likely fix is to go to this registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\
Network\Real Mode Net
and delete the value named "AutoLogon", as shown here:
http://www.wown.com/j_helmig/nologon.htm#AutoLogon
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)
Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.
Microsoft Most Valuable Professional - Windows Networking
http://mvp.support.microsoft.com
Steve Winograd's Networking FAQ
http://www.bcmaven.com/networking/faq.htm
Similar Threads
Linear Mode
