Workgroup Frustration - Please Help!

[Dave]

I have a Windows XP Professional box with SP1a and all updates and patches
with the XP built-in firewall turned OFF, and fast user switching is
enabled.
The XP box has been setup and configured to run in a workgroup in a business
setting.
I also have a Windows 2000 Professional box with SP4 and all updates and
patches applied.
Both machines are in the same workgroup.
Both machines get to the internet just fine with no problems at all.
Identical accounts with identical passwords are on both machines.
There is no software firewall on either machine.
These boxes are networked with a Linksys firewall/router.
The XP box connects to the 2000 box with no problems at all. It pings the
netbios name AND the IP address just fine. It is seen it My Network Places,
and connects from Start>Run>\\{netbiosname}C$
The problem is when the 2000 box attempts to connect with the XP box. It
pings the netbios name and IP address just fine. It appears in "My Network
Places", but when you try to click on it in "My Network Places" you get the
error \\{netbios name} is not accessible. Logon failure: user account
restriction.
Also when the 2000 box attempts to connect to the XP box via
Start>Run>\\{netbios name}it gets the same error as just listed above.


Any thoughts?

 

[Roland Hall]

Hey Dave...

Perhaps Start>Run>\\{netbiosname}C$ is \\computername\c$ ??? (computername
== NetBIOS name)
You get this error: Logon failure: user account restriction.

Sounds to me like the user account on the XP is restricted from
Administrative share access. c$ is a built-in administrative share and
administrative credentials are required. If the user account does not have
Administrative rights assigned, you can't get there from here.

Roland

I have a Windows XP Professional box with SP1a and all updates and patches
with the XP built-in firewall turned OFF, and fast user switching is
enabled.
The XP box has been setup and configured to run in a workgroup in a business
setting.
I also have a Windows 2000 Professional box with SP4 and all updates and
patches applied.
Both machines are in the same workgroup.
Both machines get to the internet just fine with no problems at all.
Identical accounts with identical passwords are on both machines.
There is no software firewall on either machine.
These boxes are networked with a Linksys firewall/router.
The XP box connects to the 2000 box with no problems at all. It pings the
netbios name AND the IP address just fine. It is seen it My Network Places,
and connects from Start>Run>\\{netbiosname}C$
The problem is when the 2000 box attempts to connect with the XP box. It
pings the netbios name and IP address just fine. It appears in "My Network
Places", but when you try to click on it in "My Network Places" you get the
error \\{netbios name} is not accessible. Logon failure: user account
restriction.
Also when the 2000 box attempts to connect to the XP box via
Start>Run>\\{netbios name}it gets the same error as just listed above.


Any thoughts?

 

[Dave]

Yes, it does have administrative rights. I have even tried logged in as
Administrator on both machines

 

[Colon Terminus]

Hi Dave,

As you've discovered, simple networking is not so simple with an XP box.
They took something that was close to perfect in Windows 2000 and pretty
much broke it in XP.

At a command prompt on the XP box type "ipconfig /all" without the
quotes, of course. What do you see as "Node Type"?

 

[Dave]

Node type: "Unknown"

Hi Dave,

As you've discovered, simple networking is not so simple with an XP box.
They took something that was close to perfect in Windows 2000 and pretty
much broke it in XP.

At a command prompt on the XP box type "ipconfig /all" without the
quotes, of course. What do you see as "Node Type"?

 

[Dave]

XP box results: Node Type: Unknown
2000 box results: Node Type: Broadcast

 

[Marina Roos]

Hi Dave,

Can you give us the whole ipconfig/all from both computers?

Marina

 

[Colon Terminus]

Bingo!

You need to add a value to the registry. If you're uncomfortabel with
this, I've attached a .reg file that'll do it. Save the attachment to
your desktop, right click on it and chose edit. You can then visually
verify that it is nothing more than it is presented to be.

HKLM = HKEY_LOCAL_MACHINE

HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters

Add a DWORD value named NodeType. Set the value of NodeType to 1.

That oughtta fix it.

 

[nemo]

Try adding a user to the XP machine with the same username and
password that you use to log on to the win2k machine.

Regards

nemo

 

[Dave]

I have already done this as I stated in my original post.

 

[Unnamed]

You know, I would like to say what a load of rubbish the above comment is. I
was networking happily with no problems on a network with 2 x 98SE
computers. XP came along and I updated one of the 98SE computers to XP Home.
The only difference I noted was in testing, I allowed all automatic and XP
took a VERY long time to become active on the network. So, I manually
configured IP numbers and all was well. Last year I bought a laptop with
it's own preinstalled XP Home and added it to the network, all manually
assigned and no problems again.

Today, I wanted to transfer 2gigs of file from one of the 98 machines (Now
have 2 x 98SE and 2 x XP Home) to a newly installed secondary HD on one XP
machine and even though I had allowed the new drive to have it's files
altered by other machines on the network and given permission to the network
to see the drive, this whole machine was unavailable to the network though
it still allowed ICS. I couldn't figure out why this had happened so simply
reinstalled the network under the same conditions on this machine and wonder
of wonders, it all worked again beautifully. In short, something was
corrupted in networking on THIS machine only.

XP networking for a home environment isn't hard. It is pitifully easy! If
you think it is hard, it may be about time to admit it is hard for YOU and
stop making out like it is hard for everyone. For most people it is dead
easy given a little time reading things!

 

[Unnamed]

I have found that in using a 2000 machine on a network with XP, it is always
prudent to have the GUEST ACCOUNT enabled on the XP machine so long as you
aren't using wireless networking. Once you do that, all works out fine.

 

[Bob I]

User account restriction sound like a "permissions" issue. Is the
Account the same level on both PC's is the "share" permissions set to
allow this account?

 

[Dave]

Yes, both are part of the Administrator group

User account restriction sound like a "permissions" issue. Is the
Account the same level on both PC's is the "share" permissions set to
allow this account?