how-to block ads
|
|
Uniqs:
3382 |
Share Topic
 |
 |
|
|
|
| reply to tlarkins
Re: Node Type - XP Home Small Network Setup How-To i did figure out how to use the regedit to specify a node type...at least i was able to on my laptop,...gimme some time to try it on my desktop, and i'll get back to you | | |
|
| reply to tlarkins
Re: [XP] they see each other, but access denied i went ahead and manually set both to 'broadcast' nodetype using the registry editor...i checked to make sure they are both set correctly by going to the command prompt and typing 'ipconfig /all' on both machines and they are both set correctly to 'broadcast' nodetype...however, the problem is still the same | |
| reply to tlarkins
UPDATE:
I have looking over my router "Intruder Detection Log" and it seems that source 192.168.2.2 is trying to access 192.168.2.1 using an invalid password...does that make sense to anyone? remember, 192.169.2.2 is the IP for the desktop, and it is the one that gets the "access denied" message. does this give insight into the problem?
--
"the object of war is not to die for your country, but to get the other bastard to die for his" Patton | |
 funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | said by tlarkins:UPDATE: I have looking over my router "Intruder Detection Log" and it seems that source 192.168.2.2 is trying to access 192.168.2.1 using an invalid password...does that make sense to anyone? remember, 192.169.2.2 is the IP for the desktop, and it is the one that gets the "access denied" message. does this give insight into the problem? Hmmm. I really, really doubt it.
Do a quick test and try to access your router's config page with an invalid password. Then log in correctly and see if the first attempt was logged.
Did you go through the Chapters 6-7 that I linked to above?
Here's some other stuff (do you believe that?!?  )
Open Services (services.msc) and ensure that these services are
•not disabled and are started: Browser, Server, Workstation, Internet Connection Sharing and Firewall Service (even if you're not using these), TCP/IP NetBIOS Helper Service.
•not started and disabled: DNS Client service (needed only for Domain networks, not workgroups)
Open Network Connections.
•Remove all bridges (if any).
•Disable other transport protocols like IPX (NWLink) and NetBEUI.
•Check the advanced TCP/IP settings an ensure that NetBIOS over TCP/IP is enabled (it is 'automatic' by default, and that's almost always fine).
And I found this that might apply:
When you get an error that you have no permission to access a share, another possible cause is that Windows XP is using a saved, but obsolete password. To remedy this, use Control Panel, User Accounts, click on your own account, select "Manage my network passwords". Check whether the problem computer shows up in the list. If it does, click on it and select Remove. (source -- » www.michna.com/kb/WxNetwork.htm)
--
Robb Topolski || http://www.funchords.com/ || Hillsboro, Oregon USA
The enemy of freedom is dependence.
Support this site - Get more features - Be a Member! - It's Free! | |
3 edits | you were right about the router.
And yes, I did go through Chapters 6-7.
i opened services.msc on my laptop, and didnt see Browser, Internet Connection Sharing and Firewall Service listed.
also, the DNS Client service was started and set to automatic on startup...so i turned it off, and set it to disabled on startup.
desktop was exactly the same.
also, i tried to use the "connect to another computer" from the 'action' menu option...it gave me an error 5, unable to open service control manager database on desktop.
does that tell us anything? i was unable to start the other services because they weren't listed.
--
"the object of war is not to die for your country, but to get the other bastard to die for his" Patton | |
funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | Okay, take a look at this: »support.microsoft.com/kb/813940/
I'd like to know if your network card properties have the same clients and services shown in that article. Also see if you have anything extra.
How you got through the Home Networking Wizard, I'll never know. Maybe there was a system restore or something since you did that.
--
Robb Topolski || http://www.funchords.com/ || Hillsboro, Oregon USA
The enemy of freedom is dependence.
Support this site - Get more features - Be a Member! - It's Free! | |
| reply to tlarkins
tlarkins, I have the same exact problem. I have searched other forums and get the same suggestions on fixes but to no avail. Here is my post on another forum to make things a little clearer:
OK, my home network consists of 4 computers and an xbox hardwired to the network and a laptop wireless. The connection is a hub not a router. I have satellite internet and all computers connect to the internet thru one computer. I use winproxy instead of microsoft ICS and this programs firewall. The firewall is turned off on all other computers. We ftp to the xbox so I will leave that out of my setup. The computers are as follows:
Name: OS:
LivingRoom XP Home (this computer has the adapter for
the internet)
CHI XP Home (has a printer that the network
shares)
Dad 98 SE (this is the laptop)
Alex XP Home
Basement 98 SE
-Livingroom can see everything except CHI and its printer
-CHI can see everything but Livingroom
-Basement, Alex and Dad can see each other but not CHI or Livingroom
Under network conetions, LAN, all computers showup:
Livingroom
Dad
Chi
Basement
Alex
but if I am on the laptop and click Livingroom I get the message:
\\Livingroom is not accesible
No permission to access resource
and if I click CHI I get the message:
Enter a network password
Resource: \\CHI\IPC$
Password:________________
I get the same message if I try to print something from any of the computers on the printer connected to CHI.
Does this sound similar to your problem? I am just baffled. Gene
--
DPCSRS 1350 G4R 4.0.3.9 DAK403_P8, P4 2.2 Win XP,3 client P + PII W98 and PIII 700 laptop win98se hooked via linksys wap, orbitnet | |
1 edit | your setup is more complicated than mine, but the problem is the same...hope we find a solution. | |
| reply to tlarkins
I'd like to know if your network card properties have the same clients and services shown in that article. Also see if you have anything extra.
both have only those four...not more, nothing less
--
"the object of war is not to die for your country, but to get the other bastard to die for his" Patton | |
funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | reply to tlarkins
I may have to wave the white flag on this one. I'll come back to this thread if I come up with something else.
Hopefully someone else can see something that we've missed and comment... | |
| said by funchords:I may have to wave the white flag on this one. I'll come back to this thread if I come up with something else. Hopefully someone else can see something that we've missed and comment... well, darn...
--
"the object of war is not to die for your country, but to get the other bastard to die for his" Patton | |
 cacrollEventually, Prozac becomes normalPremium
join:2002-07-25
Martinez, CA | reply to tlarkins
said by tlarkins:i used windows xp to setup a home network...problem is, i can't access either computer from the other. when i goto "view workgroup computers" i am able to see both computers, no matter which i am physically sitting in front of. however, at that point, i can only access the computer i am at, it gives the following error message: "XXXXXX is not accessible. You might not have permission to use this network resource. contact the" blah blah blah, you know the rest. now, from the desktop, i also get this: "access denied" but from the laptop, i get logon failure, you have not been given permission to access this resource" i have tried with xp firewall, and without xp firewall, i have checked and my norton doesn't use a firewall, it is antivirus only, not internet security. i have no other 3rd party programs that run firewalls.
With XP Home, "access denied" means the Guest account isn't properly activated for network access. The other error, "not been given permission...", means you have to explicitly set rights for Guest; this is a bit more work.
Activate Guest Properly
Set Rights For Guest
--
Cheers,
Chuck
PChuck's Network | |
1 edit | said by cacroll:With XP Home, "access denied" means the Guest account isn't properly activated for network access. The other error, "not been given permission...", means you have to explicitly set rights for Guest; this is a bit more work. Activate Guest ProperlySet Rights For Guest heck yea, the first was fixed by doing this at the command prompt:
net user Guest /active:yes
now i no longer have the 'access denied' problem and can access my laptop from my desktop.
will try the other thing and get back
--
"the object of war is not to die for your country, but to get the other bastard to die for his" Patton | |
2 edits | reply to tlarkins
ALL PROBLEMS RESOLVED... thanks cacroll
due to XP Home limitations, i had to manually use the following:
Type these three lines, one at a time, at the command prompt. The ntrights commands are case-sensitive and all are space sensitive, so type them exactly as shown. Note the spaces separating each word, and the "+r" in the second one and the "-r" in the third one:
net user guest /active:yes
ntrights +r SeNetworkLogonRight -u Guest
ntrights -r SeDenyNetworkLogonRight -u Guest
thanks to everyone for all the hard work! now I can do some major files and resource sharing!
--
"the object of war is not to die for your country, but to get the other bastard to die for his" Patton | |
cacrollEventually, Prozac becomes normalPremium
join:2002-07-25
Martinez, CA | said by tlarkins:ALL PROBLEMS RESOLVED... thanks cacroll due to XP Home limitations, i had to manually use the following: Type these three lines, one at a time, at the command prompt. The ntrights commands are case-sensitive and all are space sensitive, so type them exactly as shown. Note the spaces separating each word, and the "+r" in the second one and the "-r" in the third one: net user guest /active:yes ntrights +r SeNetworkLogonRight -u Guest ntrights -r SeDenyNetworkLogonRight -u Guest thanks to everyone for all the hard work! now I can do some major files and resource sharing!
Glad to help, and thanks for the feedback.
--
Cheers,
Chuck
PChuck's Network | |
funchordsHelloPremium,MVM
join:2001-03-11
Yarmouth Port, MA
kudos:5 | reply to tlarkins
I am so glad to hear you finally solve it!! Congrats tlarkin and thanks Chuck!! Great job both of you! | |
| reply to funchords
Re: Node Type - XP Home Small Network Setup How-To Worked like a champ!
Instant fix... | |
| Hi,
I get the ntrights is not recognized problem when I type that into cmd, I am having the exact same problems.
Please help 
Windows xp x 2, both can see each other, only one can access both. | |
| reply to tlarkins
Re: [XP] they see each other, but access denied This may help from »www.michna.com/kb/wxnet.htm
*Simple File Sharing:
Background: Simple file sharing, the only method on Windows XP Home and one of two choices on Windows XP Professional, always uses the Guest account. (Classic file sharing also automatically uses the Guest account if the original logon request fails.) If access through the Guest account is inhibited, then sharing cannot work, except by logging on to XP Professional with classic file sharing through a non-guest account.
In Windows XP Professional you can check whether you have simple file sharing enabled by clicking on Start, Control Panel, Folder Options, View, and looking at the option "Use Simple File Sharing (Recommended)".
Windows NT and 2000 automatically treat failed attempts to log on over the network in a second attempt to log them on anonymously, i.e. as Guest. Windows XP can do this too, but it has to be enabled first, particularly on XP Professional.
To make sure Windows XP Home is set up properly, you can run the Network Setup Wizard. If you use a router, select the option where the computer connects to the Internet through a residential gateway.
The Guest account should have no password. If you are not sure whether this has mistakenly been changed, you can remove any password from the Guest account with the following procedure.
Click on: Start
Click on: Run...
Type into the data entry field: control userpasswords2
Click on: OK
Click once on: Guest
Click on: Reset Password
Do not enter any password, leave the two fields empty.
Click on: OK
For network access to Windows XP through the Guest account, the Guest account has to be enabled in Computer Management, Local Users and Groups. A quick way to enable Guest network access is to type the following command at a command prompt:
net user guest /active:yes
If this doesn't solve the problem and you are still being asked for a password, check for stored network passwords.
Click on: Control Panel
Click on: User accounts
Click on your own account.
Click on: Manage my network passwords
Check whether there are any stored passwords for the target computer. If so, remove them.
If, however, the problem is just the other way around and you actually want to see the "Connect as" dialog, you have to disable the Guest account on the target computer, i.e. the server, the computer on which the objects are that you want to access.
Note also that the settings in the user manager in the control panel have nothing to do with networking. Disabling the Guest account there only has the effect that nobody can log on locally (at the keyboard). It does not have any effect on network access.
On an NTFS partition, Windows XP Home does not allow to share these folders:
User folders directly in Documents and Settings
Program Files
The main Windows folder
*NetBIOS node type
Another related and surprisingly frequent problem beside disabled NetBIOS over TCP/IP is the setting of an unsuitable node type for Windows networks (which use NetBIOS). If you don't see other computers in Network Neighborhood or My Network Places, then this computer may have the wrong node type. If you get error messages when you try to access another computer, then you may have to walk over to that other computer and perform the following steps there.
First check the node type by opening a command line window and typing the command
ipconfig /all
This command reports the node type, among other information. It should be Hybrid or Unknown, but not Point-to-Point (p-node, actually a mistaken interpretation of Peer-to-Peer), because that would work only when a WINS server is present.
If the node type is P-t-P, you can use regedit.exe to go to
HKEY_LOCAL_MACHINE
\System
\CurrentControlSet
\Services
\Netbt
\Parameters
and delete any of the two values NodeType and DhcpNodeType if they exist, forcing Windows to fall back to its default node type, which should be Hybrid. Reboot.
Additional information about these values:
Value Name: DhcpNodeType
Value Type: REG_DWORD - Number
Valid Range: 1,2,4,8 (B-node, P-node, M-node, H-node)
Default: 1 or 8 based on the WINS server configuration
Description: This optional parameter specifies the NBT node type. It is written by the DHCP client service, if enabled. This parameter determines what methods NetBT uses to register and resolve names. A B-node system uses broadcasts. A P-node system uses only point-to-point name queries to a name server (WINS). An M-node system broadcasts first, and then queries the name server. An H-node system queries the name server first, and then broadcasts. Resolution through LMHOSTS and/or DNS, if enabled, follows these methods. If this key is not present, the system defaults to B-node if there are no WINS servers configured for the network. The system defaults to H-node if there is at least one WINS server configured.
Value Name: NodeType
Value Type: REG_DWORD - Number
Valid Range: 1 - 8
Default: 1
Description: This parameter specifies the NBT node type. It is an optional parameter that, if present, will override the DhcpNodeType parameter. See the entry for DhcpNodeType above for a complete description.
More details can be found in the following Microsoft Knowledge Base article.
Default Node Type for Microsoft Clients
»support.microsoft.com/kb/160177/
The cause of the wrong node type is unclear, but there is the suspicion that Windows itself changes the node type to P-t-P when the computer is brought into contact with certain DHCP or WINS servers, for example when a portable computer is connected to a company network, perhaps when it joins a domain that has a WINS server. If so, then the typical victim should be a travelling laptop computer.
*The RestrictAnonymous registry value
You have both the following symptoms:
You can ping the computer by IP and by name.
When you type on another computer, replacing computername with the name of the inaccessible computer:
net view \\computername
you get one of the various "Error 5" error messages, like "System error 5 has occurred. Access is denied" or "Error 5: You do not currently have access to this file. ..."
This is in some cases caused by a registry setting named RestrictAnonymous. Go to the computer which you cannot access, start a registry editor and change the following registry value.
HKEY_LOCAL_MACHINE
\SYSTEM
\CurrentControlSet
\Control
\Lsa
Value name: RestrictAnonymous
Value type: DWORD
If the value is 1 or even 2, change it to 0, reboot and retest. If the problem is solved, leave the value at zero. If not, you can change it back if you like.
Check immediately afterwards and again after a reboot, whether the value changes back to non-zero on its own. If that happens, then you have to find the culprit, which can be spyware, a worm, or a badly designed security program. In this case this procedure most likely solved your problem, but then the bad software stepped back in and recreated the problem.
One last thing, remember that simple file sharing uses the guest account access. TO reset permissions on your shares you simply unshare the item (i.e. a folder or printer) and reshare it.
Hope this helps! | |
|
