windows XP pro - simple network question

[chennaiprogrammer]

I have 10 windows XP pro computers connected on a network LAN

and their internal IP addresses are

192.168.0.1 to 192.168.0.10

Now I need the computer having IP address 192.168.0.5 to access ONLY 192.168.0.2 and 192.168.0.4 and no other computers ?

For all other computers no access restrictions at all.

1) Is it possible to configure access restrictions on 192.168.0.5 computer like that ?

2) Plus is it possible to allow ONLY 192.168.0.10 access to all files and permissions of 192.168.0.5 ? i.e 192.168.0.10 is the only external computer that can do *anything* on 192.168.0.5 and all other computers do not have access on 192.168.0.5 at all

Note 192.168.0.10 has access to all other computers no problem.

 

[smah]

In the grand scheme of things, you'd probably better off controlling permissions by user instead of machine. However, I suppose that you could set some firewall software on each machine to behave the way you describe.

 

[vacunita]

You could also play around with the lmhosts, and hosts files, and point every IP address you don't want the PC to access to itself, and only leave the 2 that you do want it to access.




----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

 

[lhuegele]

You could also set-up vlan's on your network switch if it supports that. Another option is to sub-net your lan.

 

[chennaiprogrammer]

I thought this would be easy. So is there no simple way to do

what Im asking ?

 

[vacunita]

You could also look into Sharing Permissions. You can set folder permissions to only allow certain users to open them and view them. Of course that would require that all users from the 10 Pc's exist in all 10 machines. so you could then change the permissions on a per user basis.

But if you wanted a point and click solution, i'm afraid there no such thing. you will have to at least get into the network workings a bit.

----------------------------------
Ignorance is not necessarily Bliss, case in point:
Unknown has caused an Unknown Error on Unknown and must be shutdown to prevent damage to Unknown.

 

[ArizonaGeek]

In the grand scheme of things, you'd probably better off controlling permissions by user instead of machine.

I'd have to agree with smah. If you are on a domain you could just set up permissions per user, they may be able to SEE the other machines but will have no access to them. You could even go so far as to set up deny permissions to the machines they shouldn't have access to.

To accomplish what you want via networking, at least from what I am seeing, is WAY WAY more work than you should be willing to do.

To that end, there is no real easy way for what you want to do. Good luck!

Cheers
Rob