Solairs TCP/IP Networking

makhalid-at-gmail.com wrote:

> In the command prompt if I type telnet://192.168.1.5 ...it would
> work...but if I type telnet://devhost..it doesnt work...


Did you try editing the Windows HOSTS file as originally suggested???

On Thu, 28 Jun 2007 11:17:39 -0400, Oscar del Rio wrote:

> makhalid-at-gmail.com wrote:
>
>> In the command prompt if I type telnet://192.168.1.5 ...it would
>> work...but if I type telnet://devhost..it doesnt work...
>
>
> Did you try editing the Windows HOSTS file as originally suggested???

That would require setting a static IP address for the Solaris machine
which for a Windows user is an "Ohhh, noess!. Easily accomplished,
however, by executing sys-unconfig and examining the router's
configuration to locate the unallocated DHCP pool addresses.

However, once accomplished, the HOSTS file in Windows is
C:\windows\system32\drivers\etc\hosts

On Jun 28, 12:45 pm, Dave Uhring wrote:
> On Thu, 28 Jun 2007 11:17:39 -0400, Oscar del Rio wrote:
> > makha...@gmail.com wrote:
>
> >> In the command prompt if I type telnet://192.168.1.5 ...it would
> >> work...but if I type telnet://devhost..it doesnt work...
>
> > Did you try editing the Windows HOSTS file as originally suggested???
>
> That would require setting a static IP address for the Solaris machine
> which for a Windows user is an "Ohhh, noess!. Easily accomplished,
> however, by executing sys-unconfig and examining the router's
> configuration to locate the unallocated DHCP pool addresses.
>
> However, once accomplished, the HOSTS file in Windows is
> C:\windows\system32\drivers\etc\hosts

Thanks for the reply....I donot want to edit the Windows Host
file...becuase if I want to connect to the Sun box from other network..
(WAN), I cannot do that right...so thought if I had a hostname, I can
connect to the hostname even from WAN ..from a different PC....Now I
feel that I'm having a wrong concept of the Host Name....Can I define
a host name of my own and put it on the network so that other pc's
from different networks can access it?

Thanks for all the ideas..

makhalid-at-gmail.com wrote:
> On Jun 28, 12:45 pm, Dave Uhring wrote:
>
>>On Thu, 28 Jun 2007 11:17:39 -0400, Oscar del Rio wrote:
>>
>>>makha...@gmail.com wrote:
>>
>>>>In the command prompt if I type telnet://192.168.1.5 ...it would
>>>>work...but if I type telnet://devhost..it doesnt work...
>>>
>>>Did you try editing the Windows HOSTS file as originally suggested???
>>
>>That would require setting a static IP address for the Solaris machine
>>which for a Windows user is an "Ohhh, noess!. Easily accomplished,
>>however, by executing sys-unconfig and examining the router's
>>configuration to locate the unallocated DHCP pool addresses.
>>
>>However, once accomplished, the HOSTS file in Windows is
>>C:\windows\system32\drivers\etc\hosts
>
>
> Thanks for the reply....I donot want to edit the Windows Host
> file...becuase if I want to connect to the Sun box from other network..
> (WAN), I cannot do that right...so thought if I had a hostname, I can
> connect to the hostname even from WAN ..from a different PC....Now I
> feel that I'm having a wrong concept of the Host Name....Can I define
> a host name of my own and put it on the network so that other pc's
> from different networks can access it?
>
> Thanks for all the ideas..
>

I'm afraid you do have the wrong concept of the hostname. Hostnames are
for human convenience. IP addresses are for machines. You normally use
something like the "hosts" file or a DNS server to translate.

You can telnet or ftp to mumble.somedomain.com and your machine
translates the name to the numeric address for you. You could simply
use the numeric address and the the machine would not care.

You'll find your "hosts" file in C:\WINDOWS\system32\drivers\etc\hosts

The format of the entries looks like this:


127.0.0.1 localhost
192.168.1.1 my_router
192.168.1.11 alpha5
192.168.1.12 alpha6
192.168.1.20 sunblok timehost
192.168.1.30 sunburn
192.168.1.31 sunbitch
192.168.1.32 sunspot
192.168.1.40 topper
192.168.1.99 LJ4000

Your hosts file is equivalent to the list of friend's and neighbor's
telephone numbers that you undoubtedly keep somewhere.

On Thu, 28 Jun 2007 18:31:49 -0400, Richard B. Gilbert wrote:

> Your hosts file is equivalent to the list of friend's and neighbor's
> telephone numbers that you undoubtedly keep somewhere.

The hosts file also has absolutely no effect on the ability of other hosts
to connect to the Solaris host. Solaris does not know nor care what you
do to your Windows box.

Dave Uhring wrote:
> On Thu, 28 Jun 2007 18:31:49 -0400, Richard B. Gilbert wrote:
>
>
>>Your hosts file is equivalent to the list of friend's and neighbor's
>>telephone numbers that you undoubtedly keep somewhere.
>
>
> The hosts file also has absolutely no effect on the ability of other hosts
> to connect to the Solaris host. Solaris does not know nor care what you
> do to your Windows box.
>

If you had been paying attention, you would have noticed that the OP was
having problems connecting FROM his Windows box! And the text you
neglected to quote made it quite clear that it was the hosts file on
Windows that I was talking about. If his Solaris box is not listed in
DNS, the host file is the only way he will ever connect to it by name
from a Windows machine!

On Thu, 28 Jun 2007 19:34:47 -0400, Richard B. Gilbert wrote:

> Dave Uhring wrote:
>> On Thu, 28 Jun 2007 18:31:49 -0400, Richard B. Gilbert wrote:

>> The hosts file also has absolutely no effect on the ability of other hosts
>> to connect to the Solaris host. Solaris does not know nor care what you
>> do to your Windows box.
>>
>
> If you had been paying attention, you would have noticed that the OP was
> having problems connecting FROM his Windows box! And the text you
> neglected to quote made it quite clear that it was the hosts file on
> Windows that I was talking about. If his Solaris box is not listed in
> DNS, the host file is the only way he will ever connect to it by name
> from a Windows machine!

I was commenting on a previous statement from the OP:

"Thanks for the reply....I donot want to edit the Windows Host
file...becuase if I want to connect to the Sun box from other network..
(WAN), I cannot do that right...so thought if I had a hostname, I can
connect to the hostname even from WAN ..from a different PC."

Dave Uhring wrote:
> On Thu, 28 Jun 2007 19:34:47 -0400, Richard B. Gilbert wrote:
>
>
>>Dave Uhring wrote:
>>
>>>On Thu, 28 Jun 2007 18:31:49 -0400, Richard B. Gilbert wrote:
>>
>
>>>The hosts file also has absolutely no effect on the ability of other hosts
>>>to connect to the Solaris host. Solaris does not know nor care what you
>>>do to your Windows box.
>>>
>>
>>If you had been paying attention, you would have noticed that the OP was
>>having problems connecting FROM his Windows box! And the text you
>>neglected to quote made it quite clear that it was the hosts file on
>>Windows that I was talking about. If his Solaris box is not listed in
>>DNS, the host file is the only way he will ever connect to it by name
>>from a Windows machine!
>
>
> I was commenting on a previous statement from the OP:
>
> "Thanks for the reply....I donot want to edit the Windows Host
> file...becuase if I want to connect to the Sun box from other network..
> (WAN), I cannot do that right...so thought if I had a hostname, I can
> connect to the hostname even from WAN ..from a different PC."
>

The OP seems to be more than a little confused about hostnames and
connecting to other systems over the network. A hostname is not a piece
of magic, it's just a name that you use to look up the the IP "phone
number" using either DNS or the hosts file. If he wants to connect by
name from a Windows box, an IP - hostname equivalence in the hosts file
is the way to go. Of course he could also register the Solaris system
in a DNS server but I don't want to even think about explaining that to
anyone at his level.

On Thu, 28 Jun 2007 21:05:44 -0400, Richard B. Gilbert wrote:

> Dave Uhring wrote:

>> I was commenting on a previous statement from the OP:
>>
>> "Thanks for the reply....I donot want to edit the Windows Host
>> file...becuase if I want to connect to the Sun box from other network..
>> (WAN), I cannot do that right...so thought if I had a hostname, I can
>> connect to the hostname even from WAN ..from a different PC."
>>
>
> The OP seems to be more than a little confused about hostnames and
> connecting to other systems over the network. A hostname is not a piece
> of magic, it's just a name that you use to look up the the IP "phone
> number" using either DNS or the hosts file. If he wants to connect by
> name from a Windows box, an IP - hostname equivalence in the hosts file
> is the way to go. Of course he could also register the Solaris system
> in a DNS server but I don't want to even think about explaining that to
> anyone at his level.

Bigadmin has a feature article on DNS which is fairly accurate. The only
obvious error is the author's wanting to use ndc on a BIND-9 server.

http://www.sun.com/bigadmin/features...s.html?biga=15

But that won't much help the OP in gaining access to the Solaris host from
the "WAN" - perhaps he means the Internet. I'm sure that his router's
DHCP server is allocating RFC1918 addresses and it's likely that the
router does not have a redirect capability.

On Jun 28, 11:19 pm, Dave Uhring wrote:
> On Thu, 28 Jun 2007 21:05:44 -0400, Richard B. Gilbert wrote:
> > Dave Uhring wrote:
> >> I was commenting on a previous statement from the OP:
>
> >> "Thanks for the reply....I donot want to edit the Windows Host
> >> file...becuase if I want to connect to the Sun box from other network..
> >> (WAN), I cannot do that right...so thought if I had a hostname, I can
> >> connect to the hostname even from WAN ..from a different PC."
>
> > The OP seems to be more than a little confused about hostnames and
> > connecting to other systems over the network. A hostname is not a piece
> > of magic, it's just a name that you use to look up the the IP "phone
> > number" using either DNS or the hosts file. If he wants to connect by
> > name from a Windows box, an IP - hostname equivalence in the hosts file
> > is the way to go. Of course he could also register the Solaris system
> > in a DNS server but I don't want to even think about explaining that to
> > anyone at his level.
>
> Bigadmin has a feature article on DNS which is fairly accurate. The only
> obvious error is the author's wanting to use ndc on a BIND-9 server.
>
> http://www.sun.com/bigadmin/features...s.html?biga=15
>
> But that won't much help the OP in gaining access to the Solaris host from
> the "WAN" - perhaps he means the Internet. I'm sure that his router's
> DHCP server is allocating RFC1918 addresses and it's likely that the
> router does not have a redirect capability.- Hide quoted text -
>
> - Show quoted text -

Thanks for all the replies.....Really appreciate it....
Let me know if what I inferred is right...
If I have a DNS server setup on my sun box and made an entry like
hostname ipaddress...Then I should be able to ping hostname from
other pc in the same network ..will this work?