http://www.eecs.harvard.edu/~shnayder/computer.jpg
Check out this picture of what the scientists in the 1950s expected computers to look like in 2004! How amazing! This computer would not even fit in my house!
Friday, September 24, 2004
Wednesday, September 15, 2004
Self-Assessment Survey Example from Conroe SD
Assessment tools for ICT in education
Assessment tools for ICT in education
http://www.unescobkk.org/education/ict/v2/info.asp?id=11088
Great site for listing out of assessments for site technology. Investigate this.
http://www.unescobkk.org/education/ict/v2/info.asp?id=11088
Great site for listing out of assessments for site technology. Investigate this.
Sunday, September 05, 2004
Logging in to Mac OS X Server using Windows XP Computer
We have a business lab with a number of brand new Windows XP computers. We are unable to log in to the Mac OS X Server X.3.4, eventhough we have Windows Services on and the Mac OS X Server is set up as the PDC.
I found the following helpful discussions:
- http://discussions.info.apple.com/webx?13@206.RzcIaN89vNW.7@.68998011/0 - discusses how to do it:
"On your server, configure Windows services as a PDC (Primary Domain Controller) and define a domain.
At your PC, logon as as administrator and go to Network Neighborhood and see if you can see the domain. If you can, you need to set the PC up to access the domain. On W2K, it's My Computer/Properties/ Network Identification. Click on "Properties" and check Domain and enter the OSX PDC domain name. You will be asked to logon to the OSX server (admin) and after a long minute you should receive a message, "Welcome to XXXXXXX Domain". You will be prompted to reboot.
At the logon screen, enter a OSX username (long name or short name) / password. Make sure you enter the domain you wish to enter. If you don't see a "Log on to ________" box, select options and then select the domain. This should get you on the server.
To verify, open My Computer and you should have a H: drive assigned with the shortname of the user you signed on as. "
______
More detailed information comes from the File Services Administration manual from Apple on pages 55 - 72 :
"Changing General Settings
You can use the General pane of the Windows service settings in Server Admin to
provide a server description, name, and workgroup and specify the server’s role in its domain.
To configure Windows service General settings:
1 Open Server Admin and select Windows in the Computers & Services list.
2 Click Settings, then click General.
3 To specify how your server participates in the local domain, choose from the Role popup menu.
4 In the Description field, type a description that is meaningful to you or your users.
This description appears in the Network Neighborhood window on client computers,
and is optional.
The Description cannot exceed 48 characters.
5 In the Computer Name field, type the server name you want users to see when they
connect.
The default name is the NetBIOS name of the Windows file server. The name should
contain no more than 15 characters, and no special characters or punctuation.
If practical, make the server name match its unqualified DNS host name. For example, if your DNS server has an entry for your server as “server.apple.com,” give your server the name “server.”
6 In the Workgroup field, type the name of the workgroup that you want users to see in the Network Neighborhood window.
If you have Windows domains on your subnet, use one of them as the workgroup
name to make it easier for clients to communicate across subnets. Otherwise, consult
your Windows network administrator for the correct group name.
The workgroup name cannot exceed 15 characters.
From the Command Line
You can also change the Windows service settings by modifying the serveradmin
command in Terminal. For more information, see the file services chapter of the
command-line administration guide.
PAGE 60:
"Changing Advanced Settings
You can use the Advanced pane of the Windows service settings in Server Admin to
choose a client code page, set the server to be a workgroup or domain master browser,
specify the server’s WINS registration, and enable virtual share points for user homes.
To configure Windows services Advanced settings:
1 Open Server Admin and select Windows in the Computers & Services list.
2 Click Settings, then click Advanced.
3 Choose the character set you want clients to use from the Code Page pop-up menu.
4 Next to Services, choose whether to enable domain browsing services.
“Workgroup Master Browser” provides browsing and discovery of servers in a single subnet.
“Domain Master Browser” provides browsing and discovery of servers across subnets.
5 Next to WINS Registration, choose how you want the server to register with WINS.
Choose “Off” to prevent your server from registering itself with any external WINS
server or local name resolution server.
Choose “Enable WINS server” to have the file server provide local name resolution
services. This allows clients across multiple subnets to perform name/address
resolution.
Choose “Register with WINS server” if your Windows clients and Windows server are not
all on the same subnet, and your network has a WINS server. Then enter the IP address
or DNS name of the WINS server.
6 To simplify setting up share points for Windows user home directories, select “Enable virtual share points.”
When you enable virtual share points, home directories are mounted automatically
when Windows users log in to the server, without you having to set up individual share points for each of your users.
From the Command Line
You can also change the Windows service settings using the serveradmin command
in Terminal. For more information, see the file services chapter of the command-line
administration guide."
Page 64
"Enabling Domain Browsing
If there are no Microsoft servers on your subnet or network to control domain
browsing, you can use these options to restrict domain browsing to a single subnet or
allow browsing across your network.
To enable domain browsing:
1 Open Server Admin and select Windows in the Computers & Services list.
2 Click Settings, then click Advanced.
3 Next to Services, select Workgroup Master Browser, Domain Master Browser, or both.
Select Master Browser to let clients browse for and locate servers in a single subnet.
Select Domain Master Browser to let clients browse for and locate servers across your
network (subnets).
4 Click Save."
Page 67 - HOW TO CONNECT USING WINDOWS NETWORK NEIGHBORHOOD:
"Connecting to the Server Using Network Neighborhood
Before trying to connect to the server from a Windows client computer, find out the
workgroup or domain of both the client computer and the file server.
You can find the workgroup name of a Windows client computer in the computer’s
Network Neighborhood window. To find the server’s workgroup name, open Server
Admin, click Windows in the Computers & Services list, click Settings, then click
General.
To connect to a Windows server using the Network Neighborhood:
1 On the Windows client computer, open the Network Neighborhood window. If you are
in the same workgroup or domain as the server, skip to step 4.
2 Double-click the Entire Network icon.
3 Double-click the icon of the workgroup or domain the server is located in.
4 Double-click the server’s icon.
5 Log in using your Windows login name.
Connecting to the Server by Name or Address in Windows
You can connect to the Windows server by double-clicking its name in the Network
Neighborhood. You can also connect without using the Network Neighborhood.
To connect to the Windows server without the Network Neighborhood:
1 On the Windows client computer, choose Start > Find > Computer.
2 Type the name or IP address of your Windows server.
3 Double-click the server to connect.
4 Log in using your Mac OS X Server login name."
The full PDF can be found at - http://a1872.g.akamai.net/7/1872/51/90d4af5d78e651/www.apple.com/server/pdfs/File_Services.pdf
______
Once we can log on to the PDC, the following discussion discusses how to modify registry to make things easier for users:
http://discussions.info.apple.com/WebX?128@@.6891391b
I found the following helpful discussions:
- http://discussions.info.apple.com/webx?13@206.RzcIaN89vNW.7@.68998011/0 - discusses how to do it:
"On your server, configure Windows services as a PDC (Primary Domain Controller) and define a domain.
At your PC, logon as as administrator and go to Network Neighborhood and see if you can see the domain. If you can, you need to set the PC up to access the domain. On W2K, it's My Computer/Properties/ Network Identification. Click on "Properties" and check Domain and enter the OSX PDC domain name. You will be asked to logon to the OSX server (admin) and after a long minute you should receive a message, "Welcome to XXXXXXX Domain". You will be prompted to reboot.
At the logon screen, enter a OSX username (long name or short name) / password. Make sure you enter the domain you wish to enter. If you don't see a "Log on to ________" box, select options and then select the domain. This should get you on the server.
To verify, open My Computer and you should have a H: drive assigned with the shortname of the user you signed on as. "
______
More detailed information comes from the File Services Administration manual from Apple on pages 55 - 72 :
"Changing General Settings
You can use the General pane of the Windows service settings in Server Admin to
provide a server description, name, and workgroup and specify the server’s role in its domain.
To configure Windows service General settings:
1 Open Server Admin and select Windows in the Computers & Services list.
2 Click Settings, then click General.
3 To specify how your server participates in the local domain, choose from the Role popup menu.
4 In the Description field, type a description that is meaningful to you or your users.
This description appears in the Network Neighborhood window on client computers,
and is optional.
The Description cannot exceed 48 characters.
5 In the Computer Name field, type the server name you want users to see when they
connect.
The default name is the NetBIOS name of the Windows file server. The name should
contain no more than 15 characters, and no special characters or punctuation.
If practical, make the server name match its unqualified DNS host name. For example, if your DNS server has an entry for your server as “server.apple.com,” give your server the name “server.”
6 In the Workgroup field, type the name of the workgroup that you want users to see in the Network Neighborhood window.
If you have Windows domains on your subnet, use one of them as the workgroup
name to make it easier for clients to communicate across subnets. Otherwise, consult
your Windows network administrator for the correct group name.
The workgroup name cannot exceed 15 characters.
From the Command Line
You can also change the Windows service settings by modifying the serveradmin
command in Terminal. For more information, see the file services chapter of the
command-line administration guide.
PAGE 60:
"Changing Advanced Settings
You can use the Advanced pane of the Windows service settings in Server Admin to
choose a client code page, set the server to be a workgroup or domain master browser,
specify the server’s WINS registration, and enable virtual share points for user homes.
To configure Windows services Advanced settings:
1 Open Server Admin and select Windows in the Computers & Services list.
2 Click Settings, then click Advanced.
3 Choose the character set you want clients to use from the Code Page pop-up menu.
4 Next to Services, choose whether to enable domain browsing services.
“Workgroup Master Browser” provides browsing and discovery of servers in a single subnet.
“Domain Master Browser” provides browsing and discovery of servers across subnets.
5 Next to WINS Registration, choose how you want the server to register with WINS.
Choose “Off” to prevent your server from registering itself with any external WINS
server or local name resolution server.
Choose “Enable WINS server” to have the file server provide local name resolution
services. This allows clients across multiple subnets to perform name/address
resolution.
Choose “Register with WINS server” if your Windows clients and Windows server are not
all on the same subnet, and your network has a WINS server. Then enter the IP address
or DNS name of the WINS server.
6 To simplify setting up share points for Windows user home directories, select “Enable virtual share points.”
When you enable virtual share points, home directories are mounted automatically
when Windows users log in to the server, without you having to set up individual share points for each of your users.
From the Command Line
You can also change the Windows service settings using the serveradmin command
in Terminal. For more information, see the file services chapter of the command-line
administration guide."
Page 64
"Enabling Domain Browsing
If there are no Microsoft servers on your subnet or network to control domain
browsing, you can use these options to restrict domain browsing to a single subnet or
allow browsing across your network.
To enable domain browsing:
1 Open Server Admin and select Windows in the Computers & Services list.
2 Click Settings, then click Advanced.
3 Next to Services, select Workgroup Master Browser, Domain Master Browser, or both.
Select Master Browser to let clients browse for and locate servers in a single subnet.
Select Domain Master Browser to let clients browse for and locate servers across your
network (subnets).
4 Click Save."
Page 67 - HOW TO CONNECT USING WINDOWS NETWORK NEIGHBORHOOD:
"Connecting to the Server Using Network Neighborhood
Before trying to connect to the server from a Windows client computer, find out the
workgroup or domain of both the client computer and the file server.
You can find the workgroup name of a Windows client computer in the computer’s
Network Neighborhood window. To find the server’s workgroup name, open Server
Admin, click Windows in the Computers & Services list, click Settings, then click
General.
To connect to a Windows server using the Network Neighborhood:
1 On the Windows client computer, open the Network Neighborhood window. If you are
in the same workgroup or domain as the server, skip to step 4.
2 Double-click the Entire Network icon.
3 Double-click the icon of the workgroup or domain the server is located in.
4 Double-click the server’s icon.
5 Log in using your Windows login name.
Connecting to the Server by Name or Address in Windows
You can connect to the Windows server by double-clicking its name in the Network
Neighborhood. You can also connect without using the Network Neighborhood.
To connect to the Windows server without the Network Neighborhood:
1 On the Windows client computer, choose Start > Find > Computer.
2 Type the name or IP address of your Windows server.
3 Double-click the server to connect.
4 Log in using your Mac OS X Server login name."
The full PDF can be found at - http://a1872.g.akamai.net/7/1872/51/90d4af5d78e651/www.apple.com/server/pdfs/File_Services.pdf
______
Once we can log on to the PDC, the following discussion discusses how to modify registry to make things easier for users:
http://discussions.info.apple.com/WebX?128@@.6891391b
Feed Burner RSS and ATOM feed of this Blog
http://feeds.feedburner.com/LaraHillsReflectionsOnTechnologyAndEducation
Mailman on Mac OS X Server Not Receiving Mail for Lists
When I created a few mailing list groups on my Mac OS X Server mailman using the Web Page admin at http://mail.haddon.k12.nj.us/mailman/admin - I am receiving emails from the server, but I am not able to send back to the mailing list.
Here is the error message I receive in the returned email:
A message (from) was received at 5 Sep 2004 16:42:59 +0000.
The following addresses had delivery problems:
Permanent Failure: 550_:_User_unknown_in_local_recipient_table
Delivery last attempted at Sun, 5 Sep 2004 16:43:01 -0000
I found some information, that I am including below:
At Apple Discussions for Mail Services / Mailman, I found this discussion - http://discussions.info.apple.com/webx?14@@.6896bbc9 - that recommends a terminal command to resolve a domain name issue in mailman's configuration file.
I also found this kbase document:
"We hit a Bug" message when creating a Mailing List: http://docs.info.apple.com/article.html?artnum=107889
Mac OS X Server 10.3 includes a Web interface for mailing list administration. If you create a new mailing list with this tool, you may see a message that says, "We're sorry, we hit a bug!"
This Mailman interface is available at http://myserver.com/mailman/admin, where "myserver.com" would be replaced with the address of your server.
When you try to save a new mailing list, you see this message:
Bug in Mailman version 2.1.2
We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks!
This message is followed by a detailed traceback.
To resolve the issue, follow these steps:
Open Terminal (/Applications/Utilities/).
Type: sudo chmod g+w /var/mailman/data/aliases.db
Press Return.
Use Server Admin to remove the partialy created list.
Here is the error message I receive in the returned email:
A message (from
The following addresses had delivery problems:
Permanent Failure: 550_
Delivery last attempted at Sun, 5 Sep 2004 16:43:01 -0000
I found some information, that I am including below:
At Apple Discussions for Mail Services / Mailman, I found this discussion - http://discussions.info.apple.com/webx?14@@.6896bbc9 - that recommends a terminal command to resolve a domain name issue in mailman's configuration file.
I also found this kbase document:
"We hit a Bug" message when creating a Mailing List: http://docs.info.apple.com/article.html?artnum=107889
Mac OS X Server 10.3 includes a Web interface for mailing list administration. If you create a new mailing list with this tool, you may see a message that says, "We're sorry, we hit a bug!"
This Mailman interface is available at http://myserver.com/mailman/admin, where "myserver.com" would be replaced with the address of your server.
When you try to save a new mailing list, you see this message:
Bug in Mailman version 2.1.2
We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks!
This message is followed by a detailed traceback.
To resolve the issue, follow these steps:
Open Terminal (/Applications/Utilities/).
Type: sudo chmod g+w /var/mailman/data/aliases.db
Press Return.
Use Server Admin to remove the partialy created list.
Subscribe to:
Posts (Atom)
Posts
