Network Neighborhood Question

[CornMaster]

I'm not even sure if this is possible....but I need to share a folder on one system, with full access.....but I don't want anyone to be able to see this folder in Network Neighborhood on the other computers.

Can it be done?? Either Natively or with aid from another program?

[ShadowKing]

Yep, very easily.

When you create a share name, end it with a $.

So, for example, if I share C:\temp as TempStuff$ on a machine named Joe, I can connect to it by typing \\joe\tempstuff$ but it will be hidden and not visible from explorer.

Enjoy.

One thing you might want to be aware of is that if NETBIOS is enabled, they can still figure out that it exists and get at it. So if you are using Win2k, you might want to disable NetBios.

[CornMaster]

That hid the folder from Network Neighborhood.....but now my shortcut to the program doesn't work...because it can't find the file. .....

Nevermind. Fixed it. Just had to make the new shortcut with the network path...instead of just the file. Thanks.

[KINGofBLEH]

[quote]Originally posted by CornMaster:
<strong>That hid the folder from Network Neighborhood.....but now my shortcut to the program doesn't work...because it can't find the file. .....

Nevermind. Fixed it. Just had to make the new shortcut with the network path...instead of just the file. Thanks. </strong><hr></blockquote>

Point your shortcut to the IP address of the host machine. EX: "\\192.168.1.5\SharedFolder$".

[Ya_know]

[quote]Originally posted by KINGofBLEH:
<strong>

Point your shortcut to the IP address of the host machine. EX: "\\192.168.1.5\SharedFolder$".</strong><hr></blockquote>

Depending on your situation, pointing to an IP may not be a good idea. IP addresses can be changed more frequently than computer names, even static IP's.

For example, we had several servers all over the country with static IP's. When a different company bought us out all of the frame-relay circuits were changed, thus changing subnets. All emulation sessions to these servers using the old IP addresses were invalid. Sessions had to be recreated, using a system name.

[KINGofBLEH]

[quote]Originally posted by Ya_know:
<strong>

Depending on your situation, pointing to an IP may not be a good idea. IP addresses can be changed more frequently than computer names, even static IP's.

For example, we had several servers all over the country with static IP's. When a different company bought us out all of the frame-relay circuits were changed, thus changing subnets. All emulation sessions to these servers using the old IP addresses were invalid. Sessions had to be recreated, using a system name.</strong><hr></blockquote>

Touche`. But if the NetBios name is hidden in Network Neighborhood, then he will not be able to map a drive to it. I was just offering the next best alternative.

Mapping to hidden shares would only work in a Win 2k or NT domain running AD or DFS (respectively).