|
|
|
Windows file sharing
AppleShare IP allows you to provide file sharing services over
TCP/IP to Windows 95, Windows 98, and Windows NT clients.
IMPORTANT: The instructions in this section assume that you have followed
the TCP/IP setup and Windows file sharing setup instructions in
the "Getting Started" manual.
This section tells you about
It also tells you how to
|
|
|
|
About Windows file sharing and SMB |
|
|
|
|
|
The Web & File Server provides Windows file sharing service via
Microsoft's SMB (Server Message Block) protocol. SMB runs on top
of a protocol called NetBIOS, which runs on top of another protocol,
such as NetBEUI, Novell IPX, or TCP/IP. AppleShare IP only supports
SMB over TCP/IP.
Windows and Mac OS file sharing:
To use AppleShare file sharing on a Mac OS-based client, the user
opens the Chooser and selects the AppleShare icon. As soon as
AppleShare is selected, the client computer sends a request to
the current zone and asks that all AppleShare servers identify
themselves. The zone and AppleShare IP server, for example, then
appear in the Chooser.
To use AppleShare's Windows file sharing on a Windows client,
the user opens the Network Neighborhood window and the client
computer asks the Browse Master (a computer on the local subnet
that has a list of available servers) for Windows file sharing
servers. Since the Windows servers don't announce their presence
as often as Mac OS servers, the Browse Master's server list can
become out of date; it can take up to an hour to accurately reflect
the servers available on the subnet.
On Windows networks, browsing for and connecting to servers doesn't
automatically work across IP subnets (across routers). In order
for Windows clients to see your AppleShare IP server when your
network has more than one subnet, you need to register your AppleShare
IP server with the name resolution software on your Windows NT
server. This procedure is similar to the required DNS server setup
on Mac OS networks.
For more information about SMB or other Windows networking topics,
see these Microsoft Web sites:
|
|
|
|
Enabling and disabling Windows file sharing |
|
|
|
|
|
You can turn on Windows file sharing service to allow registered
users with Windows computers to connect to the Web & File Server
for file sharing services. You can also turn off Windows file
sharing service and allow or deny guest access.
To enable Windows file sharing service, follow these steps:
1 |
Log on to AppleShare IP Remote Admin. |
2 |
Click the File server button.

|
3 |
Click the Server Settings button. |
4 |
In the Server Settings list, click Windows File Sharing. |
5 |
To turn on Windows File Sharing, select the "Enable Windows File
Sharing" checkbox, then go to step 6. |
|
To turn it off, deselect the checkbox. Then you're done. |
|
Note: The Web & File Server assigns the AppleShare IP server's unqualified
DNS name (the first name before the first dot) as the name of
the Windows file sharing server. You should not change this name
because it makes it easier for some clients to connect to the
Web & File Server. |
6 |
To allow any Windows client user to connect to the Web & File
Server without entering a name or password, select the Enable
Guest Access checkbox. |
7 |
Type the workgroup name in the Workgroup Name text box. |
|
This is the name your Windows clients use to describe their local
group of computers on the network. Consult your Windows network
administrator for the correct name. |
|
Note: If you have any Windows NT domains (a domain is Windows NT's
version of a workgroup; Windows NT domains can span subnets but
workgroups cannot) on your subnet, use one of them as the workgroup
name. This will make it easier for clients to communicate across
subnets. |
8 |
If you like, type a description for the server. |
|
Users can see this information in their Network Neighborhood.
|
9 |
If your network has a WINS (Windows Internet Name Service) server,
select the Enable WINS Registration checkbox. Then enter the IP
address or Internet domain name of a WINS Server on your network. |
|
You should select this box if your clients and the AppleShare
IP Web & File Server are not all on the same subnet. |
|
When this box is selected, the AppleShare IP server is registered
with the WINS server on your network and Windows clients can connect
to it across subnets. |
10 |
Click the Save button. |
|
Your changes take effect after you turn off and on Windows file
sharing or restart the server. Make sure no one is connected to
the server when you restart it. |
11 |
If you turned on Windows file sharing service, make sure that
your AppleShare IP Web & File Server appears in your clients'
Network Neighborhood window. For instructions, see Opening the Network Neighborhood. |
|
|
|
|
Making the Web & File Server appear in the Network Neighborhood
(single subnet) |
|
|
|
|
|
Once Windows file sharing is set up, you may want to make sure
that users can see the AppleShare IP Web & File Server icon in
their Network Neighborhood window. This section describes how
to make the AppleShare IP icon appear on a single-subnet network.
If your clients are not all in the same subnet as the Web & File
Server, see Making the Web & File Server appear in the Network Neighborhood
(across subnets).
Note: The easiest way to connect to the Web & File Server is to use
the Network Neighborhood. However, your Windows clients can also
connect without using the Network Neighborhood. For instructions,
see Connecting to the Web & File Server without using the Network
Neighborhood.
To make the AppleShare IP icon appear in the Network Neighborhood
window when clients are on the same subnet as the Web & File Server,
follow these steps:
1 |
Make sure your Windows clients are properly configured for TCP/IP
and have the appropriate networking software installed. |
2 |
Make sure your Windows clients are on the same subnet as the Web
& File Server. If not, skip to Making the Web & File Server appear in the Network Neighborhood
(across subnets). |
3 |
Check to see if your Windows clients and AppleShare IP server
are in the same workgroup by noting the workgroup name in the
Network Neighborhood window on a Windows client computer. |
|
A workgroup is a collection of computers on a network, like a
zone on a Mac OS-based computer. If your AppleShare IP server
is in a different workgroup from any of your Windows clients,
your users will need to know the workgroup of the AppleShare IP
server. |
4 |
Open the Network Neighborhood window on a Windows client computer
to see the AppleShare IP server. |
|
It may take a few minutes, or longer, for the AppleShare IP server
to appear. (The Refresh command does not speed the process.) |
|
Client users in the same workgroup or Windows NT domain (Windows
NT domains can span subnets but workgroups cannot) as the Web
& File Server can connect to the server as soon as it appears
in the Network Neighborhood window by double-clicking its icon.
|
|
Client users in a different workgroup or Windows NT domain can
connect to the server by double-clicking the Entire Network icon,
the correct workgroup or Windows NT domain icon, and the Web &
File Server icon. |
|
When users log onto the Web & File Server, their Windows login
name is used as their AppleShare user name. |
|
|
|
|
Making the Web & File Server appear in the Network Neighborhood
(across subnets) |
|
|
|
|
|
Once Windows file sharing is set up, you may want to make sure
that users can see the AppleShare IP Web & File Server icon in
the Network Neighborhood window. This section describes how to
make the AppleShare IP icon appear when your Windows clients are
not in the same subnet as the Web & File Server.
If your clients are all in the same subnet as the Web & File Server,
see Making the Web & File Server appear in the Network Neighborhood
(single subnet).
When your Windows clients are in a different subnet from your
AppleShare IP Web & File Server, you need to provide a way to
match IP addresses with Internet domain names across subnets.
You can provide this name resolution service by installing WINS
(Windows Internet Name Service) software on a workstation on your
network, or by creating LMHOSTS files.
If you want your clients to be able to browse across subnets and
see your AppleShare IP server and other computers in the Network
Neighborhood window, you need to configure a Windows NT server
on your network to allow browsing across subnets. For more information,
see your Windows Networking documentation.
Note: The easiest way to connect to the Web & File Server is to use
the Network Neighborhood. However, your Windows clients can also
connect without using the Network Neighborhood. For instructions,
see Connecting to the Web & File Server without using the Network
Neighborhood.
To make the AppleShare IP icon appear in the Network Neighborhood
window when clients span subnets, follow these steps:
1 |
Make sure your Windows clients are properly configured for TCP/IP
and have the appropriate networking software installed. |
2 |
Make sure your Windows clients and AppleShare IP Web & File Server
are members of a Windows NT domain on your network. |
|
A Windows NT domain is the Windows NT's version of a workgroup.
Windows NT domains can span subnets while workgroups cannot. |
|
For instructions on how to create a Windows NT domain, see your
Windows NT documentation. |
3 |
Log on to AppleShare IP Remote Admin, and make sure the Enable WINS Registration checkbox in the Windows
File Sharing section of the File Server Settings window is selected,
and that a DNS name (or IP address) is specified for your WINS
server. (If you do not have a WINS server, skip to step 4.) |
|
WINS matches IP addresses with Internet domain names so that users
can communicate across subnets. |
|
If you have a Windows NT server, it came with WINS software installed.
For instructions on how to register your computers using the WINS
software, see your Windows NT networking documentation. |
4 |
If you do not have a WINS server, you need to provide name resolution
across subnets by creating an LMHOSTS file and placing a copy
on each Windows client. |
|
LMHOSTS is a text file that contains the names and IP addresses
of the Windows computers on all subnets to which your Windows
clients need to connect. For more information, see the LMHOSTS.SAM
file installed with your Windows 95 or Windows 98 software. |
5 |
Open the Network Neighborhood window on a Windows client to see
the AppleShare IP server. |
|
It may take several minutes for the AppleShare IP server to appear.
(The Refresh command does not speed the process.) |
|
Client users in the same Windows NT domain as the Web & File Server
can connect to the server by double-clicking its icon in the Network
Neighborhood window. |
|
Client users in a different Windows NT domain can connect to the
server by double-clicking the Entire Network icon, the correct
Windows NT domain icon, and the Web & File Server icon. |
|
|
|
|
Connecting to the Web & File Server without using the Network
Neighborhood |
|
|
|
|
|
If your Windows clients are properly configured for networking
and connected to the network, they can connect to the Web & File
Server even if they cannot see the server icon in the Network
Neighborhood window.
To connect to the Web & File Server without seeing it in the Network
Neighborhood, follow these steps:
1 |
Make sure your AppleShare IP server is configured for Windows
file sharing. |
2 |
Turn on Windows file sharing service on your AppleShare IP server
as described in Enabling and disabling Windows file sharing. |
3 |
On the Windows client, use the Find command in the Start menu
to locate your AppleShare IP Web & File Server. |
|
Choose Computer from the Find command's submenu in the Start menu.
Type the Windows server name of the Web & File Server in the box
that appears, and click OK. Your server appears in the list of
found items. |
4 |
Double-click the server to connect. |
|
If necessary, enter the client user's name and password. |
|
|
|
|
Changing the name of the Windows file sharing server |
|
 |
|
|
|
You can change the server name that Windows clients see in the
Network Neighborhood window.
Note: The Web & File Server assigns the AppleShare IP server's unqualified
DNS name (the first name before the first dot) as the Windows
file sharing server name. You should use this name, because it
makes it easier for some clients to connect to the Web & File
Server.
To change the name of the AppleShare IP Windows file sharing server,
follow these steps:
1 |
Log on to AppleShare IP Remote Admin. |
2 |
Click the File server button.

|
3 |
Click the Server Settings button. |
4 |
In the Server Settings list, click Windows File Sharing. |
5 |
To change the server name that appears in the Network Neighborhood
window, enter a Windows host name in the Server Name box. |
|
The name should have fewer than 15 characters and no special characters
or punctuation (such as ./\[]:+"|<>=;,*? or space). |
|
For example, an AppleShare IP server with the name "myserver.company.com"
might have the Windows server name "myserver." |
6 |
Click the Save button. |
7 |
Your changes take effect after you turn Windows file sharing off
and on, or stop and start the Web & File Server. Make sure no
one is connected to the server when you stop service (you will
need to go to the server to start it). Be sure to tell your Windows
users the new name of the server. |
|
|
|
|
Windows file sharing and naming guidelines |
|
 |
|
|
|
Mac OS and Windows systems store and maintain files differently.
You should understand the differences to avoid problems when naming
share points.
These are some general Windows file sharing and naming guidelines:
|
Create separate shared folders for Windows users and ask them
to use only these folders. Windows users can damage Macintosh
files (especially applications) by opening or moving them. Keeping
the two types of files in separate folders minimizes the risk
of accidental damage. |
|
Don't give Windows users access to folders containing Mac OS-only
files. Some Mac OS file information is lost when a file is taken
from a Mac OS computer to a Windows computer. |
|
When users are modifying files, they should use the application
that created the file. Although many files can be opened by other
applications, using a different application to make changes can
permanently damage a file. |
|
Do not use file names longer than 31 characters. |
|
Table of contents
|