Network lost after reboot


 
Thread Tools Search this Thread
Operating Systems SCO Network lost after reboot
# 8  
Old 07-23-2007
Sorry for overlooking the first thing that came to mind, but I assume you've ensured that you have a default route added somewhere in a startup script in /etc/rc2.d ??

For instance:

route add default <gateway ip address>


Just making sure. Sometimes it's the obvious stuff that gets overlooked.
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Solaris

Changing "rx_queue_number" in "ixgbe.conf". Reboot or Network Restart?

Hi all, First post here. Working on Solaris 10, on a Sun t4-4, need to change RX queue depth(ethernet, not HBA) and was wondering if i could get by with just restarting the network or if i should just bounce the whole shebang. Apologies if i missed a similar thread. if there is one, please... (2 Replies)
Discussion started by: caspnx
2 Replies

2. IP Networking

Finding lost machine on network trouble

Couldn't find my PC on network. Root of evil the was in bad patch-cable. (0 Replies)
Discussion started by: useretail
0 Replies

3. UNIX for Dummies Questions & Answers

Will authconfig make permanent change or lost after reboot?

Hi, I made following configuration to create user directory: # authconfig --enablemkhomedir --update But the directory is created as permission 755, I'd like to modify the script to change directory access permission to 700, where is the script which copies /etc/skel to /home... (0 Replies)
Discussion started by: hce
0 Replies

4. SuSE

reboot and boot from network

Hello, Does any one know any command which reboot the system and select as boot device the network. I give bootnet to many servers at once and i want to avoid opening ILOM and select as boot device the network. Can i do it by just executing a command? Thanks in advance (2 Replies)
Discussion started by: @dagio
2 Replies

5. AIX

tuning network parameters : parameters not persist after reboot

Hello, On Aix 5.2, we changed the parameters tcp_keepinit, tcp_keepintvl and tcp_keepidle with the no command. tunrestore -R is present in inittab in the directory /etc/tunables we can clearly see the inclusion of parameters during reboot, including the file lastboot.log ... (0 Replies)
Discussion started by: dantares
0 Replies

6. Solaris

[help]network error after reboot server v890 sparc

hi expert, i had reinstall the sun v890 server solaris 8 and also do mirroring, i had configure the network for the server (hostname.eri0,hosts,netmasks,nodename,etc) after i reboot get and error messages below : Setting default IPv4 interface for multicast: add net 224.0/4: gateway... (5 Replies)
Discussion started by: bucci
5 Replies

7. Solaris

Network Connectivity lost after reboot

I have 4 V440 servers running Solaris 9. I have their interfaces configured (ce0) and have connectivity to our network. However, after reboot,...the connectivity is lost although the interface shows that its still up after an ifconfig -a. Only after I reconfigure the interface do I restore... (19 Replies)
Discussion started by: StorageGuy
19 Replies
Login or Register to Ask a Question
REBOOT(8)						      System Manager's Manual							 REBOOT(8)

NAME
reboot - reboot the system immediately SYNOPSIS
reboot [-f] DESCRIPTION
Reboot can be used to reboot the system after installing a new kernel. It does not inform the users, but does log it's actions in /usr/adm/wtmp and /usr/adm/authlog. The system is then rebooted with the reboot(2) systemcall. If the -f flag is not given then all processes are sent terminate signals to give them a chance to die peacefully before the reboot() call. If the wtmp file exists, reboot logs itself as if it were a shutdown. This is done to prevent last(1) from talking about system-crashes. Reboot is registered as is in the authlog file. Reboot can only be executed by the super-user. Any other caller will be refused, either by reboot(8) or by reboot(2). SEE ALSO
reboot(2), shutdown(8), halt(8), boot(8). BUGS
The error message's given by reboot are not always useful. There are several routines that can fail, but which are not fatal for the pro- gram. AUTHOR
Edvard Tuinder (v892231@si.hhs.NL) REBOOT(8)