RE: 2 pc network - XP and Win95 - help needed badly!

From: Clark (Clark_at_discussions.microsoft.com)
Date: 09/03/04


Date: Fri, 3 Sep 2004 15:17:02 -0700

Just thought I would post the solution to this. After reading every
troubleshooting site and trying countless settings and
scenerios.............what really has to be done is
un-installing/re-installing the NIC's. Apparently......in Win95, and
sometimes in XP, previous IP addresses just won't get released and/or renewed
no matter what commands you use. Also......I deleted the winsock entries
(winsock and winsock32 in the registry) in XP and let it replace/rebuild them
on re-boot.......just in case they were somehow currupted, but I'm not
totally sure this was part of the problem. Re-installing the NIC re-sets them
clean. This was probably the one thing I did not think of to do. Now, ICS is
assigning the proper IP addresses, and the network is functioning perfectly.

"Clark" wrote:

> I've been trying to get these two machines networked for 10 days now with no
> joy. It seems I've tried every procedure at every networking site on the net.
> The current problem is this: The DHCP service in XP is not automatically
> assigning an IP address to PC2 (Win95), and is assigning an improper IP
> address (169.254.117.212) to it's own (lan) nic. From what I've read, DHCP
> should be doing this correctly and automatically with ICS installed. I'm
> getting an error message in the event viewer at regular intervals when XP is
> running.......Error: 32003 Source: IPNATHLP "The Network Address
> Translator(NAT) was unable to request an operation of the kernal-mode
> translation module", which is basically saying that "the public (shared)
> connection is waiting for a DHCP assigned IP address". There were also two
> other interesting one-time errors prior to this one: #1 Warning: Source: DHCP
> "Your computer has automatically configured the IP address for the network
> card with network address 00B0D0E7AF18. The IP address being used is
> 169.254.117.212".......followed by Error: Source IPNATHLP " The DHCP
> allocator has disabled itself on IP address 169.254.117.212 since the IP
> address is outside the 192.168.0.0/255.255.255.0 scope of which addresses are
> being allocated to DHCP clients. To enable the DHCP allocator for this IP
> address, please change the scope to include this IP address, or change the IP
> address to fall within the scope". Some other details: The set-up is a Dell
> 8100 (XP) with a 3COM integrated nic for the LAN, and an Intel internal DSL
> modem for the shared internet connection. The 95 machine has a Netgear nic
> and both machines plug into a 5 port switch. All hardware is functioning
> normally. PC2 (95) does not list PC1 (XP) in the network. PC1 DOES list PC2
> in the network, but can't be accessed (message: network address not found).
> Neither machine can ping each other. All required components are
> installed...........File/Printer Sharing, Client For MS Networks, Shares
> (folders,drives,printer) are enabled on both machines, Protocols
> installed.......I've even tried Netbeui because I read somewhere it was the
> easiest to configure, and set it as default on 95. I tried assigning IP
> addresses manually on both........192.168.0.1 and 2 with subnet mask
> 255.255.255.0. and confirmed on both machines with command 'ipconfig' and
> 'winipconfig'. Currently, at the command prompt on XP, it indicates no IP
> address or anything else assigned to ethernet lan nic, and the same on the 95
> machine. (both currently set to 'assign IP address automatically').
> So, it seems it's come down to the DHCP problem on XP, and possibly changing
> the scope one way or another, which I have no idea how to do. If anyone has
> any suggestions (that doesn't involve spending any money), or ideas, I would
> really appreciate it!
> Thanks very much for the time and any help........



Relevant Pages

  • 2 pc network....XP and Win95 problem-help needed badly
    ... The current problem I've come up with is this: It seems that DHCP in XP is ... assigning an improper IP address to it's own NIC, ... machines and set it to default on 95. ... accessed (message "Network address not found"). ...
    (microsoft.public.windowsxp.network_web)
  • Re: Network help anyone?
    ... control panel select Network connections, ... You can usually define the range of DHCP addresses available within ... Why not try assigning a static ip address of say: ...
    (microsoft.public.windowsxp.general)
  • Re: Fixed Lease DHCP Doesnt Work After Connecting Different Netwo
    ... Shouldn't be the one on the network you aren't connected to! ... then changing back to DHCP. ... One way around this would be to do an ipconfig /release *before* shutting ... Why is this happening and who can I fix it without assigning myself ...
    (microsoft.public.windowsxp.network_web)
  • Re: Limit DHCP addresses
    ... DHCP was not designed with goal of assigning ... Another option would be to build IPSec policy. ... network outlets -- but only the one in use. ...
    (microsoft.public.windows.server.general)
  • Re: networking private and public hosts questions
    ... some systmes in storage to create a test network. ... a WS to the child and attempted to pull an IP from the DHCP server, ...
    (microsoft.public.win2000.networking)