connecting to the workgroup, massive problem

S

Shane Jimerfield

I have Windows XP SP2, and I'm having the following
problems. I have both a WiFi and LAN card. These problems
happen with both.

1) When I click "Show workgroup computers" i get "CBDNET
is not accessible. You may not have permission to use
this network resource. The list of servers for this
workgroup is not currently available."

2) When I run "Net View" from the command prompt i
get "System error 6118 has occurred. The list of servers
for this workgroup is not currently available"

3) If i run "Net View \\primus" I get "System error 53
has occurred. The network path was not found."

4) If i run "Net view \\192.168.4.242" (which is the IP
for primus then it works) then it shows me the resources.

5) If I ping Primus i get "Ping request could not find
host primus. Please check the name and try again."

6) If i ping 192.168.4.242 then it works.


Here are few things I've done:

1) I've made sure that NETBIOS over TCP/IP is enabled.

2) I've added the following exceptions in Widows Firewall
TCP and UDP for ports 136-139 both incoming and outgoing.

3) I've renamed the computer.

4) I've checked to see that all machines are on the same
workgroup, "CBDNET"

5) I've tried disableling the firewall.

6) I've checked to see that the "COmputer Browser"
service is running.

7) I've flushed DNS

8) I've run "netsh int ip reset reset.txt"

9) I've run "netsh winsock reset catalog"

The only thing that I'm not sure about are duplicates of
NETBIOS names. If a computer has two connections one
wired and wireless can that cause NETBIOS problems?

Any help would be great!

Shane
 
T

Tony Allen

Read up on using nbstat from a command prompt. Or - just enter it at the
prompt and it'll list all the switches and what they do.
 
R

Ron Lowe

1) I've made sure that NETBIOS over TCP/IP is enabled.
3) If i run "Net View \\primus" I get "System error 53
has occurred. The network path was not found."

4) If i run "Net view \\192.168.4.242" (which is the IP
for primus then it works) then it shows me the resources.

5) If I ping Primus i get "Ping request could not find
host primus. Please check the name and try again."

6) If i ping 192.168.4.242 then it works.
Click to expand...



Sure sounds like a NetBIOS name resolution problem.

What does an IPCONFOG /ALL report the Node Type as?
 
R

Ron Lowe

What does an IPCONFOG /ALL report the Node Type as?
^^^^^^^^^^^
IPCONFIG /ALL

Typo, obviously.
My Typong stonks.
 
T

Tony Allen

I thought the "O" was intentional - since a lot of us seem in the 'fog' on
similar issues. : )
 
K

Ken J

Ulysses & Tony,

I had the same problem! I also looked through posts and tried various
suggestions. I have XP SP2 on one end of my home network and Win98 on the
other. I could ping IP addresses but not names. Could not see shares.

Here's how I solved the problem. It's a workaround. Microsoft seems
committed to TCP/IP, but IPX can be used for local networks just fine. I
added the IPX/SPX protocol to both machines. I also made sure that NetBIOS
was added for the IPX on both machines. Then I went into the IPX/SPX
properties, advanced tab, and I set the frame type to 802.2 on both
machines. You could also use 802.3 on both, but they must be the same. I
rebooted and my local shares came up just fine!

Give this a try.

Ken
 
C

Chuck

peer-peer

shane
Click to expand...

Shane,

If you don't have a WINS server, that is one of your problems.

Here are Microsoft article discussing node types:
<http://support.microsoft.com/?id=314053>
<http://support.microsoft.com/?id=160177>

To correct this, you'll need to run the Registry Editor on My_Computer.

You need to find this key:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters]
and delete these two values (which ever is there):
NodeType
DhcpNodeType

After you delete the two values, reboot the computer. After the reboot, rerun
IPConfig and post the results.

Cheers,
Chuck
Paranoia comes from experience - and is not necessarily a bad thing.
 
D

Doug Sherman [MVP]

"2) I've added the following exceptions in Widows Firewall
TCP and UDP for ports 136-139 both incoming and outgoing."

This is not enough - you also need to open:

TCP 445; UDP 445

"If a computer has two connections one
wired and wireless can that cause NETBIOS problems?"

Yes. Disable one of these connections and reboot.

Doug Sherman

MCSE Win2k/NT4.0, MCSA, MCP+I, MVP
 
R

Ron Lowe

5) If I ping Primus i get "Ping request could not find
peer-peer
Click to expand...


That's the problem.

In this case, go to Start | Run | regedit.
Go to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters

If either of the following values are present, delete them:

NodeType;
DhcpNodeType.

Then Re-boot.

This should cause the node type to default correctly.
( the node type will report as 'Unknown' in the default case. )

For futher details, see this article:
Default Node Type for Microsoft Clients
http://support.microsoft.com/default.aspx?scid=kb;en-us;160177
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Workgroup connecting 2
Workgroup connectivity 4
cannot ping and access from some pc in workgroup 3
Workgroup Is Not Accessible. You May Not Have Permission .... 6
Home networking 2
XP Pro PC Not Accessible Within Workgroup 1
A very strange workgroup problem 3
Can't ping SOME computers on XP workgroup 3

Top