Win98 unable to see out

Involved in an offfice situation with 4 networked PC's - 2 x Win98, 1xWinXP Pro and 1xWinXP Home. All connected through a dynalink 5 port hub using cat5 cable with one of the Win98's "owning" a shared printer. When the first XP (home) came on board we ran the networking wizard disk that WinXP told us too and everyone was able to share resources and use the printer. Ditto when the 2nd XP came into the office. Most are using Realtec network adapter cards and the associated drivers

Last night we had to take off the network the non-printer 98 machine and reformat it. I put it back onto the network using the same name and workgroup as before. The two Xp's and the printer Win98 can view and access all files in the "new" 98 machine, however it itself cannot browse the network. We're obtaining IP's automatically with the tcp/ip protocol and the 98's have Netbeui loaded as well. Should I have given it a slightly different name

The "new" 98 machine will not even offer to show the workgroup in Network Neighbourhood, just saying "Unable to browse network". Which also means that it won't load the shared printer. I have loaded the WinXP network wizard onto the "new" 98PC. Now, cause the others can view it, i presume the software, cableing and protocols are okay. Is the network card misconfigured somehow? The 98's are set up for Windows logon and have turned on the file and printer sharing.

This really bugs me as it was working 12 hours earlier. Can anyone *see* what I'm doing wrong ?? Is there some way of forcing the connection? (in plain language please

All help appreciate

W

www.careyholzman.com/netfixes.htm

Carey

"Wayne" <(E-Mail Removed)> wrote in message
news:BA71A32A-713A-4BEA-A087-(E-Mail Removed)...
> Involved in an offfice situation with 4 networked PC's - 2 x Win98,
1xWinXP Pro and 1xWinXP Home. All connected through a dynalink 5 port hub
using cat5 cable with one of the Win98's "owning" a shared printer. When the
first XP (home) came on board we ran the networking wizard disk that WinXP
told us too and everyone was able to share resources and use the printer.
Ditto when the 2nd XP came into the office. Most are using Realtec network
adapter cards and the associated drivers.
>
> Last night we had to take off the network the non-printer 98 machine and
reformat it. I put it back onto the network using the same name and
workgroup as before. The two Xp's and the printer Win98 can view and access
all files in the "new" 98 machine, however it itself cannot browse the
network. We're obtaining IP's automatically with the tcp/ip protocol and the
98's have Netbeui loaded as well. Should I have given it a slightly
different name?
>
> The "new" 98 machine will not even offer to show the workgroup in Network
Neighbourhood, just saying "Unable to browse network". Which also means that
it won't load the shared printer. I have loaded the WinXP network wizard
onto the "new" 98PC. Now, cause the others can view it, i presume the
software, cableing and protocols are okay. Is the network card misconfigured
somehow? The 98's are set up for Windows logon and have turned on the file
and printer sharing.
>
> This really bugs me as it was working 12 hours earlier. Can anyone *see*
what I'm doing wrong ?? Is there some way of forcing the connection? (in
plain language please)
>
> All help appreciated
>
> W.
>
>

In article <BA71A32A-713A-4BEA-A087-(E-Mail Removed)>,
"Wayne" <(E-Mail Removed)> wrote:
>Involved in an offfice situation with 4 networked PC's - 2 x Win98, 1xWinXP
>Pro and 1xWinXP Home. All connected through a dynalink 5 port hub
>using cat5 cable with one of the Win98's "owning" a shared printer.
>When the first XP (home) came on board we ran the networking wizard
>disk that WinXP told us too and everyone was able to share resources
>and use the printer. Ditto when the 2nd XP came into the office. Most are
>using Realtec network adapter cards and the associated drivers.
>
>Last night we had to take off the network the non-printer 98 machine and
>reformat it. I put it back onto the network using the same name and workgroup
>as before. The two Xp's and the printer Win98 can view and access all files in
>the "new" 98 machine, however it itself cannot browse the network. We're
>obtaining IP's automatically with the tcp/ip protocol and the 98's have Netbeui
>loaded as well. Should I have given it a slightly different name?
>
>The "new" 98 machine will not even offer to show the workgroup in Network
>Neighbourhood, just saying "Unable to browse network". Which also means
>that it won't load the shared printer. I have loaded the WinXP network wizard
>onto the "new" 98PC. Now, cause the others can view it, i presume the software,
>cableing and protocols are okay. Is the network card misconfigured somehow?
>The 98's are set up for Windows logon and have turned on the file and printer sharing.
>
>This really bugs me as it was working 12 hours earlier. Can anyone *see* what
>I'm doing wrong ?? Is there some way of forcing the connection? (in plain language please)
>
>All help appreciated
>
>W.

It's very common for a Windows 95/98/Me computer to have problems
browsing the network after a Windows installation. 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

Reboot the computer, log in, and everything should work.
--
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

Steve - you're the man!!.....thank you.

In article <29210FF1-D7FE-4BD4-AEBD-(E-Mail Removed)>,
"Wayne" <(E-Mail Removed)> wrote:
>>>Involved in an offfice situation with 4 networked PC's - 2 x Win98, 1xWinXP
>>>Pro and 1xWinXP Home. All connected through a dynalink 5 port hub
>>>using cat5 cable with one of the Win98's "owning" a shared printer.
>>>When the first XP (home) came on board we ran the networking wizard
>>>disk that WinXP told us too and everyone was able to share resources
>>>and use the printer. Ditto when the 2nd XP came into the office. Most are
>>>using Realtec network adapter cards and the associated drivers.
>>>
>>>Last night we had to take off the network the non-printer 98 machine and
>>>reformat it. I put it back onto the network using the same name and workgroup
>>>as before. The two Xp's and the printer Win98 can view and access all files in
>>>the "new" 98 machine, however it itself cannot browse the network. We're
>>>obtaining IP's automatically with the tcp/ip protocol and the 98's have Netbeui
>>>loaded as well. Should I have given it a slightly different name?
>>>
>>>The "new" 98 machine will not even offer to show the workgroup in Network
>>>Neighbourhood, just saying "Unable to browse network". Which also means
>>>that it won't load the shared printer. I have loaded the WinXP network wizard
>>>onto the "new" 98PC. Now, cause the others can view it, i presume the software,
>>>cableing and protocols are okay. Is the network card misconfigured somehow?
>>>The 98's are set up for Windows logon and have turned on the file and printer sharing.
>>>
>>>This really bugs me as it was working 12 hours earlier. Can anyone *see* what
>>>I'm doing wrong ?? Is there some way of forcing the connection? (in plain language please)
>>>
>>>All help appreciated
>>>
>>>W.
>>
>>It's very common for a Windows 95/98/Me computer to have problems
>>browsing the network after a Windows installation. 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
>>
>>Reboot the computer, log in, and everything should work.
>
>Steve - you're the man!!.....thank you.

You're welcome, Wayne.
--
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

Carey Holzman wrote:
> www.careyholzman.com/netfixes.htm
>
> Carey
>
> "Wayne" <(E-Mail Removed)> wrote in message
> news:BA71A32A-713A-4BEA-A087-(E-Mail Removed)...
>
>>Involved in an offfice situation with 4 networked PC's - 2 x Win98,
>
> 1xWinXP Pro and 1xWinXP Home. All connected through a dynalink 5 port hub
> using cat5 cable with one of the Win98's "owning" a shared printer. When the
> first XP (home) came on board we ran the networking wizard disk that WinXP
> told us too and everyone was able to share resources and use the printer.
> Ditto when the 2nd XP came into the office. Most are using Realtec network
> adapter cards and the associated drivers.
>
>>Last night we had to take off the network the non-printer 98 machine and
>
> reformat it. I put it back onto the network using the same name and
> workgroup as before. The two Xp's and the printer Win98 can view and access
> all files in the "new" 98 machine, however it itself cannot browse the
> network. We're obtaining IP's automatically with the tcp/ip protocol and the
> 98's have Netbeui loaded as well. Should I have given it a slightly
> different name?
>
>>The "new" 98 machine will not even offer to show the workgroup in Network
>
> Neighbourhood, just saying "Unable to browse network". Which also means that
> it won't load the shared printer. I have loaded the WinXP network wizard
> onto the "new" 98PC. Now, cause the others can view it, i presume the
> software, cableing and protocols are okay. Is the network card misconfigured
> somehow? The 98's are set up for Windows logon and have turned on the file
> and printer sharing.
>
>>This really bugs me as it was working 12 hours earlier. Can anyone *see*
>
> what I'm doing wrong ?? Is there some way of forcing the connection? (in
> plain language please)
>
>>All help appreciated
>>
>>W.
>>
>>
>
>
>
Nice.
Thank you, for sharing your experiences with the world.

--

Robert...