Dell PowerVault 735N Service Manual page 20

Basic Troubleshooting: Dell PowerVault 735N Systems Service Manual
I have just finished using the
PowerVault Kick-Start utility.
After rebooting my system, the
system shuts down and
powers off.
I configured the system using
the Kick-Start utility. Now, I
cannot access the NAS
Manager using Microsoft
Internet Explorer.
I connected the network cable
but forgot to insert the Kick-
Start diskette before I powered
on the system. Can I still
configure my system with
Kick-Start?
From a Macintosh client, users
cannot modify or delete a file
previously accessed by a
Windows client.
I just created a new volume on
my system but I cannot see
file:///C:/Users/Phebega_Pericho/Desktop/spv735N/en/sm/basics.htm[3/15/2013 4:18:13 PM]
occur.
You left the PowerVault Kick-Start
diskette in the diskette drive.
The system may not be connected to
the network.
No. When Kick-Start booted up it did
not find a Kick-Start diskette or a
system running DHCP to obtain an
IP address. Microsoft Windows
Advanced Server assigned your
system an Autoconfiguration IP
address.
The time is not properly
synchronized between clients and
the system.
Terminal Services will not update the
system when a new volume is
1. Start the PowerVault 735N NAS
Manager.
2. Click on Maintenance.
3. Enter your user name and
password.
4. On the desktop, click on
Advanced Administration menu
icon.
2. Select System Settings—>
Network Properties.
3. Check the onboard NIC. If the
NIC is disabled, bind Services for
Macintosh to an enabled NIC.
Remove the diskette from the
diskette drive and power on the
system.
1. Make sure the system is
connected to the network.
2. Make sure you entered a
correct IP address in the Kick-Start
Application Menu.
3. If the problem persists, use the
serial port as described in the
System Setup Placemat to access
the NAS Manager and ensure that
the configuration settings are
correct.
Use the serial port as outlined in
the System Setup Placemat or the
User's Guide.
Make sure that the clients'
systems are synchronized within
ten minutes relative to the time
zone.
Exit from Terminal Services and
reconnect. The volume should now