asked on

Configure DNS Client to connceted to the Internet

I have a SUN WKS Solaris 2.6 & try to connect to the internet. I asked our DNS group to added my WKS to DNS. I can use DNS in the LAN environment, but I can't connect to the internet with netscpae. I am a stand alone wks & not part of any NIS group. The two files I configurated are NSSWITCH.CONF & RESOLV.CONF.

The configuration files for NSSWITCH.CONF & RESOLV.CONF

#
# /etc/nsswitch.files:
#
# An example file that could be copied over to /etc/nsswitch.conf; it
# does not use any naming service.
#
# "hosts:" and "services:" in this file are used only if the
# /etc/netconfig file has a "-" for nametoaddr_libs of "inet" transports.

passwd: files
group: files
hosts: files dns
networks: files
protocols: files
rpc: files
ethers: files
netmasks: files
bootparams: files
publickey: files
# At present there isn't a 'files' backend for netgroup; the system will
# figure it out pretty quickly, and won't use netgroups at all.
netgroup: files
automount: files
aliases: files
services: files
sendmailvars: files

RESOLV.CONF

domain fmr.com
nameserver 127.0.0.1
nameserver 137.199.36.20
nameserver 155.1.1.15
nameserver 155.200.144.15
nameserver 155.1.28.22

THX in Advance...

-VT

vctsang

ASKER

Edited text of question

vctsang

ASKER

Adjusted points to 100

ahoffmann

Can you ping your specified nameservers?
If so, does nslookup give you IP addresses for names?
If so, can you ping these names or IP addresses?
If not you have a routing problem, post result of:
netstat -rn

vctsang

ASKER

Thanks for your response ahoffmann.

I changed the Resolv.conf to match the DNS I am using for Windows 95. I can ping all the servers with names & IPs.

# more resolv.conf
domain fmr.com
nameserver 137.199.36.20
nameserver 155.1.1.15
nameserver 155.1.167.22

# ping 137.199.36.20
137.199.36.20 is alive
# ping 155.1.1.15
155.1.1.15 is alive
# ping 155.1.167.22
155.1.167.22 is alive

# nslookup 137.199.36.20
Server: fddn-qns.fmr.com
Address: 137.199.36.20
Name: fddn-qns.fmr.com
Address: 137.199.36.20
# ping fddn-qns.fmr.com
fddn-qns.fmr.com is alive

# nslookup 155.1.1.15
Server: fddn-qns.fmr.com
Address: 137.199.36.20
Name: fddn-tns.fmr.com
Address: 155.1.1.15
# ping fddn-tns.fmr.com
fddn-tns.fmr.com is alive

# nslookup 155.1.167.22
Server: fddn-qns.fmr.com
Address: 137.199.36.20

Name: fddn-ns.fmr.com
Address: 155.1.167.22

# ping fddn-ns.fmr.com
fddn-ns.fmr.com is alive

# netstat -rn

Routing Table:
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
155.1.0.0 155.1.243.184 U 3 4 hme0
224.0.0.0 155.1.243.184 U 3 0 hme0
default 155.1.243.1 UG 0 12
127.0.0.1 127.0.0.1 UH 0 2260 lo0
#

ahoffmann

so, does it work now?

vctsang

ASKER

No..I still having the same problem

rkuethe

Just to rule out the obvious, check for /etc/defaultdomain and /etc/defaultrouter. Also run domainname from the command line, set your domain and see if that helps. Maybe trying entering a site in /etc/hosts. Are you trying to go through a firewall?

vctsang

ASKER

I checked the /etc dir & I don't have a defaultdomain file. I have the following 2 files:

Default
Defaultrouter

I tried the enter a the yahoo.com site in the host file, it failed to connect. I am going through a firewall.
I was able to connect to the internal intranet but not the internet. I am thinking it might be the firewals.

Thx...
-VTl

rkuethe

Can you ping your wks by name from a LAN PC?
Also run a tracert on a PC (WIN/NT command); it will show if it is going through a firewall:
tracert ahost.adomain.com

vctsang

ASKER

Yes, I can ping & telnet to my Sun WKS in the LAN environment from my PC. When I did a tracert to www.yahoo.com from my Win95 Wks I got the following Infos.

Tracing route to www5.yahoo.com [204.71.177.70]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms h99a.fmr.com [155.1.243.2]
2 h99a.fmr.com [155.1.243.2] reports: Destination host unreachable.

Trace complete.

Thx again....
-VT

arthurd

Does your site have a firewall? Do they have a proxy server? If so, you'll have to configure netscape to use the proxy server or have your local lan admins to punch a hole in the firewall for you.

rkuethe

arthurd is on the money, try setting up your proxy server to be:

155.1.243.2 (the http port is 8080)

That is the typical port number used (default); to see if that port is active try:

"telnet 155.1.243.2 8080"

You can also download "traceroute" (I think gnu has it), compile and run that on the workstation.

or try this:

/usr/sbin/ping -Rvs ahost.adomain.com

If all else fails: (as root on your station)
snoop mystation >>/tmp/a.log.file
Try connecting again (different screen) and check the packet info in the logfile. ****CAUTION: LOG file will grow quickly!!!; don't forget to kill the snoop.

ASKER CERTIFIED SOLUTION

maximum

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

vctsang

ASKER

I am all set. I want to thank you both...You guys are the greatest....Happy Holidays!!!!!!!