Networking Forums

Networking Forums > Computer Networking > Windows Networking > Cannot access entire network from Win98

Reply
Thread Tools Display Modes

Cannot access entire network from Win98

 
 
Ian D. Weatherall
Guest
Posts: n/a

 
      10-21-2004, 08:10 PM
Hello folks,
I have 3 machines seup utilising a dsl connection via a wireles router the 3
machines are like this

pc1 - WinXP Pro SP1 - hard wired
pc2 - Win98SE - hard wired
pc3 - Win98SE Wireless

I recently reinstalled Win98 on pc3 and now when I access the network
neighbourhood, then entire nework I get a message telling me the network
cannot be accessed it
doesn't even show itself as part of the network

I can ping pc1 & pc2 from pc3
When I "Find computer" from pc3 it finds both pc1 & pc2

I can use either pc1 or pc2 to transfer files to pc 3 and vice versa

Each pc has net access without a problem.

I have un/reinstalled each client and made sure the workgroup name is
correct.

I only have tcp/ip as a protocol and client for microsoft networks and file
and printer sharing installed as the clients.

Any thoughts, I hope this is enough infomation

Ian



 
Reply With Quote
 
 
 
 
Carey Holzman
Guest
Posts: n/a

 
      10-21-2004, 11:51 PM
www.careyholzman.com/netfixes.htm

Carey

"Ian D. Weatherall" <(E-Mail Removed)> wrote in message
news:417817a9$1@devmonkey....
> Hello folks,
> I have 3 machines seup utilising a dsl connection via a wireles router the
> 3
> machines are like this
>
> pc1 - WinXP Pro SP1 - hard wired
> pc2 - Win98SE - hard wired
> pc3 - Win98SE Wireless
>
> I recently reinstalled Win98 on pc3 and now when I access the network
> neighbourhood, then entire nework I get a message telling me the network
> cannot be accessed it
> doesn't even show itself as part of the network
>
> I can ping pc1 & pc2 from pc3
> When I "Find computer" from pc3 it finds both pc1 & pc2
>
> I can use either pc1 or pc2 to transfer files to pc 3 and vice versa
>
> Each pc has net access without a problem.
>
> I have un/reinstalled each client and made sure the workgroup name is
> correct.
>
> I only have tcp/ip as a protocol and client for microsoft networks and
> file
> and printer sharing installed as the clients.
>
> Any thoughts, I hope this is enough infomation
>
> Ian
>
>
>



 
Reply With Quote
 
Ian D. Weatherall
Guest
Posts: n/a

 
      10-22-2004, 02:17 AM
Thank you, Carey.
I can only find a reference to my problem with WinME, I have Win98 will it
still work.
Regards,
Ian

"Carey Holzman" <(E-Mail Removed)> wrote in message
news:O$(E-Mail Removed)...
> www.careyholzman.com/netfixes.htm
>
> Carey
>
> "Ian D. Weatherall" <(E-Mail Removed)> wrote in message
> news:417817a9$1@devmonkey....
> > Hello folks,
> > I have 3 machines seup utilising a dsl connection via a wireles router

the
> > 3
> > machines are like this
> >
> > pc1 - WinXP Pro SP1 - hard wired
> > pc2 - Win98SE - hard wired
> > pc3 - Win98SE Wireless
> >
> > I recently reinstalled Win98 on pc3 and now when I access the network
> > neighbourhood, then entire nework I get a message telling me the network
> > cannot be accessed it
> > doesn't even show itself as part of the network
> >
> > I can ping pc1 & pc2 from pc3
> > When I "Find computer" from pc3 it finds both pc1 & pc2
> >
> > I can use either pc1 or pc2 to transfer files to pc 3 and vice versa
> >
> > Each pc has net access without a problem.
> >
> > I have un/reinstalled each client and made sure the workgroup name is
> > correct.
> >
> > I only have tcp/ip as a protocol and client for microsoft networks and
> > file
> > and printer sharing installed as the clients.
> >
> > Any thoughts, I hope this is enough infomation
> >
> > Ian
> >
> >
> >

>
>



 
Reply With Quote
 
Steve Winograd [MVP]
Guest
Posts: n/a

 
      10-22-2004, 08:48 AM
In article <417817a9$1@devmonkey.>, "Ian D. Weatherall"
<(E-Mail Removed)> wrote:
>Hello folks,
>I have 3 machines seup utilising a dsl connection via a wireles router the 3
>machines are like this
>
>pc1 - WinXP Pro SP1 - hard wired
>pc2 - Win98SE - hard wired
>pc3 - Win98SE Wireless
>
>I recently reinstalled Win98 on pc3 and now when I access the network
>neighbourhood, then entire nework I get a message telling me the network
>cannot be accessed it
>doesn't even show itself as part of the network
>
>I can ping pc1 & pc2 from pc3
>When I "Find computer" from pc3 it finds both pc1 & pc2
>
>I can use either pc1 or pc2 to transfer files to pc 3 and vice versa
>
>Each pc has net access without a problem.
>
>I have un/reinstalled each client and made sure the workgroup name is
>correct.
>
>I only have tcp/ip as a protocol and client for microsoft networks and file
>and printer sharing installed as the clients.
>
>Any thoughts, I hope this is enough infomation
>
>Ian


Since "Find computer" and pinging work from pc3, the basic network
settings are right. There's no reason to make any changes in the
network protocols. Some minor problem is preventing pc3 from browsing
in Network Neighborhood.

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 through Find computer" or by typing the other
computer's name in the Start | Run box preceded by two backslash
characters:

\\computer

Since there's a Windows XP computer on the network, it might help to
disable Browse Master on pc3: Control Panel | Network | File and
Printer Sharing | Properties.

If that doesn't help, here are some 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 pc3 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
 
Reply With Quote
 
Ian D. Weatherall
Guest
Posts: n/a

 
      10-27-2004, 04:24 AM
Thank you for the help Steve,
The user logon was the issue, the pc didn't request a login on startup, but
it also wasn't logging on as a user. I logged off then back on and
everything has been great since, even after restarting.
Thanks again.
Ian

"Steve Winograd [MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> In article <417817a9$1@devmonkey.>, "Ian D. Weatherall"
> <(E-Mail Removed)> wrote:
> >Hello folks,
> >I have 3 machines seup utilising a dsl connection via a wireles router

the 3
> >machines are like this
> >
> >pc1 - WinXP Pro SP1 - hard wired
> >pc2 - Win98SE - hard wired
> >pc3 - Win98SE Wireless
> >
> >I recently reinstalled Win98 on pc3 and now when I access the network
> >neighbourhood, then entire nework I get a message telling me the network
> >cannot be accessed it
> >doesn't even show itself as part of the network
> >
> >I can ping pc1 & pc2 from pc3
> >When I "Find computer" from pc3 it finds both pc1 & pc2
> >
> >I can use either pc1 or pc2 to transfer files to pc 3 and vice versa
> >
> >Each pc has net access without a problem.
> >
> >I have un/reinstalled each client and made sure the workgroup name is
> >correct.
> >
> >I only have tcp/ip as a protocol and client for microsoft networks and

file
> >and printer sharing installed as the clients.
> >
> >Any thoughts, I hope this is enough infomation
> >
> >Ian

>
> Since "Find computer" and pinging work from pc3, the basic network
> settings are right. There's no reason to make any changes in the
> network protocols. Some minor problem is preventing pc3 from browsing
> in Network Neighborhood.
>
> 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 through Find computer" or by typing the other
> computer's name in the Start | Run box preceded by two backslash
> characters:
>
> \\computer
>
> Since there's a Windows XP computer on the network, it might help to
> disable Browse Master on pc3: Control Panel | Network | File and
> Printer Sharing | Properties.
>
> If that doesn't help, here are some 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 pc3 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



 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Access Entire network with RRAS in Server 2003 (with vpn) JHO Windows Networking 4 08-26-2005 01:15 AM
Win98 SE cant access network Fred Windows Networking 7 05-06-2005 05:48 PM
Network Access Win98 Mat Windows Networking 0 06-22-2004 12:55 PM
Error message:Unable to access the entire network Scott Windows Networking 3 12-11-2003 04:24 AM
Want access to 'entire network' Windows Networking 2 12-05-2003 05:51 PM



1 2 3 4 5 6 7 8 9 10 11