Obtain an IP Address Automatically - "Is Goofy" on XP 5

[dydavid]

Obtain an IP Address Automatically - "Is Goofy" on XP

Client is using these items:
1. ARESCOM unit for MSN DSL 192.168.1.1 Gateway
2. Linksys BEFSR41 4-Port Switch 192.168.2.1 Gateway
3. Windows 98 HP Pavilion P2 [Obtain an IP Address Automatically ]
4. Windows XP HP Pavilion P4 [Obtain an IP Address Automatically - failed]
5. Obtain an IP Address Automatically in enabled on TCP/IP

---------------
A. When client is using items 1, 2, 3, 5 - the Internet works very well. #3 has 192.168.2.2 & 255.255.255.252 and works well.

B. When client is using items 1, 2, 4, 5 - the Internet does not work. Tried all of these things: re-installing Realtek driver for Network adapter on Win XP PC, upgraded Realtek driver, Start Run Reset adapter, disabled & re-enabled [Local Area Connection], rebooted PC, [pinged 127.0.0.1 - OK], [pinged 192.168.2.1 - Not OK].

C. The only way I could get the XP PC to work was to configure the Network Adapter manually:
IP 192.168.2.3, Subnet 255.255.255.0, Gateway - 192.168.2.1, and DNS values from MSN.

D. HP Tech Support recommended replacing the new XP PC with another one.

E. Linksys Tech Support recommended checking this with Microsoft.

Any ideas anybody?

Thanks, Dave.

 

[candyman200]

Just a thought - check the Linksys logs and see if there's anything that pops out. Here's the link to BEFSR41 page and there's a log viewer download at the bottom of the page.

http://www.linksys.com/products/product.asp?prid=20&grid=5

I've had "issues" with WLAN Linksys NICs not grabbing an IP and our LAN is mostly 3-Com/Netgear NICS and HP switches.

 

[ceh4702]

I use Win XP Home Edition and I do not have any trouble getting XP to connect to my Linksys Cable/DSL Router. I have the Router set up for DHCP. All I did was use the Networking wizard and select that I accees the Internet through the attached LAN.

Poof it works just fine.

I did not use a signon password, and I do not know if that makes a difference. I did change the Default user names so you have to still guess my signon name. Always remove the default signon names, since everyone on earth knows the defaults for Win XP.

The networking wizard will not work if the driver or the NIC is not installed and working and connected.

Sometimes with my cable modem I have to turn it off and back on to reboot to get the networking to work properly after changing the settings for networking.

If you have any custom settings like static IP Numbers for a server or such things like that it may complicate the process. It is possible the MSN Networking may have some issues. One thing you may try is using an alias on the router setup so they all appear to have the same Hardware Address for the NIC Hardware Address.

If you do not like my post feel free to point out your opinion or my errors.

 

[BOKA]

DYDAVID, looks like you need to change your netmask in router setup. With netmask 255.255.255.252 you can only have two hosts on the subnet - 1 is router and 1 is your W98 pc. Make your netmask at least 255.255.255.248 - this way you can have 6 hosts per subnet - 1 is router + 5 clients.

Good luck.

 

[bcastner]

I agreee with BOKA, set the subnet mask on the Linksys to 2555.255.255.0. Make sure the DHCP scope on the linksys is sufficiently large enough as well: by default it should attempt 192.168.2.49 - 192.168.2.100, which should be fine.

 

[candyman200]

I guess my question is that in the original posting it did not mention anything about using both PCs at the same time ... only 1,2,3 & 5 or 1,2,4 & 5. That being the case would the TTL not expiring exclude reassigning the IP to the new MAC? If so, then changing the mask (and making sure the scope were wide enough) should work and assign a second IP to the XP MAC. If that's not the case then it's a whole different issue.

 

[BOKA]

CANDYMAN200, good comment, I agree.
But netmask is the easiest to check out. Besides, it did sound like he tried to connect W98 pc first.

 

[candyman200]

I agree with you BOKA, the Win98 appears to be first connected and the XP might not have an IP available. A netmask change on the switch is the quickest test - then you can see if, when only the XP machine is connected it gets the next IP in seqence ... you can then assume a combination of netmask and TTL is the cause.

 

[ricpinto]

The main culprit there is the subnet mask. TTL issue is the result not unless linksys also got issue.

 

[dydavid]

Thank you all. BOKA specially.

A new replacement PC will arrive Aug 8-10 from HP. Will test the .248 in place of .252 in subnet mask (which Linksys Tech Support recommended - I don't know why they did that. I explained that client had two PCs to connect.)

That makes the most sense to me.

Best regards to all. Will report back approx Aug 8-10.

Dave

 

[dydavid]

Thank you all again.

1. Set subnet to 255.255.255.248

2. Now I tried automatic TCP/IP setting for detection of
IP number. No luck. No matter if I rebooted XP PC or
reset the two routers I still could auto detect.

3. So I entered the values manually for IP num & subnet.
Works like a charm! - I am baffled.

4. When at a client site, there is no time to fiddle
around with what is not working. The client is happy,
I can remote in to his desktop & life is good.

Best regards, Dave