Sponsored Content
Operating Systems Solaris Problems connecting Solaris 10 to network via ISP Post 59513 by rhfrommn on Tuesday 21st of December 2004 04:09:27 PM
Old 12-21-2004
Your netgear router is almost certainly set up to give your computers DHCP assigned addresses. That 214.159 address given by your ISP is going to be the IP address of the router itself (and it is probably dynamic too).

But your Solaris setup is what you would do if you were setting up a static IP on the solaris box. This is very likely to be the problem. I've not set up DHCP on Solaris before so I don't know the answer off the top of my head - but I know I've contributed to other threads where I copied in text from Solaris manuals to tell somebody how to do it.

Do a search on this site for "Solaris dhcp" or something like that and I'm sure you'll turn up some info.
 

10 More Discussions You Might Find Interesting

1. Solaris

Connecting Solaris to Airport network

Hi, I've been trying to find out for the past two days how to set my Solaris 10 to join wireless network (Airport base station with ACL and wep or wpa on). Using ethernet is a bit out of question as I don't have an ethernet cable that would reach the other side of the house. Solaris 10... (1 Reply)
Discussion started by: giax
1 Replies

2. Programming

tcp server listening, client connecting problems

hello everyone. I tried searching for something related to this, but I figured it was time to ask my own question. I am experiencing these problems using Ubuntu 7.04 I am starting up a TCP listener/server and once connected, will act as a communication/control link with a program on another... (3 Replies)
Discussion started by: pjwhite
3 Replies

3. HP-UX

Connecting To An External Network Using A logical (PACKAGE) IP Address

Hie everyone, I am currently facing a problem whereby I can not connect to an external network from a package ip address on a HP-UX cluster. Below is the illustration: Primary Server IP Address : n.n.n.202 Secondary Server IP Address : n.n.n.212 Package IP Address : n.n.n.211 ... (1 Reply)
Discussion started by: cchilenga
1 Replies

4. HP-UX

Remotely connecting to HP-UX poses a lot of problems

1)MY HP-UX11iv2 machine is on a specific subnet as in rrr.rr.199.( its a rp3410 blade server).It has 2 hard disks one of them has HP-UX11iv2 and the other hard disk is not being used 2)ip of the hp-ux machine is rrr.rr.199.rrr 3)i need to access this hp-ux machine remotely from a windows machine... (3 Replies)
Discussion started by: rookie8278
3 Replies

5. UNIX for Dummies Questions & Answers

Problems connecting to the Internet

I am trying to connect a Solaris 10 PC to the internet via a Linksys router and a cable modem. I have tried following suggestions in one of the posts here for manual setup but so far no luck. Does the Solaris 10 install for x86 automatically pick up the internet connection? Dave :>) (4 Replies)
Discussion started by: dohling
4 Replies

6. IP Networking

Connecting to an SSN from an internal network

Hi I have an Apache Web server running on a Solaris 8 box that sits on a SSN. I have one desktop that connects to the SSN from the internal network and is recognised directly without using the gateway, all other desktops, laptops from inside the internal network connect to the SSN using the... (0 Replies)
Discussion started by: Bobby76
0 Replies

7. IP Networking

Connecting to DHCP network with Realtek interface

I have a Realtek 8139 interface in one of my machines and it will not connect to the network. /etc/rc.conf contains ifconfig_rl0="DHCP" and "rl0" was obtained from a dmesg. A network interface restart yields the following: # /etc/rc.d/netif restart Stopping network: lo0 rl0 fwe0 plip0. rl0: no... (3 Replies)
Discussion started by: figaro
3 Replies

8. Shell Programming and Scripting

connecting to network, auto-entering info

Hey guys, I just started college a few days ago. To my dismay, my school has a very frustrating wireless network access system. Every time you want to use the network, you need to open up a browser and get re-directed to a login page. Every access, you need to reenter the same username and... (1 Reply)
Discussion started by: Chain Breaker
1 Replies

9. AIX

problems connecting with exceed (solved)

Hi, We have a user who cannot connect to the aix system anymore with hummingbird exceed. Our unix servers are aix 5.3. She is running windows xp and using hummingbird 12. She used to not have any problem, but now when she tries to use xstart she gets an error 'unable to connect to host using... (0 Replies)
Discussion started by: fwellers
0 Replies

10. Red Hat

Connecting using SSH in WAN network

i have been learning linux from some time for linux plus exam and learned SSH protocol and have practised to connect to remote computer within Lan network and able to sucesssfully connect it . using ssh username@hostname But i wish to ask how do i use same ssh protocol to connect to other ... (6 Replies)
Discussion started by: lobsang
6 Replies
in.rdisc(1M)						  System Administration Commands					      in.rdisc(1M)

NAME
in.rdisc, rdisc - network router discovery daemon SYNOPSIS
/usr/sbin/in.rdisc [-a] [-f] [-s] [send-address] [receive-address] /usr/sbin/in.rdisc -r [-p preference] [-T interval] [send-address] [receive-address] DESCRIPTION
in.rdisc remains part of the software distribution of the Solaris Operating Environment. It is, however, not used by default. in.routed(1M) includes the functionality provided by in.rdisc. See routeadm(1M) for details of how to specify the IPV4 routing daemon. in.rdisc implements the ICMP router discovery protocol. The first form of the command is used on hosts and the second form is used on routers. in.rdisc can be invoked in either the first form (host mode) or second form (router mode). On a host, in.rdisc populates the network routing tables with default routes. On a router, advertises the router to all the hosts. Host (First Form) On a host, in.rdisc listens on the ALL_HOSTS (224.0.0.1) multicast address for ROUTER_ADVERTISE messages from routers. The received mes- sages are handled by first ignoring those listed router addresses with which the host does not share a network. Among the remaining addresses, the ones with the highest preference are selected as default routers and a default route is entered in the kernel routing table for each one of them. Optionally, in.rdisc can avoid waiting for routers to announce themselves by sending out a few ROUTER_SOLICITATION messages to the ALL_ROUTERS (224.0.0.2) multicast address when it is started. A timer is associated with each router address. The address will no longer be considered for inclusion in the routing tables if the timer expires before a new advertise message is received from the router. The address will also be excluded from consideration if the host receives an advertise message with the preference being maximally negative or with a lifetime of zero. Router (Second Form) When in.rdisc is started on a router, it uses the SIOCGIFCONF ioctl(2) to find the interfaces configured into the system and it starts lis- tening on the ALL_ROUTERS multicast address on all the interfaces that support multicast. It sends out advertise messages to the ALL_HOSTS multicast address advertising all its IP addresses. A few initial advertise messages are sent out during the first 30 seconds and after that it will transmit advertise messages approximately every 600 seconds. When in.rdisc receives a solicitation message, it sends an advertise message to the host that sent the solicitation message. When in.rdisc is terminated by a signal, it sends out an advertise message with the preference being maximally negative. OPTIONS
-a Accept all routers independent of the preference they have in their advertise messages. Normally, in.rdisc only accepts (and enters in the kernel routing tables) the router or routers with the highest preference. -f Run in.rdisc forever even if no routers are found. Normally, in.rdisc gives up if it has not received any advertise message after soliciting three times, in which case it exits with a non-zero exit code. If -f is not specified in the first form then -s must be specified. -r Act as a router, rather than a host. -s Send three solicitation messages initially to quickly discover the routers when the system is booted. When -s is specified, in.rdisc exits with a non-zero exit code if it can not find any routers. This can be overridden with the -f option. -p preference Set the preference transmitted in the solicitation messages. The default is zero. -T interval Set the interval between transmitting the advertise messages. The default time is 600 seconds. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWroute | +-----------------------------+-----------------------------+ SEE ALSO
in.routed(1M), routeadm(1M), ioctl(2), gateways(4), attributes(5), icmp(7P), inet(7P) Deering, S.E., editor, ICMP Router Discovery Messages, RFC 1256, Network Information Center, SRI International, Menlo Park, California, September 1991. SunOS 5.10 5 Nov 2004 in.rdisc(1M)
All times are GMT -4. The time now is 09:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy