SCOUG-HELP Mailing List Archives
Return to [ 26 |
May |
2007 ]
Content Type: text/plain
What could be the reason for route failure?
I'm reconfiguring a computer that was used on a different network.
The setup.cmd is correct but route fails.
From the commandline I enter route add default '192.168.1.10
-hopcount 1' and it fails.
I cannot ping either, it fails.
But I can connect via peer. So that pretty much sez the nic &
cable are good.
I've changed tcpcfg to match my network. The old network was dhcp
this one is static, I've created a hosts file (which shouldn't
effect my inablility to ping ip addr).
I've been through files in \mptn & \tcpip & checked config.sys.
I'm missing something but can't find it.
I'd appreciate any clues.
Thanks, Jon
=====================================================
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".
=====================================================
Return to [ 26 |
May |
2007 ]
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.
|