Text 6295, 56 rader
Skriven 2005-03-28 06:01:00 av Jeff Guerdat (1:106/2000.0)
     Kommentar till en text av Gerald Miller
Ärende: lan
===========
On 03-27-05, Gerald Miller said to Jeff Guerdat:

GM>I'm not sure if the ZoneAlarm or router firewalls are responsible for the
GM>local IP Address change but I am suspicious of ZAP.

Zone Alarm has no effect on network address - it works once you have an
address from the router.

GM>I had thought that the original NIC may have turned "rogue" on me.  So I
GM>replaced it with another DLink NIC.  W2K detected the hardware change and
GM>I had to step through the driver update wizard.  When all was said and
GM>done, IPCONFIG /ALL said the Win2K IP Address was 169.254.203.4 with a
GM>Subnet Mask of 255.255.0.0.

That's the DHCP address used by the NIC/OS to talk to a DHCP server to gain a
real address.  If that's what you saw, the router wasn't supplying an address
for some reason.  Given enough time (several minutes) the address would have
finally changed to 0.0.0.0, also useless.

GM>That didn't fit within the IP range of
GM>addresses as set by the router, so I pulled up Network Properties, changed
GM>"Autodetect IP" to manually configure and set the IP Address to
GM>192.168.2.xxx with Subnet Mask of 255.255.255.0 and Default Gateway of
GM>192.168.2.x.

Forcing it works fine as long as the router doesn't try to ALSO assign the
same address to another computer.

JG> Changing workgroup names has no effect on the IP address - they're
JG> separate issues.  The address is basic TCP/IP while workgroup names
JG> are all about MS Networking which runs *on* TCP/IP but also on other
JG> protocols.

GM>There seems to be an enormous number of protocols within TCP/IP!

Actually, they ride on top of TCP/IP.

GM>Tried mapping the network drive -- couldn't detect the WinXP workgroup
GM>name.  Forced it to browse for the \\winxp\junk folder -- it took a while,
GM>but it was finally able to see the drive and I took the opportunity to
GM>copy some Win2K files and folders to WinXP.  That appears to have been
GM>successful.

GM>Still no Inet connection and I can't hook up with the mailserver...

I'd try to determine why you can't use DHCP - that will give you the DNS
server settings needed to access things outside your LAN.  You can manually
set them but it should be working properly.  If you think it's ZA, disable it
for the time being.  Work on one problem at a time...


___
*Durango b211 * DurangoMail for Windows NT/9x

--- Maximus/2 3.01
 * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)