Axis Communications 540+ Manual De Usuario

16

AXIS 540+/AXIS 560

1. Open a Terminal and enter the following commands: 

2. The host will return 

, or a similar message. This indicates 

that the address has been set and that communication is established. 

3. Log in to the print server’s Web pages (see 

Server Management, on page 87), select 

Detailed View | TCP/IP and define Default Router and Subnet Mask. Make 
sure you first set 

DHCP, Auto-IP, BOOTP and RARP (...Enabled) to No!

You have now successfully set the IP address of the print server. Continue to 
“Making Network Printers available for printing on your PC” on page 18.

AXIS IP JumpStarter is an application that assists in assigning an IP address to 
your print server and finding IP addresses already assigned to Axis servers.

1. Download and install AXIS IP JumpStarter. AXIS IP JumpStarter is 

available on www.axis.com

2. For optimal use, open AXIS IPJumpstarter before you attach the print server 

to the network.

•  When you execute the ping command for the first time, you will experience a significantly 

longer response time than is usual

.

•  The ability to set the IP address with ARP and PING will only be enabled the first 4 minutes 

after restarting the print server.

•  By using the 

arp -d

 command, the static entry in the arp table is removed from the 

host’s cache memory.

arp -s <IP address> <Ethernet address>
ping <IP address>

arp -s 192.168.3.191 00:40:8c:10:00:86
ping 192.168.3.191

•  If the host name has not been mapped to an IP address, simply replace the host name entry 

with the IP address.

•  The ARP command varies between different UNIX/Linux systems. Some BSD type systems 

expect the host name and node address in reverse order. Furthermore IBM AIX systems will 
require the additional argument 

ether

.

•  When you execute the 

ping

 command for the first time, you may experience a 

significantly longer response time than is usual

.

•  The ability to set the IP address with ARP and PING will only be enabled the first 4 minutes 

after restarting the print server