Home Network

[Daolas]

Hey guys,

I've got a home network where I've shared the "C" drive on one of the computers to allow it to be used as a place to park movies, videos, music, etc.

My question is how can I view what's on the desktop of that PC. I've gone into documents and settings properties and set all the files for the user names as being able to be shared. When i try to navigate those files, I get an idiot message that says I can't view them because I don't have permission.


Any ideas?

Thanks.

 

[Weird Harold]

The "Desktop" is a function of which user is logged in, rather than which computer is being used -- sort of; it depends on how the network is set up.

I suspect in your case, each user has a personalized desktop on each computer in the network.

As for the error message you're getting, the Profiles folder (including the "desktop" folder) for each user isn't included when you set a users "files" as shared -- that just affects their my documents folder and sub-folders, not the rest of their profile. I'm not sure that you CAN set a users profile tree (pesonal informaton) as shared except to an administrator level user.

 

[rcms]

Remote desktop

If you are using Win XP, look at setting up the "Remote Desktop". It is part of the windows package, and it allows you to remotely log into another computer as if you were sitting in front of it. Just look in the windows help menu for instruction. We run a music server like this and it works very well.

 

[Daolas]

Thanks guys,

I appreciate your quick responses.

I'm off to check on Remote Desktops now.

 

[SubNebGuy]

Download a program called VNC. It's a better remote application than windows built in stuff.

its free as long as its for home use.

 

[Bert Notorius]

VNC is pretty cool. Win 95 was not very secure and you could access the profiles of other computers. I remember going in and resetting the screen saver scroll messages to what I wanted them to say.

 

[Daolas]

I just did a quick search on VNC. It looks like it might do what i need without too many problems.

I'm gonna download and play with it tomorrow.

A couple questions though.
Does it require a Static IP address?

If it does, how do i go about assigning them to my Desktops?


Thanks all

 

[south_florida_bicur]

The "Desktop" is a function of which user is logged in, rather than which computer is being used -- sort of; it depends on how the network is set up.

I suspect in your case, each user has a personalized desktop on each computer in the network.

As for the error message you're getting, the Profiles folder (including the "desktop" folder) for each user isn't included when you set a users "files" as shared -- that just affects their my documents folder and sub-folders, not the rest of their profile. I'm not sure that you CAN set a users profile tree (pesonal informaton) as shared except to an administrator level user.

WOW

you know your shit.. I am definitely contacting you with my computer questions... Glad you are here to help.

 

[Weird Harold]

I just did a quick search on VNC. It looks like it might do what i need without too many problems.

I'm gonna download and play with it tomorrow.

A couple questions though.
Does it require a Static IP address?

If it does, how do i go about assigning them to my Desktops?


Thanks all

I'm still not completely clear on just what it is that you're trying to do.

However, I think you might want to look at setting up the entire system to use aliased drive designations so that the "C:\" drive that is shared is the "C:\" drive for every computer in the network.

I'm not sure how easy or difficult that is with versions of Windows later than Win 98SE, but it should be possible. It used to require an extensive CONFIG.SYS and AUTOEXEC.BAT setup for network drivers but I haven't dealt with a true server/client network since I quit using a DOS 6.1 based Lantastic system.

You might have better luck asking your question on a more technically oriented netwrking site.

 

[rcms]

This is really funny. Check out- stayathomeserver.com. I know many people hate microsoft, but unless you have the skill to go "off the grid" don't fight it. The site is a promo for software designed to create a home server. Just plain funny, but indicative of where technology is heading.

Anyway, as I said in a previous post, I run a music server in my home, with 5 wireless networked PCs, and the WinXP "remote desktop" works great. Any computer in the house can access the server, play music at their computer, or control the house audio system. I can even access the server from any computer connected to the internet anywhere. The only problem is that only one PC can access the remote desktop feature at a time. All computers can access the shared files at anytime however, and I'm pretty sure you could set the remote function to log on multiple users; I just haven't bothered, so I can't tell you how.

 

[Bottomlover]

However, I think you might want to look at setting up the entire system to use aliased drive designations so that the "C:\" drive that is shared is the "C:\" drive for every computer in the network.

I'm not sure how easy or difficult that is with versions of Windows later than Win 98SE, but it should be possible. It used to require an extensive CONFIG.SYS and AUTOEXEC.BAT setup for network drivers but I haven't dealt with a true server/client network since I quit using a DOS 6.1 based Lantastic system.

With XP, all you have to do is use "Map Network Drive" under the Tools tab in Windows Explorer. Any user who has access to the shared drive can map it as any unused letter he wants.

 

[Weird Harold]

With XP, all you have to do is use "Map Network Drive" under the Tools tab in Windows Explorer. Any user who has access to the shared drive can map it as any unused letter he wants.

What I was talking about involves mapping drives to USED drive letters -- which was tricky but possible with Lantastic -- so that from any computer on the network, every reference to every drive is the same.

The biggest problem to solve is when you re-map the drive that contains the operating system files you lose contact with the configuration/batch/registry files that are doing the re-mapping.

I suspect that Windows' Map Drive function can re-map the c:\ drive it's working from but the documentation does't mention it because it causes so many problems without a lot of forethought and preparation.

 

[Bottomlover]

What I was talking about involves mapping drives to USED drive letters -- which was tricky but possible with Lantastic -- so that from any computer on the network, every reference to every drive is the same.

The biggest problem to solve is when you re-map the drive that contains the operating system files you lose contact with the configuration/batch/registry files that are doing the re-mapping.

I suspect that Windows' Map Drive function can re-map the c:\ drive it's working from but the documentation does't mention it because it causes so many problems without a lot of forethought and preparation.

I thought it was too simple.

 

[Weird Harold]

I thought it was too simple.

It gets a lot easier if you dumb-down everything but the server; if you set each client compuer up to "Boot from Network" (and without any local drives,) it's even easier.