on Sat, 2 Feb 2008
14:10:43 -0800
> I should have looked into RESOLV2 before I sent the previous post. It contains:
>
> domain
> nameserver 192.168.1.1
>
> 192.168.1.1 points to my router not a name server. Unless it must point there so the router can do
> its NAT thing. Perhaps SeaMonkey looks at some other source for direction.
What I saw in one of your traces was a DHCP lease renewal. If you have a
dynamic IP your ISP should be sending the IPs of the name servers with you IP.
I am guessing that you have a router that is connected to your IP. I would
expect the router to pass the name servers IP addresses to any computer that
connects to it. An alternative is to put the name servers IP addresses in the
TCP configuration, this would be a temporary fix as you will want to get your
local network configured to work correctly.
--
Robert Blair
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 02 |
February |
2008 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
