A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » Networking
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Vexating workgroup problem



 
 
Thread Tools Display Modes
  #1  
Old September 17th 05, 05:51 AM
Dr. Dos
external usenet poster
 
Posts: n/a
Default Vexating workgroup problem

My workgroup LAN connection keeps disappearing.

I have a three node Win98 LAN.
This is what is happening. With no reason, the workgroup=20
connections stop working. Each machine can no longer find=20
the other machines under My Computer Neighborhood. Each=20
machine, under Network Connections will not ID the name of=20
the workgroup, rather it generates a Windows Explorer dialog=20
error window: =93Unable to browse network. The network is not=20
available.=94 The firewall in each computer is OFF.
However, connections through the hub to the internet are=20
active and working.

Further, when I highlight My Computer Neighborhood in=20
Windows Explorer (file manager), left click file, and left=20
click My Computer Neighborhood, and the chose FIND, I can=20
find each of the networked computers, except instead of the=20
location being the workgroup name, the LOCATION is =93unknown.=94

For more than a year, I have had no problems with my LAN=20
Workgroup. Now each machine, even when disconnected from the=20
network, and therefore free standing,, cannot find its own=20
workgroup name and produces the error: =93Unable to browse=20
network. The network is not available..=94 When all machines=20
are running, I get the same error message and cannot=20
affiliate to the workgroup, although access to the internet=20
is OK. (Therefore, the physical LAN is working)..

AV reports no viruses. I have run spybot and adaware. I am=20
clean.

Network sharing settings have been changed from LMAnnounce=20
(yes) to (no), and Browsemaster from (Automatic) to (No).

Since I have no problems with interacting with the internet,=20
this seems to be a workgroup setup issue.

Can someone say what the correct settings are for the=20
network in Win98 and Win98SE.

Thank you.
  #2  
Old September 17th 05, 11:14 AM
Richard G. Harper
external usenet poster
 
Posts: n/a
Default

To browse a local area network or workgroup you must have at least one
computer running as a browse master. If it's disabled on all of them then
that would be my #1 choice for why it's not working now. It could also be a
firewall issue if you've recently installed one.

--
Richard G. Harper [MVP Shell/User]
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ...
http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Dr. Dos" wrote in message
...
My workgroup LAN connection keeps disappearing.

I have a three node Win98 LAN.
This is what is happening. With no reason, the workgroup
connections stop working. Each machine can no longer find
the other machines under My Computer Neighborhood. Each
machine, under Network Connections will not ID the name of
the workgroup, rather it generates a Windows Explorer dialog
error window: “Unable to browse network. The network is not
available.” The firewall in each computer is OFF.
However, connections through the hub to the internet are
active and working.

Further, when I highlight My Computer Neighborhood in
Windows Explorer (file manager), left click file, and left
click My Computer Neighborhood, and the chose FIND, I can
find each of the networked computers, except instead of the
location being the workgroup name, the LOCATION is “unknown.”

For more than a year, I have had no problems with my LAN
Workgroup. Now each machine, even when disconnected from the
network, and therefore free standing,, cannot find its own
workgroup name and produces the error: “Unable to browse
network. The network is not available..” When all machines
are running, I get the same error message and cannot
affiliate to the workgroup, although access to the internet
is OK. (Therefore, the physical LAN is working)..

AV reports no viruses. I have run spybot and adaware. I am
clean.

Network sharing settings have been changed from LMAnnounce
(yes) to (no), and Browsemaster from (Automatic) to (No).

Since I have no problems with interacting with the internet,
this seems to be a workgroup setup issue.

Can someone say what the correct settings are for the
network in Win98 and Win98SE.

Thank you.


  #3  
Old September 17th 05, 11:14 AM posted to microsoft.public.win98.networking
Richard G. Harper
External Usenet User
 
Posts: 396
Default Vexating workgroup problem

To browse a local area network or workgroup you must have at least one
computer running as a browse master. If it's disabled on all of them then
that would be my #1 choice for why it's not working now. It could also be a
firewall issue if you've recently installed one.

--
Richard G. Harper [MVP Shell/User]
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ...
http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Dr. Dos" wrote in message
...
My workgroup LAN connection keeps disappearing.

I have a three node Win98 LAN.
This is what is happening. With no reason, the workgroup
connections stop working. Each machine can no longer find
the other machines under My Computer Neighborhood. Each
machine, under Network Connections will not ID the name of
the workgroup, rather it generates a Windows Explorer dialog
error window: “Unable to browse network. The network is not
available.” The firewall in each computer is OFF.
However, connections through the hub to the internet are
active and working.

Further, when I highlight My Computer Neighborhood in
Windows Explorer (file manager), left click file, and left
click My Computer Neighborhood, and the chose FIND, I can
find each of the networked computers, except instead of the
location being the workgroup name, the LOCATION is “unknown.”

For more than a year, I have had no problems with my LAN
Workgroup. Now each machine, even when disconnected from the
network, and therefore free standing,, cannot find its own
workgroup name and produces the error: “Unable to browse
network. The network is not available..” When all machines
are running, I get the same error message and cannot
affiliate to the workgroup, although access to the internet
is OK. (Therefore, the physical LAN is working)..

AV reports no viruses. I have run spybot and adaware. I am
clean.

Network sharing settings have been changed from LMAnnounce
(yes) to (no), and Browsemaster from (Automatic) to (No).

Since I have no problems with interacting with the internet,
this seems to be a workgroup setup issue.

Can someone say what the correct settings are for the
network in Win98 and Win98SE.

Thank you.


  #4  
Old September 17th 05, 08:00 PM
Dr. Dos
external usenet poster
 
Posts: n/a
Default

Richard G. Harper wrote:

To browse a local area network or workgroup you must have at least one
computer running as a browse master. If it's disabled on all of them then
that would be my #1 choice for why it's not working now. It could also be a
firewall issue if you've recently installed one.


I have sent all three of my Windows 98 machines to Browse
Master Enabled and LM Announce as yes. Also quick logon. I
have booted with Client for MS Networks and MS Family. But,
these do not solve my problem.

There are four machines running. Their "names" are P-4, P-5,
P-6 and M-7.
P-6 is an XP Pro- SP2 machine.

This is what is happening. When P-5 is booted and not
attached to the network, when using Windows Explorer (file
manager) to view network connections, I get the error
message, "unable to browse network." Therefore P-5 does not
find itself on the network, and it does not find the work
group under "entire network." When I run P-5 attached to the
network, but no other machine is turned on, I get the same
"unable" message. Occasionally P-5 will find itself under
the network, but then if I close file manager, or reboot
with no changes, next time I look, the network is gone. I
cannot reproduce these behaviors, they just happen.

When I run P-4 (network settings are exactly the same as M-7
and P-5), sometimes P-5 will only see P-4 and not itself,
sometimes it will see P-4 and P-5, and sometimes it will not
see the network (unable to browse). This sequence has
happened merely by opening and closing Windows Explorer
(file manager)and/or just expanding and collapsing Network
Neighborhood. Sometimes this happens in reverse. There is no
predicable pattern. Rebooting produces the same
unpredictable experiences.

M-7 acts the same way. Sometimes I get the error when
clicking on network neighborhood "unable to browse." and M-7
does not see itself in the network and does not see the work
group. I have done this when M-7 was disconnected from the
network, connected to the network with no other machines,
and connect when other machines are running.
Clicking/re-clicking on the network neighborhood sometimes
will "suddenly" cause parts of the network to be revealed,
and even the work group will appear under the entire network.

When I integrate the XP machine P-6, it sees all four
computers (P-4, P-5, P-6, M-7) and the work group name,
while M-7 only sees P-6 and the work group name (and not
itself, or P-4 or P-5 which it saw before a simple reboot,
with no changes). P-5 only sees sees P-6 and the work group
name. P-4 sees all four machines, and even on reboot
continued to see all four. After P-4 was rebooted, M-7 and
P-5 saw all four after View Refresh was done (but not before).

The regular directory tree functions of file manager work
for each machine. Each machine, when connected to a router,
has no problems connecting to the internet OR when using the
network neighborhood subroutine from file nn find computer
can find the other computers.

Machines are virus free, etc., and my tests have been done
with AV, etc, applications, all not running. There is no
firewall (ever) on any machine and the firmware firewall in
the router is programed to pass/ignore/not interfere with my
LAN. There have been no (recent) changes to the router. With
the unpredictable experiences on each Win98 machine while it
is not connected to the router, it has to be something with
the OS.

I have uninstalled and reinstalled the network functions on
each machine, and nothing changes, i.e., same quirky behaviors.

This is madness!!!

This minute, al is normal, but ten minutes ago is was messed up.

Again, thanks for your suggestions.
  #5  
Old September 17th 05, 08:00 PM posted to microsoft.public.win98.networking
Dr. Dos[_3_]
external usenet poster
 
Posts: 3
Default Vexating workgroup problem

Richard G. Harper wrote:

To browse a local area network or workgroup you must have at least one
computer running as a browse master. If it's disabled on all of them then
that would be my #1 choice for why it's not working now. It could also be a
firewall issue if you've recently installed one.


I have sent all three of my Windows 98 machines to Browse
Master Enabled and LM Announce as yes. Also quick logon. I
have booted with Client for MS Networks and MS Family. But,
these do not solve my problem.

There are four machines running. Their "names" are P-4, P-5,
P-6 and M-7.
P-6 is an XP Pro- SP2 machine.

This is what is happening. When P-5 is booted and not
attached to the network, when using Windows Explorer (file
manager) to view network connections, I get the error
message, "unable to browse network." Therefore P-5 does not
find itself on the network, and it does not find the work
group under "entire network." When I run P-5 attached to the
network, but no other machine is turned on, I get the same
"unable" message. Occasionally P-5 will find itself under
the network, but then if I close file manager, or reboot
with no changes, next time I look, the network is gone. I
cannot reproduce these behaviors, they just happen.

When I run P-4 (network settings are exactly the same as M-7
and P-5), sometimes P-5 will only see P-4 and not itself,
sometimes it will see P-4 and P-5, and sometimes it will not
see the network (unable to browse). This sequence has
happened merely by opening and closing Windows Explorer
(file manager)and/or just expanding and collapsing Network
Neighborhood. Sometimes this happens in reverse. There is no
predicable pattern. Rebooting produces the same
unpredictable experiences.

M-7 acts the same way. Sometimes I get the error when
clicking on network neighborhood "unable to browse." and M-7
does not see itself in the network and does not see the work
group. I have done this when M-7 was disconnected from the
network, connected to the network with no other machines,
and connect when other machines are running.
Clicking/re-clicking on the network neighborhood sometimes
will "suddenly" cause parts of the network to be revealed,
and even the work group will appear under the entire network.

When I integrate the XP machine P-6, it sees all four
computers (P-4, P-5, P-6, M-7) and the work group name,
while M-7 only sees P-6 and the work group name (and not
itself, or P-4 or P-5 which it saw before a simple reboot,
with no changes). P-5 only sees sees P-6 and the work group
name. P-4 sees all four machines, and even on reboot
continued to see all four. After P-4 was rebooted, M-7 and
P-5 saw all four after View Refresh was done (but not before).

The regular directory tree functions of file manager work
for each machine. Each machine, when connected to a router,
has no problems connecting to the internet OR when using the
network neighborhood subroutine from file nn find computer
can find the other computers.

Machines are virus free, etc., and my tests have been done
with AV, etc, applications, all not running. There is no
firewall (ever) on any machine and the firmware firewall in
the router is programed to pass/ignore/not interfere with my
LAN. There have been no (recent) changes to the router. With
the unpredictable experiences on each Win98 machine while it
is not connected to the router, it has to be something with
the OS.

I have uninstalled and reinstalled the network functions on
each machine, and nothing changes, i.e., same quirky behaviors.

This is madness!!!

This minute, al is normal, but ten minutes ago is was messed up.

Again, thanks for your suggestions.
  #6  
Old September 17th 05, 10:54 PM
PattyL
external usenet poster
 
Posts: n/a
Default

Assuming that the workgroup name has not changed from when this worked and
that it has no spaces in it and is 11 characters or less, I recommend trying
a new hub.

Random behavior like you are describing is often caused by failing hardware.

PattyL


"Dr. Dos" wrote in message
...
Richard G. Harper wrote:

To browse a local area network or workgroup you must have at least one
computer running as a browse master. If it's disabled on all of them
then that would be my #1 choice for why it's not working now. It could
also be a firewall issue if you've recently installed one.


I have sent all three of my Windows 98 machines to Browse Master Enabled
and LM Announce as yes. Also quick logon. I have booted with Client for MS
Networks and MS Family. But, these do not solve my problem.

There are four machines running. Their "names" are P-4, P-5, P-6 and M-7.
P-6 is an XP Pro- SP2 machine.

This is what is happening. When P-5 is booted and not attached to the
network, when using Windows Explorer (file manager) to view network
connections, I get the error message, "unable to browse network."
Therefore P-5 does not find itself on the network, and it does not find
the work group under "entire network." When I run P-5 attached to the
network, but no other machine is turned on, I get the same "unable"
message. Occasionally P-5 will find itself under the network, but then if
I close file manager, or reboot with no changes, next time I look, the
network is gone. I cannot reproduce these behaviors, they just happen.

When I run P-4 (network settings are exactly the same as M-7 and P-5),
sometimes P-5 will only see P-4 and not itself, sometimes it will see P-4
and P-5, and sometimes it will not see the network (unable to browse).
This sequence has happened merely by opening and closing Windows Explorer
(file manager)and/or just expanding and collapsing Network Neighborhood.
Sometimes this happens in reverse. There is no predicable pattern.
Rebooting produces the same unpredictable experiences.

M-7 acts the same way. Sometimes I get the error when clicking on network
neighborhood "unable to browse." and M-7 does not see itself in the
network and does not see the work group. I have done this when M-7 was
disconnected from the network, connected to the network with no other
machines, and connect when other machines are running.
Clicking/re-clicking on the network neighborhood sometimes will "suddenly"
cause parts of the network to be revealed, and even the work group will
appear under the entire network.

When I integrate the XP machine P-6, it sees all four computers (P-4, P-5,
P-6, M-7) and the work group name, while M-7 only sees P-6 and the work
group name (and not itself, or P-4 or P-5 which it saw before a simple
reboot, with no changes). P-5 only sees sees P-6 and the work group name.
P-4 sees all four machines, and even on reboot continued to see all four.
After P-4 was rebooted, M-7 and P-5 saw all four after View Refresh was
done (but not before).

The regular directory tree functions of file manager work for each
machine. Each machine, when connected to a router, has no problems
connecting to the internet OR when using the network neighborhood
subroutine from file nn find computer can find the other computers.

Machines are virus free, etc., and my tests have been done with AV, etc,
applications, all not running. There is no firewall (ever) on any machine
and the firmware firewall in the router is programed to pass/ignore/not
interfere with my LAN. There have been no (recent) changes to the router.
With the unpredictable experiences on each Win98 machine while it is not
connected to the router, it has to be something with the OS.

I have uninstalled and reinstalled the network functions on each machine,
and nothing changes, i.e., same quirky behaviors.

This is madness!!!

This minute, al is normal, but ten minutes ago is was messed up.

Again, thanks for your suggestions.



  #7  
Old September 17th 05, 10:54 PM posted to microsoft.public.win98.networking
PattyL
external usenet poster
 
Posts: 39
Default Vexating workgroup problem

Assuming that the workgroup name has not changed from when this worked and
that it has no spaces in it and is 11 characters or less, I recommend trying
a new hub.

Random behavior like you are describing is often caused by failing hardware.

PattyL


"Dr. Dos" wrote in message
...
Richard G. Harper wrote:

To browse a local area network or workgroup you must have at least one
computer running as a browse master. If it's disabled on all of them
then that would be my #1 choice for why it's not working now. It could
also be a firewall issue if you've recently installed one.


I have sent all three of my Windows 98 machines to Browse Master Enabled
and LM Announce as yes. Also quick logon. I have booted with Client for MS
Networks and MS Family. But, these do not solve my problem.

There are four machines running. Their "names" are P-4, P-5, P-6 and M-7.
P-6 is an XP Pro- SP2 machine.

This is what is happening. When P-5 is booted and not attached to the
network, when using Windows Explorer (file manager) to view network
connections, I get the error message, "unable to browse network."
Therefore P-5 does not find itself on the network, and it does not find
the work group under "entire network." When I run P-5 attached to the
network, but no other machine is turned on, I get the same "unable"
message. Occasionally P-5 will find itself under the network, but then if
I close file manager, or reboot with no changes, next time I look, the
network is gone. I cannot reproduce these behaviors, they just happen.

When I run P-4 (network settings are exactly the same as M-7 and P-5),
sometimes P-5 will only see P-4 and not itself, sometimes it will see P-4
and P-5, and sometimes it will not see the network (unable to browse).
This sequence has happened merely by opening and closing Windows Explorer
(file manager)and/or just expanding and collapsing Network Neighborhood.
Sometimes this happens in reverse. There is no predicable pattern.
Rebooting produces the same unpredictable experiences.

M-7 acts the same way. Sometimes I get the error when clicking on network
neighborhood "unable to browse." and M-7 does not see itself in the
network and does not see the work group. I have done this when M-7 was
disconnected from the network, connected to the network with no other
machines, and connect when other machines are running.
Clicking/re-clicking on the network neighborhood sometimes will "suddenly"
cause parts of the network to be revealed, and even the work group will
appear under the entire network.

When I integrate the XP machine P-6, it sees all four computers (P-4, P-5,
P-6, M-7) and the work group name, while M-7 only sees P-6 and the work
group name (and not itself, or P-4 or P-5 which it saw before a simple
reboot, with no changes). P-5 only sees sees P-6 and the work group name.
P-4 sees all four machines, and even on reboot continued to see all four.
After P-4 was rebooted, M-7 and P-5 saw all four after View Refresh was
done (but not before).

The regular directory tree functions of file manager work for each
machine. Each machine, when connected to a router, has no problems
connecting to the internet OR when using the network neighborhood
subroutine from file nn find computer can find the other computers.

Machines are virus free, etc., and my tests have been done with AV, etc,
applications, all not running. There is no firewall (ever) on any machine
and the firmware firewall in the router is programed to pass/ignore/not
interfere with my LAN. There have been no (recent) changes to the router.
With the unpredictable experiences on each Win98 machine while it is not
connected to the router, it has to be something with the OS.

I have uninstalled and reinstalled the network functions on each machine,
and nothing changes, i.e., same quirky behaviors.

This is madness!!!

This minute, al is normal, but ten minutes ago is was messed up.

Again, thanks for your suggestions.



  #8  
Old September 18th 05, 01:26 AM
Dr. Dos
external usenet poster
 
Posts: n/a
Default

PattyL wrote:

Assuming that the workgroup name has not changed from when this worked and
that it has no spaces in it and is 11 characters or less, I recommend trying
a new hub.

Random behavior like you are describing is often caused by failing hardware.

PattyL


"Dr. Dos" wrote in message
...

Richard G. Harper wrote:


To browse a local area network or workgroup you must have at least one
computer running as a browse master. If it's disabled on all of them
then that would be my #1 choice for why it's not working now. It could
also be a firewall issue if you've recently installed one.


I have sent all three of my Windows 98 machines to Browse Master Enabled
and LM Announce as yes. Also quick logon. I have booted with Client for MS
Networks and MS Family. But, these do not solve my problem.

There are four machines running. Their "names" are P-4, P-5, P-6 and M-7.
P-6 is an XP Pro- SP2 machine.

This is what is happening. When P-5 is booted and not attached to the
network, when using Windows Explorer (file manager) to view network
connections, I get the error message, "unable to browse network."
Therefore P-5 does not find itself on the network, and it does not find
the work group under "entire network." When I run P-5 attached to the
network, but no other machine is turned on, I get the same "unable"
message. Occasionally P-5 will find itself under the network, but then if
I close file manager, or reboot with no changes, next time I look, the
network is gone. I cannot reproduce these behaviors, they just happen.

When I run P-4 (network settings are exactly the same as M-7 and P-5),
sometimes P-5 will only see P-4 and not itself, sometimes it will see P-4
and P-5, and sometimes it will not see the network (unable to browse).
This sequence has happened merely by opening and closing Windows Explorer
(file manager)and/or just expanding and collapsing Network Neighborhood.
Sometimes this happens in reverse. There is no predicable pattern.
Rebooting produces the same unpredictable experiences.

M-7 acts the same way. Sometimes I get the error when clicking on network
neighborhood "unable to browse." and M-7 does not see itself in the
network and does not see the work group. I have done this when M-7 was
disconnected from the network, connected to the network with no other
machines, and connect when other machines are running.
Clicking/re-clicking on the network neighborhood sometimes will "suddenly"
cause parts of the network to be revealed, and even the work group will
appear under the entire network.

When I integrate the XP machine P-6, it sees all four computers (P-4, P-5,
P-6, M-7) and the work group name, while M-7 only sees P-6 and the work
group name (and not itself, or P-4 or P-5 which it saw before a simple
reboot, with no changes). P-5 only sees sees P-6 and the work group name.
P-4 sees all four machines, and even on reboot continued to see all four.
After P-4 was rebooted, M-7 and P-5 saw all four after View Refresh was
done (but not before).

The regular directory tree functions of file manager work for each
machine. Each machine, when connected to a router, has no problems
connecting to the internet OR when using the network neighborhood
subroutine from file nn find computer can find the other computers.

Machines are virus free, etc., and my tests have been done with AV, etc,
applications, all not running. There is no firewall (ever) on any machine
and the firmware firewall in the router is programed to pass/ignore/not
interfere with my LAN. There have been no (recent) changes to the router.
With the unpredictable experiences on each Win98 machine while it is not
connected to the router, it has to be something with the OS.

I have uninstalled and reinstalled the network functions on each machine,
and nothing changes, i.e., same quirky behaviors.

This is madness!!!

This minute, al is normal, but ten minutes ago is was messed up.

Again, thanks for your suggestions.




Thanks PattyL,

Hardware is a thought, especially because of the strange
intermittent experiences, but....

Prior to that time I had a similar experience and replaced a
switching hub and the router, and a WiFi card. Altogether,
this network has been stable (mostly) for six years (XP
excepted).

This happens with each machine, even when each is not
connected to the router (free-standing), and also when only
one (at a time) is turned on and connected to a router. The
work group name is "kosher" in all ways, and the work group
LAN has been working nicely for about nine months.

I have two suspicions: a Windows update to the Win98's or my
AV program (Trend PC-Cillin) messing the registry, even when
not running.

System has been stable for four hours now. I am hoping.....
  #9  
Old September 18th 05, 01:26 AM posted to microsoft.public.win98.networking
Dr. Dos[_3_]
external usenet poster
 
Posts: 3
Default Vexating workgroup problem

PattyL wrote:

Assuming that the workgroup name has not changed from when this worked and
that it has no spaces in it and is 11 characters or less, I recommend trying
a new hub.

Random behavior like you are describing is often caused by failing hardware.

PattyL


"Dr. Dos" wrote in message
...

Richard G. Harper wrote:


To browse a local area network or workgroup you must have at least one
computer running as a browse master. If it's disabled on all of them
then that would be my #1 choice for why it's not working now. It could
also be a firewall issue if you've recently installed one.


I have sent all three of my Windows 98 machines to Browse Master Enabled
and LM Announce as yes. Also quick logon. I have booted with Client for MS
Networks and MS Family. But, these do not solve my problem.

There are four machines running. Their "names" are P-4, P-5, P-6 and M-7.
P-6 is an XP Pro- SP2 machine.

This is what is happening. When P-5 is booted and not attached to the
network, when using Windows Explorer (file manager) to view network
connections, I get the error message, "unable to browse network."
Therefore P-5 does not find itself on the network, and it does not find
the work group under "entire network." When I run P-5 attached to the
network, but no other machine is turned on, I get the same "unable"
message. Occasionally P-5 will find itself under the network, but then if
I close file manager, or reboot with no changes, next time I look, the
network is gone. I cannot reproduce these behaviors, they just happen.

When I run P-4 (network settings are exactly the same as M-7 and P-5),
sometimes P-5 will only see P-4 and not itself, sometimes it will see P-4
and P-5, and sometimes it will not see the network (unable to browse).
This sequence has happened merely by opening and closing Windows Explorer
(file manager)and/or just expanding and collapsing Network Neighborhood.
Sometimes this happens in reverse. There is no predicable pattern.
Rebooting produces the same unpredictable experiences.

M-7 acts the same way. Sometimes I get the error when clicking on network
neighborhood "unable to browse." and M-7 does not see itself in the
network and does not see the work group. I have done this when M-7 was
disconnected from the network, connected to the network with no other
machines, and connect when other machines are running.
Clicking/re-clicking on the network neighborhood sometimes will "suddenly"
cause parts of the network to be revealed, and even the work group will
appear under the entire network.

When I integrate the XP machine P-6, it sees all four computers (P-4, P-5,
P-6, M-7) and the work group name, while M-7 only sees P-6 and the work
group name (and not itself, or P-4 or P-5 which it saw before a simple
reboot, with no changes). P-5 only sees sees P-6 and the work group name.
P-4 sees all four machines, and even on reboot continued to see all four.
After P-4 was rebooted, M-7 and P-5 saw all four after View Refresh was
done (but not before).

The regular directory tree functions of file manager work for each
machine. Each machine, when connected to a router, has no problems
connecting to the internet OR when using the network neighborhood
subroutine from file nn find computer can find the other computers.

Machines are virus free, etc., and my tests have been done with AV, etc,
applications, all not running. There is no firewall (ever) on any machine
and the firmware firewall in the router is programed to pass/ignore/not
interfere with my LAN. There have been no (recent) changes to the router.
With the unpredictable experiences on each Win98 machine while it is not
connected to the router, it has to be something with the OS.

I have uninstalled and reinstalled the network functions on each machine,
and nothing changes, i.e., same quirky behaviors.

This is madness!!!

This minute, al is normal, but ten minutes ago is was messed up.

Again, thanks for your suggestions.




Thanks PattyL,

Hardware is a thought, especially because of the strange
intermittent experiences, but....

Prior to that time I had a similar experience and replaced a
switching hub and the router, and a WiFi card. Altogether,
this network has been stable (mostly) for six years (XP
excepted).

This happens with each machine, even when each is not
connected to the router (free-standing), and also when only
one (at a time) is turned on and connected to a router. The
work group name is "kosher" in all ways, and the work group
LAN has been working nicely for about nine months.

I have two suspicions: a Windows update to the Win98's or my
AV program (Trend PC-Cillin) messing the registry, even when
not running.

System has been stable for four hours now. I am hoping.....
  #10  
Old September 19th 05, 02:38 AM posted to microsoft.public.win98.networking
Dr. Dos[_3_]
external usenet poster
 
Posts: 3
Default Vexating workgroup problem

Richard G. Harper wrote:
To browse a local area network or workgroup you must have at least one
computer running as a browse master. If it's disabled on all of them then
that would be my #1 choice for why it's not working now. It could also be a
firewall issue if you've recently installed one.


Mr. Harper,

I keep reading of similar situations as mine on this NG. I
have followed your advice regarding Browse Master (and also
turned on LM Announce). I also set Client for Microsoft
Networks for quick log-on.

One suggestion I saw here (below in the thread) was to read
MS KB Q258717, and so I did. While my issue is with Win98,
the symptoms are quite similar to what I experience. I do
not use a password for log-on. I use Microsoft Family
Log-on. Is there a way to deal with the user/log-on issue
and still continue to use the automatic log-on feature of
Microsoft Family Log-on?

e
 




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

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Network Login and Connection Problem William B. \(Beau\) Sanders General 1 July 9th 05 09:06 PM
Audio problem and Troubleshooter problem Roger Fink General 35 January 29th 05 09:59 PM
File Sharing+ Workgroup Woo General 15 January 17th 05 12:01 PM
Continued problem with Slow System bgaard General 9 January 13th 05 11:08 PM
Win98 SE Shut Down problem KOBE General 2 January 3rd 05 02:32 AM


All times are GMT +1. The time now is 11:24 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.