Can't access network workgroup

[Guest]

With no known changes to my laptop or company's network ican no longer access
the workgroup. All computers have the same workgroup name and none are
running firewalls. The errors I get when double click "computers near me"or
"Microsoft Windows Network" are "Oem workgroup not accessible. List of
servers for this workgroup unavailable". From other computers "computers near
me"if I click on my computers name I get "Network path not found". Using cmd.
Ican ping any of the other computers by IP address but not by name. The
network is setup using DHCP. I can access the internet with no problems. The
laptop has had no new software installed that might interfere and I have
scanned for viruses.

 

[Phillip Windell]

If you can ping by name then you are not resolving names. The first thing I
always check for when any problem suddenly pops up out of the blue
now-a-days is Spyware/Adware that is perfectly capable to wrecking total
havoc on any machines networking abilities. The ones I trust the most are
Spybot S&D, SpySweeper, and Ad-Aware (in that order).

Once the machine is cleaned up with those, then you have a more clean slate
to troubleshoot from if there are still problems.

 

[Phillip Windell]

I meant, "can *not* ping by name", but you can ping by IP# then you are not
resolving names...ect.

If you can ping by name then you are not resolving names. The first thing I
always check for when any problem suddenly pops up out of the blue
now-a-days is Spyware/Adware that is perfectly capable to wrecking total
havoc on any machines networking abilities. The ones I trust the most are
Spybot S&D, SpySweeper, and Ad-Aware (in that order).

Once the machine is cleaned up with those, then you have a more clean slate
to troubleshoot from if there are still problems.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

With no known changes to my laptop or company's network ican no longer access
the workgroup. All computers have the same workgroup name and none are
running firewalls. The errors I get when double click "computers near me"or
"Microsoft Windows Network" are "Oem workgroup not accessible. List of
servers for this workgroup unavailable". From other computers "computers near
me"if I click on my computers name I get "Network path not found". Using cmd.
Ican ping any of the other computers by IP address but not by name. The
network is setup using DHCP. I can access the internet with no problems. The
laptop has had no new software installed that might interfere and I have
scanned for viruses.

 

[Guest]

I have the same issue and after reading messages here, there are several
people having the same issue, independant of the network scheme. It seems
like a Microsoft flaw or bug. What Microsoft software are you using?

I meant, "can *not* ping by name", but you can ping by IP# then you are not
resolving names...ect.

If you can ping by name then you are not resolving names. The first thing I
always check for when any problem suddenly pops up out of the blue
now-a-days is Spyware/Adware that is perfectly capable to wrecking total
havoc on any machines networking abilities. The ones I trust the most are
Spybot S&D, SpySweeper, and Ad-Aware (in that order).

Once the machine is cleaned up with those, then you have a more clean slate
to troubleshoot from if there are still problems.


--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

With no known changes to my laptop or company's network ican no longer access
the workgroup. All computers have the same workgroup name and none are
running firewalls. The errors I get when double click "computers near me"or
"Microsoft Windows Network" are "Oem workgroup not accessible. List of
servers for this workgroup unavailable". From other computers "computers near
me"if I click on my computers name I get "Network path not found". Using cmd.
Ican ping any of the other computers by IP address but not by name. The
network is setup using DHCP. I can access the internet with no problems. The
laptop has had no new software installed that might interfere and I have
scanned for viruses.

 

[Phillip Windell]

I have the same issue and after reading messages here, there are several
people having the same issue, independant of the network scheme. It seems
like a Microsoft flaw or bug. What Microsoft software are you using?

Many people are also infected to their eyebrowse with spyware and don't know
they are. Spyware does an amazing amount of destruction, some intentional,
some because the Spyware is poorly written.

A lot of similar problems occur with "wireless" networking because of the
security implementations that are used with them. The way they keep
replacing the 802 "specification" with newer ones implies they keep having
problems with the existing ones. What variation are they up to
now?.."g"?,.."h"?,.."j"? Then combine that with the slight proprietary
variations that may exist between vendors,....then combine the firmware
variations on top of that even within a single vendor.

 

[Steven L Umbach]

Try booting into safe mode with networking to see if that works and if it
does you have a startup program/service/driver conflict that can hopefully
be resolved with something like msconfig or autoruns from SysInternals. Also
try to connect to a share using the IP address of the server offering the
share instead of name as in \\xxx.xxx.xxx.xxx\sharename in the runbox. If
that works you have a problem with netbios name resolution. Run Ipconfig
/all on your computer and another working computer that works on the network
to verify that tcp/ip configuration is correct. --- Steve

 

[Guest]

Try booting into safe mode with networking to see if that works and if it
does you have a startup program/service/driver conflict that can hopefully
be resolved with something like msconfig or autoruns from SysInternals. Also
try to connect to a share using the IP address of the server offering the
share instead of name as in \\xxx.xxx.xxx.xxx\sharename in the runbox. If
that works you have a problem with netbios name resolution. Run Ipconfig
/all on your computer and another working computer that works on the network
to verify that tcp/ip configuration is correct. --- Steve

As suggested I ran the Spybot S&D. All settings in ipconfig/all the tcp/ip
configuration were the same.
The one thig that work was the \\xxx.xxx.xxx.xxx\sharename that Steve
suggested. Doing that I can access the non networking laptop from a good
machine and access the good machine from the bad laptop. I did start the
laptop in the safemode with networking but stiil could not get it to work
that way. Any other suggestions?

 

[Guest]

Spybot S&D WAS a good spyware program but is being bought out by someone and
is no longer being updated. you might want to try SpySweeper, as suggested as
a second choice.