networking problem

[kostk0]

Hello, i have the following network problem:

I have 2 XP pro computers, connected in lan, pinging fine.
On both computers i logon with the same credentials with administrative privileges. From computer A, i can access fine every shared resource that computer B offers. Trying to access computer A, from computer B (the opposite) i get an access denied message. All network settings are double checked and are fine. What troubles me is that at computer A, when i am at command promt, i see this: C:\Documents and settings\ComputerA.user>
When i changed the computerA name, the command prompt stayed the same as above, unchanged..
When i'm at computerB, at command prompt I normally see the : C:\Documents and settings\user>

Anyone can help me out ?

Thanks in advance,
Kostas

 

[Fatboy0341]

Are both of these PCs members of the same workgroup (check the spelling) and how are their IP/DNS settings set up? Automatic? Are you logging on as a LOCAL Admin or are the PCs members of a domain?

WHat are the actual names of these PCs?



"He who laughs last probably made a backup. He who laughs loudest probably hasn't checked his backups in a while."

 

[kostk0]

Yes they are members of the same workgroup for sure. I use static ip, auto dns. they are not connected to the internet.
they are pinging each other fine. there is no domain. i created new users with admin rights. the names are gramatea and mario. mario cannot access gramatea.

what troubles me is the prompt described at my first post.

thanks,
Kostas

 

[ArizonaGeek]

Check your NT permissions for the login you trying. Right click on the share and select the Security Tab make sure that login has the appropriate access.

Windows permissions and NT permissions are different things, just because you share something doesnt necessarily mean its totally shared out.

 

[linney]

Are you running any security type software (Firewall or Antivirus with hidden firewalling components)?

Put both machines in to "Safe Mode with Networking" and see if they can talk to each other.

WinXP Connectivity Issues
faq779-4625

Change the Command Prompt

http://www.winguides.com/registry/category.php?180

 

[kostk0]

Hi, thanks for your help,

NT permissions security is checked and it's ok.

Also, there is'nt any connectivity problem between the machines. The problem is clearly at the user permission level.

I know this, because i create the same user with the same password on both computers, but on one of the computers (gramatea) the username is modified to : gramatea.username

So when i connect to 'gramatea' computer from 'mario' computer, logged in as 'username' , 'gramatea' rejects me because it does'nt know anybody 'username', it only knows 'gramatea.username' ....

I even tryed to create a user named 'gramatea.username' on 'mario' computer but it did'nt work..

 

[linney]

Can either user use Remote Desktop to remotely connect to their computer from the other computer?

Any Shared folders you have set up on either machine, check to see that the "Everyone" user is added with a suitable access permission. This will allow the .user and the non. user that amount of access when attempting to access Shared folders.

Simple File Sharing- enabled

http://www.practicallynetworked.com/sharing/xp/filesharing.htm

Simple File Sharing - disabled

http://www.practicallynetworked.com/sharing/xp_filesharing/index.htm

http://www.michna.com/kb/wxnet.htm

 

[Freestone]

Delete the offending profile gramatea.username and try creating the account again.

What usernames are you using? I don't know if it'll make a difference, but generic terms like 'username' could disguise a naming issue.

 

[kostk0]

Hi, thanks for the help,

I did'nt try Remote Desktop. I will.
"Everyone" is added. I tryed everything with user names and permisions.. deleted accounts and made new ones etc..

i'll check the links you sent me also, thanks

 

[linney]

Also try Safe Mode with Networking, that will eliminate blocking issues by third party software such as firewalls and other security type programs.

In the Event Viewer, the security logs might hold some clues too.