SCOUG-HELP Mailing List Archives
Return to [ 16 | 
June | 
2003 ]
<< Previous Message << 
 >> Next Message >>
 
 
 
Content Type:   text/plain 
=====================================================  
If you are responding to someone asking for help who  
may not be a member of this list, be sure to use the  
REPLY TO ALL feature of your email program.  
=====================================================  
 
Steven Levine writes:   
 
 
> In <20030616030327.94726.qmail@courtney.linkline.com>, on 06/15/03   
>    at 08:02 PM, waynec@linkline.com said:   
>   
>>They were sent friday evening, off-forum.   
>   
> OK.  I found the rest of them.  You are using a non-compliant e-mail  
> program that does not properly encode files that contain Ctrl-Z  
> characters.  My e-mail program is not very forgiving about this and cuts  
> off the message at the Ctrl-Z.  IMO, both are wrong, but I know how to  
> handle the problem once I know it exists.  I've got all the files now.   
>   
> Just to verify, these are from the new AMD?  Correct.  The config.sys  
> comments are confusing.  
 
No, on the P2. The cloned scsiWarp partition on the AMD is still not   
bootable with the ide 40gb drive attached. I know the config.sys comments   
are confusing, they evolved over a number of years.   
 
>   
> Resolv2 is wrong.  As I suspected you are confusing domain with hostname.   
> Change resolv2 from:   
>   
>  domain waynesworld   
>   
> to   
>   
>  domain linkline.com   
>   
> Setup.cmd has a minor error:   
>   
>   ifconfig lan1   
>   
> does nothing.  It might as well be REM'ed out.  
 
Well, I don't think I was confusing domain with hostname, at least not in   
the tcpcfg or the LinkSys router. It did appear thet the "resolv2" was mixed   
up, so I must have done something that caused that. Actually, I do not think   
that "linkline.com" has to be the domain name. Anyway, I made changes,   
rebooted, same problem, noted some things didn't change, made more changes,   
etc. Basically, I altered resolv2, resolv, tcpcfg, and used mptcfg to remove   
the reference to the firewall, and made changes to the LinkSys router setup.   
 
resolv now says:   
 
 domain linkline.com  
 nameserver 66.59.235.1  
 nameserver 64.30.215.129   
 
resolv2 now says:   
 
 domain                        (not a misprint, it is blank)  
 nameserver 66.59.235.1  
 nameserver 64.30.215.129   
 
I reran the adapter configurator to remove the FXWRAP1$ entry.   
 
I made sure that tcpcfg showed the same hostname as config.sys and left the   
local domain name blank (this seems to be propogated from the LinkSys   
anyway).   
 
I updated the LinkSys router to use "WayneLS" as the hostname for the   
LinkSys (which is an optional entry) and left the domain name (also   
optional) blank; set up 2 dns addresses to the addresses provided by my ISP   
(I formerly had tried both and just one dns address without effect).   
 
Frankly I'm not certain which of these changes made the difference, as I   
tried a half-dozen combinations, rebooting each time, before it started   
working. I was making some of those changes in parallel on the AMD, which   
kept right on working through all of them.   
 
Anyway, you got me pointed at the right area, Steven, and it is now   
working!!!!   
 
 
>   
> Config.sys has a another typical minor TCP/IP setup error.  You want to  
> change:   
>   
>   SET TZ=EST5EDT   
>   
> to   
>   
>   SET TZ=PST5PDT   
>   
> Fix these up and if the DNS problem persists, send me copies of the  
> updated files and new traces.  
 
Problem did not persist.   
 
>   
>>Well, now I am confused. I installed Injoy  some years back, when i was   
>>using  dial-up for internet access; I thought I'd removed it, or at least  
>> crippled it. Sorry, I'm just not all that knowledgeable on networking.  
>>Perhaps Injoy IS the problem.   
>   
> Just make sure the Injoy dialer is really inactive when you are using DSL.   
> It probably is.  As I mentioned before Injoy Firewall and your Linksys  
> router do the same thing for a DSL connection.  I can't usually tell by  
> looking at a trace which is being used.  
 
This could have been the culprit (FXWRAP1$), but it's hard to say that,   
because that entry has been in my protocol.ini for a long time and the   
problem is only a couple of months old. I may add it back in on protocol.ini   
just to see if it causes the problem to reoccur.   
 
Thanks, Steven, I'm feeling a lot better now that I can go surfing without   
that constant aggravation!   
 
Now, do you want me to change the subject on my posts for my AMD ide 40gb   
(and install diskettes) problems?  
 
=====================================================  
 
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  
"rollin@scoug.com".  
 
=====================================================  
 
  
<< Previous Message << 
 >> Next Message >>
Return to [ 16 | 
June | 
2003 ] 
  
  
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.
 
 |