"unable to browse network" error from WIN98 PC to XP PC . . .

"unable to browse network" error from WIN98 PC to XP PC
through gigabit switch (both systems on same segment), but
XP can see both systems in the workgroup. both systems can
browse internet. can find computers through "find
computer". just have network netghborhood icon.

In article <ab8801c488a1$4c3b3f80$(E-Mail Removed)>, "Rick"
<(E-Mail Removed)> wrote:
>"unable to browse network" error from WIN98 PC to XP PC
>through gigabit switch (both systems on same segment), but
>XP can see both systems in the workgroup. both systems can
>browse internet. can find computers through "find
>computer". just have network netghborhood icon.

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 or Start | Shut Down | Close all programs... 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

High but on windows XP I have same problem since updating to SP2 but I do
not have option
in control panel to set share-level access control is selected in Access
Control tab
and all computer users are logged in. There is no problem browsing from the
XP machine to the Windows 98 and ME machines just browsing to XP from the
98/ME.

Any other ideas on correcting this issue would be very much appreciated.
Birderman


"Steve Winograd [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In article <ab8801c488a1$4c3b3f80$(E-Mail Removed)>, "Rick"
> <(E-Mail Removed)> wrote:
> >"unable to browse network" error from WIN98 PC to XP PC
> >through gigabit switch (both systems on same segment), but
> >XP can see both systems in the workgroup. both systems can
> >browse internet. can find computers through "find
> >computer". just have network netghborhood icon.
>
> 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 or Start | Shut Down | Close all programs... 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