Question about Operating Systems

1 Answer

Siemens gr40 120a

Its this is load sharing per module,if the module is defective can i insert another module,without configuration.

Posted by on

1 Answer

  • Level 3:

    An expert who has achieved level 3 by getting 1000 points


    An expert that got 20 achievements.


    An expert that got 10 achievements.


    An expert that got 5 achievements.

  • Master
  • 2,427 Answers
Re: siemens gr40 120a - Operating Systems

Yeah you should be able to

Posted on Dec 30, 2007

Add Your Answer

0 characters

Uploading: 0%


Complete. Click "Add" to insert your video. Add


3 Points

Related Questions:

1 Answer

Enable ICS on a windows Vista Home Premium Machine(Dell)

- Configuration on the machine that is connected to the internet.Firstly make sure that firewall on the machine is configured to allow ICMP and access to HTTP / HTTPS. Also make sure that the port 80 is opened on the firewall
To enable ICS perform the below steps - Identify the Dial-up connection that has to be shared - Right Click on the Dialup connection and go to properties, in the sharing tab enable ICS and choose the connection through which you would share the internet to your network.
- Configuration on the Client Machines
Connect the other computer to this one
You should be good to go now.
* I am assuming that you are not using a router or a hub, it is a direct connection.

Apr 04, 2011 | Microsoft Windows Vista Home Premium with...


How to share Speakers via Network

SpeakerShare is a practical and reliable Java based application that helps you to share the connected speaker with other computers effortlessly.

It is able to transfer sounds in uncompressed PCM format (also known as Pulse-code modulation) used to represent sampled analog signals.

The main window of the application is very simple and easy to work with. You can navigate between two tabs, namely 'Use' and 'Share' and let other computers to connect to your speakers immediately.

The Use tab of the application enables you to choose the mixer you are interested in such as headphones, speakers and port capture microphones. The 'Speaker' section allows you to view the name of the computer you want to share your speakers from.

By accessing the Share tab, you can easily choose the mixer you are interested in, then press the 'Share' button. After that, you can preview all the available PCs in the Speaker section so you need to use this tab firstly in order to configure the application properly.

The 'Connected Client' allows you to view all the connected computers to your speakers so you can rest assured that you will know which PC uses your shared speakers.

However, a drawback of SpeakerShare is that it does not allow you to manage all the connected computers the way you want, such as removing them from the list and restricting their access to your speakers.

Considering all of the above, SpeakerShare is a useful and effective program that comes in handy for users who need to let other computers to connect to their speakers by sharing them with ease.

It Runs on: Windows All

Some alternatives are :- Airfoil, WiFi2HiFi

Speakershare Download

on Feb 18, 2015 | Microsoft Operating Systems

1 Answer

How can i set up network file sharing

First step is to check if the file sharing option is checked in my computer folder options.

Start- My computer- TOOLS - FOLDER OPTIONS- and click on the second tab VIEW- scroll down to the last option which will show as USE SIMPLE FILE SHARING.

Level 1: My Documents (Private) loadTOCNode(3, 'moreinformation'); The owner of the file or folder has read and write permission to the file or folder. Nobody else may read or write to the folder or the files in it. All subfolders that are contained in a folder that is marked as private remain private unless you change the parent folder permissions.

If you are a Computer Administrator and create a user password for your account by using the User Accounts Control Panel tool, you are prompted to make your files and folder private.

Note The option to make a folder private (Level 1) is available only to a user account in its own My Documents folder.

To configure a folder and all the files in it to Level 1, follow these steps:
  1. Right-click the folder, and then click Sharing and Security.
  2. Select the Make this Folder Private check box, and then click OK.
Local NTFS Permissions:
  • Owner: Full Control
  • System: Full Control
Network Share Permissions:
  • Not Shared
Level 2 (Default): My Documents (Default) loadTOCNode(3, 'moreinformation'); The owner of the file or folder and local Computer Administrators have read and write permission to the file or folder. Nobody else may read or write to the folder or the files in it. This is the default setting for all the folders and files in each user's My Documents folder.

To configure a folder and all the files in it to Level 2, follow these steps:
  1. Right-click the folder, and then click Sharing and Security.
  2. Make sure that both the Make this Folder Private and the Share this folder on the network check boxes are cleared, and then click OK.
Local NTFS Permissions:
  • Owner: Full Control
  • Administrators: Full Control
  • System: Full Control
Network Share Permissions:
  • Not Shared
Level 3: Files in shared documents available to local users loadTOCNode(3, 'moreinformation'); Files are shared with users who log on to the computer locally. Local Computer Administrators can read, write, and delete the files in the Shared Documents folder. Restricted Users can only read the files in the Shared Documents folder. In Windows XP Professional, Power Users may also read, write, or delete any files in the Shared Documents Folder. The Power Users group is available only in Windows XP Professional. Remote users cannot access folders or files at Level 3. To allow remote users to access files, you must share them out on the network (Level 4 or 5).

To configure a file or a folder and all the files in it to Level 3, start Microsoft Windows Explorer, and then copy or move the file or folder to the Shared Documents folder under My Computer.

Local NTFS Permissions:
  • Owner: Full Control
  • Administrators: Full Control
  • Power Users: Change
  • Restricted Users: Read
  • System: Full Control
Network Share Permissions:
  • Not Shared
Level 4: Shared on the Network (Read-Only) loadTOCNode(3, 'moreinformation'); Files are shared for everyone to read on the network. All local users, including the Guest account, can read the files. But they cannot modify the contents. Any user can read and change your files.

To configure a folder and all the files in it to Level 4, follow these steps:
  1. Right-click the folder, and then click Sharing and Security.
  2. Click to select the Share this folder on the network check box
  3. Click to clear the Allow network users to change my files check box, and then click OK.
Local NTFS Permissions:
  • Owner: Full Control
  • Administrators: Full Control
  • System: Full Control
  • Everyone: Read
Network Share Permissions:
  • Everyone: Read
Level 5: Shared on the network (Read and Write) loadTOCNode(3, 'moreinformation'); This level is the most available and least secure access level. Any user (local or remote) can read, write, change, or delete a file in a folder shared at this access level. We recommend that this level be used only for a closed network that has a firewall configured. All local users including the Guest account can also read and modify the files.

To configure a folder and all the files in it to Level 5, follow these steps:
  1. Right-click the folder, and then click Sharing and Security
  2. Click to select the Share this folder on the network check box, and then click OK.
Local NTFS Permissions:
  • Owner: Full Control
  • Administrators: Full Control
  • System: Full Control
  • Everyone: Change
Network Share Permissions:
  • Everyone: Full Control
Note All NTFS permissions that refer to Everyone include the Guest account.

All the levels that this article describes are mutually exclusive. Private folders (Level 1) cannot be shared unless they are no longer private. Shared folders (Level 4 and 5) cannot be made private until they are unshared.

If you create a folder in the Shared Documents folder (Level 3), share it on the network, and then allow network users to change your files (Level 5), the permissions for Level 5 are effective for the folder, the files in that folder, and the subfolders. The other files and folders in the Shared Documents folder remain configured at Level 3.

Jul 20, 2010 | Microsoft Windows Vista Ultimate Edition

1 Answer

Not able to use internet in Red Hat Linux (RHEL 5)

- What make/model of NIC?

- Cable or DSL Internet access?

- Is there a router in the picture, or does the computer connect directly to your cable/dsl modem?

- Are you using DHCP or static IP assignment?

If you're using static IP addressing, check out some of the suggestions in this article:

Created: 9/05/02 Revised: 4/6/04

Basic PCI Network Interface Card (NIC) Configuration and Troubleshooting:

As different distros use different GUI (graphical) network configuration programs, the following instructions are
command-line based, and as such should work for most distros. If you boot directly into the GUI (KDE, Gnome, etc.)
as opposed to booting into a non-graphical runlevel, open a terminal window and type the given commands from there.
Much of the following can only be done as root, so either log in as root, or "su" to root if logged in as a non-root user.

*Note: some commands can only be run from root's login shell. When the su command is used by itself, it allows a non-root
user to become root, but only from within the user's own login shell. To gain a full root login shell without having to log out
and log back in as root, use the "-" option when issuing the su command: su - .

If you have only 1 NIC installed, it will be designated "eth0"; additional NICs will be designated eth1, eth2, etc.

Before doing any of the following, *please* check the Hardware Compatibility List at your distro's support site.
If your particular make/model of NIC is not listed as being compatible with your distro, there is good chance that
it may not work at all, or that you may have to take extra steps (such as downloading a special driver/module) in
order to get it working. Considering the fact that NICs are fairly inexpensive, it is often just not worth spending
time and energy trying to "force" an unsupported card to work.

1. If, on bootup, you see a message similar to "Bringing up interface eth0: FAILED", it is very possible that you have
a resource (IRQ or I/O address) conflict. Turn off Plug-N-Play support in your BIOS before proceeding further; BIOS PNP
can often cause problems with PCI devices under a non-Windows OS. If you dual-boot Windows and Linux, don't worry- your
PCI devices should still work in Windows with BIOS PNP disabled, as the PNP functionality of the Windows OS itself will
perform the necessary resource allocation.

*Note: If you are connecting to a network or ISP via DHCP, and you see a message on bootup similar to "Determining IP
information for device eth0: FAILED", that can indicate a problem with your DHCP configuration (or the DHCP server)
This article doesn't deal with DHCP issues, but I hope to be able to post one that does in the future.

2. Use one of the following commands to verify that your card is at least basically identifying itself to the system:

lspci -vv |less
less /proc/pci
cat /proc/pci

In the resulting output, look for the "Ethernet Controller" entry. It should contain information about your model of card
and/or its chipset, as well as IRQ, I/O port, and memory address values.

3. Run the ifconfig command; information concerning your NIC should appear in the resulting output. You should also
see stats for the loopback (lo) device If you've already tried to enter your IP info (inet addr, Bcast, Mask)
through a GUI network configuration utility, verify that those values are correctly reflected in ifconfig's output. Also
check for RX/TX errors and collisions. If eth0 is not listed when you run ifconfig, try "ifconfig -a"; the "-a" option forces
ifconfig to report all network interfaces, active or not. If eth0 appears only when you run ifconfig with the -a option, it is
definitely not correctly configured.

4. Verify that the correct module is being loaded for your ethernet card by issuing the "lsmod" command; you should see the module
name in the resulting list of loaded modules. If not, issue the following two commands and try again:

depmod -ae
modprobe <name of your NIC's module>

*Note- documentation concerning module loading will often refer to the "insmod" command, but use modprobe instead if it's available.
Basically, insmod is not as "intelligent" as modprobe in the fact that it doesn't try to resolve module dependencies (where the
successful loading of a given module "depends" on another module being loaded first).

If the module appears as loaded after that, check your /etc/modules.conf (/etc/conf.modules in some distros)file to make sure that it has
an entry for the module; this will load the module automagically each time you boot. The line will look like this:

alias eth0 <name of your NIC's module>

If the line doesn't exist, add it by editing the file with your favorite text editor.

5. Run the following two commands:

less /proc/interrupts
less /proc/ioports

For the first command, note the IRQ assigned to eth0; verify that it matches the Interrupt value listed when you ran the ifconfig
command, and note if the assigned interrupt is being shared with another device. If so, this doesn't necessarily indicate a problem,
but it can.
For the second command, make sure that the address range of your Ethernet controller doesn't conflict with/overlap that of another
device. Also make sure that the start of the address range corresponds to the Base address value shown for eth0 when you ran ifconfig.

6. If any of the above steps yield errors or indicate conflicts even after you've turned off PNP support in the BIOS, try physically
rearranging the slot order of your PCI cards; doing so can force a reallocation of resources to devices on the PCI bus.

7. Once you're sure that the NIC is correctly configured and the module is properly loaded, you can try to bring the card up with
the following command:

ifconfig eth0 <the NIC's IP address> netmask <the appropriate netmask> up

If you get no errors, you should at least then be able to ping the IP address of the NIC.


Distro-specific configuration files:


Redhat, Mandrake, and a few other distros use the following two basic network interface configuration files:


The format of the files may vary slightly across distros/versions, but the the pertinent contents of the files should be very similar to:


DOMAINNAME="your_domain_name" ("localhost" is valid here)
GATEWAY="IP_address_of_your_gateway_machine/device" (if applicable)




An explanation of IP addressing as a whole (including terms such as "netmask", "network address", "broadcast address",etc.) is well beyond
the scope of this Help File. However, the following sites provide some good background information:


- Further resources, including NIC driver source code and diagnostic utilities can be found at
* Note that as of 3/04 the Scyld site appears to have undergone changes; some links on the above page are broken.


#include <disclaimer.h>

This is, as a whole, a work in progress. It might (and probably does) contain omissions and/or slight inaccuracies.
However, none of the suggestions given here will do any harm to your system if performed correctly.

Being a work in progress, any suggestions/corrections/critcisms are more than welcome. If you've noticed any errors in the above,
or just have something constructive to suggest, feel free to email me:

Jul 02, 2009 | Red Hat Enterprise Linux ES Basic Edition

2 Answers

Pc configuration


The below mentioned software would be useful for you

If you want configuration, kindly mentioned the stuff like you want configuration for firewall etc...


Apr 28, 2009 | Operating Systems

1 Answer

Loading Vista

for getting windows vista installed on the machine you should have the configuration of 1gb ram , 1 ghz of processor and 100 gb of hard drive if that is there then you must get it installed without any issues . If this is not the configuration then you should have this configuration first and then get it installed

Mar 31, 2009 | Operating Systems

1 Answer

Configuring clint vista to use shared internet in a LAN

The Internet connection must be shared for you to use it. You probably haven't configured your vista correctly. Try connecting via your internet connection (Networking)

Feb 27, 2009 | Microsoft Windows Vista Home Basic for PC

1 Answer

My Drives (c& D) alwasys get shared with C$ adn D$

This is administrative share which is enable by default. If you want to disable it, you have to configure some setting in Registry. (Only do it if you are advance user).
1) Click Start , then Run, type in 'Regedit' .
Expand My Computer -- > HKEY_LOCAL_MACHINE --> SYSTEM --> CurrentControlSet --> Services --> lanmanserver --> parameters
In the right panel, look for AutoShareWks, right click on it and change the value to '0' to disable the share.
** In case you want to enable the share back, change the value to 1.

Dec 04, 2008 | Microsoft Windows XP Professional

1 Answer

Internate sharing close in day maximum 5 time or more

Nothing Put ur Client PC' s Default gate. And then DNS IP- Address as server's ip-Address.I thing this method may be already configured on ur Server. Not yet, Try it Now......

Nov 22, 2008 | Microsoft Windows Server Standard 2003 for...

1 Answer

How to configure samba server

Hi satveergaur

Follow these instruction to configure samba server

To configure Samba using a graphical interface, use the Samba Server Configuration Tool.

The Samba Server Configuration Tool is a graphical interface for managing Samba shares, users, and basic server settings. It modifies the configuration files in the /etc/samba/ directory. Any changes to these files not made using the application are preserved.

To use this application, you must be running the X Window System, have root privileges, and have the redhat-config-samba RPM package installed. To start the Samba Server Configuration Tool from the desktop, go to the Main Menu Button (on the Panel) => System Settings => Server Settings => Samba or type the command redhat-config-samba at a shell prompt (for example, in an XTerm or a GNOME terminal).

 Samba Server Configuration Tool

The Samba Server Configuration Tool does not display shared printers or the default stanza that allows users to view their own home directories on the Samba server.

 Configuring Server Settings

The first step in configuring a Samba server is to configure the basic settings for the server and a few security options. After starting the application, select Preferences => Server Settings from the pulldown menu. The Basic tab is displayed as shown in Figure 24-2.

 Configuring Basic Server Settings

On the Basic tab, specify which workgroup the computer should be in as well as a brief description of the computer. They correspond to the workgroup and server string options in smb.conf.

 Configuring Security Server Settings

The Security tab contains the following options:

Authentication Mode — This corresponds to the security option. Select one of the following types of authentication.

ADS — The Samba server acts as a domain member in an Active Directory Domain (ADS) realm. For this option, Kerberos must be installed and configured on the server, and Samba must become a member of the ADS realm using the net utility, which is part of the samba-client package. Refer to the net man page for details. This option does not configure Samba to be an ADS Controller.

Domain — The Samba server relies on a Windows NT Primary or Backup Domain Controller to verify the user. The server passes the username and password to the Controller and waits for it to return. Specify the NetBIOS name of the Primary or Backup Domain Controller in the Authentication Server field.

The Encrypted Passwords option must be set to Yes if this is selected.

Server — The Samba server tries to verify the username and password combination by passing them to another Samba server. If it can not, the server tries to verify using the user authentication mode. Specify the NetBIOS name of the other Samba server in the Authentication Server field.

Share — Samba users do not have to enter a username and password combination on a per Samba server basis. They are not prompted for a username and password until they try to connect to a specific shared directory from a Samba server.

User — (Default) Samba users must provide a valid username and password on a per Samba server basis. Select this option if you want the Windows Username option to work. Refer to Section Managing Samba Users for details.

Encrypt Passwords — This option must be enabled if the clients are connecting from a Windows 98, Windows NT 4.0 with Service Pack 3, or other more recent versions of Microsoft Windows. The passwords are transfered between the server and the client in an encrypted format instead of in as a plain-text word that can be intercepted. This corresponds to the encrypted passwords option. Refer to Section 24.2.3 Encrypted Passwords for more information about encrypted Samba passwords.

Guest Account — When users or guest users log into a Samba server, they must be mapped to a valid user on the server. Select one of the existing usernames on the system to be the guest Samba account. When guests logs in to the Samba server, they have the same privileges as this user. This corresponds to the guest account option.

After clicking OK, the changes are written to the configuration file and the daemon is restart; thus, the changes take effect immediately.

 Managing Samba Users

The Samba Server Configuration Tool requires that an existing user account be active on the system acting as the Samba server before a Samba user can be added. The Samba user is associated with the existing user account.

To add a Samba user, select Preferences => Samba Users from the pulldown menu, and click the Add User button. On the Create New Samba User window select a Unix Username from the list of existing users on the local system.

If the user has a different username on a Windows machine and will be logging into the Samba server from the Windows machine, specify that Windows username in the Windows Username field. The Authentication Mode on the Security tab of the Server Settings preferences must be set to User for this option to work.

Also configure a Samba Password for the Samba User and confirm the Samba Password by typing it again. Even if you select to use encrypted passwords for Samba, it is recommended that the Samba passwords for all users are different from their system passwords.

To edit an existing user, select the user from the list, and click Edit User. To delete an existing Samba user, select the user, and click the Delete User button. Deleting a Samba user does not delete the associated system user account.

The users are modified immediately after clicking the OK button.

Starting and Stopping the Server

On the server that is sharing directories via Samba, the smb service must be running.

View the status of the Samba daemon with the following command: /sbin/service smb status

Start the daemon with the following command: /sbin/service smb start

Stop the daemon with the following command: /sbin/service smb stop

To start the smb service at boot time, use the command: /sbin/chkconfig --level 345 smb on


Jun 06, 2008 | Operating Systems

Not finding what you are looking for?
Operating Systems Logo

Related Topics:

471 people viewed this question

Ask a Question

Usually answered in minutes!

Top Operating Systems Experts


Level 3 Expert

18257 Answers

Brian Sullivan
Brian Sullivan

Level 3 Expert

27725 Answers


Level 3 Expert

6993 Answers

Are you an Operating System Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides