Peculiar Network Problems

[tiberius]

I have, currently, two computers connected to a Linksys 5-port switch. The RoadRunner (SB3100 SURFBoard) cablemodem is connected into the uplink port of the switch. The Windows 98 machine is unable to pull an IP Address from the cable modem, but the Windows 95 machine can pull an IP address and is fully functional.

Windows 95, current network configuration-
* Client for Microsoft Networks (Not set to log onto Windows NT Domain, Set to Logon and Restore Network Connections)

* Linksys LNE100TX Fast Ethernet Adapter (Bound to IPX/SPX Compatible Protocol, and TCP/IP)
* IPX/SPX Compatible Protocol (Bound to Linksys LNE100TX Fast Ethernet Adapter, File and Print sharing for Microsoft Networks, and NetBIOS support for IPX/SPX Compatible Protocol)
* NetBIOS (Bound to Client for Microsoft Networks, and File and Print Sharing for Microsoft Networks)
* TCP/IP (Set to Obtain IP Address Automatically, Disable WINS Resolution, no default gateways, Disable DNS, Bound to Client for Microsoft Networks)

Windows 98, with identical network configuration. A difference that I have noted, though, in winipcfg, is that the Windows 95 machine has a subnet mask of 255.255.255.0, and the Windows 98 machine has a subnet mask of 255.255.0.0. As well, the Windows 98 machine refers to the IP Address it should be assigned as an "IP Autoconfiguration Address", while the Windows 95 machine refers to it as simply a "IP Address". Also, when the Windows 95 machine doesn't have an IP address, it reports the IP address as "0.0.0.0", while the Windows 98 machine reports it as 169.x.x.x.

I've tried removing and reinstalling all network adapters, clients, protocols, and services on the 98 machine, I've tried releasing the IP with the first machine, pulling it out of the switch, and seeing if the second could pull an IP then, nothing seems to work. I've got a hunch it has to do with the Windows 98 machine's interesting values in winipcfg, but after two hours in regedit and several registry restorations, I've come to the conclusion that I can't come to a solid conclusion on how to fix it.

Any advice is more than welcome.
Tiberius

[Storm90]

Have you purchased a seconed Ip address? If so you might try and hook the cable modem rj45 line to the win 98 computer and let it pick up its Ip. After it does rehub and they both should work. Sounds like you are out of sych. Also try restarting the modem. Sometimes this helps.

[tiberius]

I honestly don't think it has to do with the network.
I think it has to do with how TCP/IP is setup for the NIC. The winipcfg for the network adapter on the 95 machine refers to "IP Address", and the winipcfg for the PPP adapter on the 98 machine refers to "IP Address", but the winipcfg for the network adapter on the 98 machine refers to "IP Autoconfiguration Address". Whatever this is, I'm sure it's the problem. If anyone knows what this is or how to fix it, please reply.

[tiberius]

Well, I figured out how to disable the IP Autoconfiguration. It didn't help.
But something else pecular is the fact that the adapter address is "FF-FF-FF-FF-FF-FF". Would that be a driver problem, or is that just a default broadcast address to locate it?

[Storm90]

Well you are useing roadrunner and as far as I know the Ip is to be automaticly detected on both machines. I am running the same set up on three machines as you are and have purchased 2 extra Ips.Yes you might want to check the drivers for your nics. That could be a problem to. When you pull up Winicpfg the name of your adapter card should show and the ip. This problem Might lie in in the nics. I would try seeing if you can get update drivers for them. Then reinstall them this in turn will rebuild yourTcp/Ip adapter
wich in turn might help. Roadrunner dose not run static Ips so they change every once
in a while so you must have Ip autoconfigeraion In order for it to renew the Ip. If this dose not help I would try hooking one machine up at a time and see if I could get a Ip adress on it. Hope this helps I am just as confused as you are. I have run this setup like yours for three years now and have not had a problem. I really think the problems lie in the nics, but I could be wrong!

[dissident75]

Well, to me it seems that the problem may is an ip config problem.... The most important thing I need to know is this. Did you purchase additional IP's?

[tiberius]

Not yet. For several reasons.
One, the technician clearly stated that it'd automatically bill me when the computer pulled another.
Two, the computer won't connect when directly attached to the cablemodem.. why pay 10 dollars for something that I'm not even sure I can get to work yet?
Three, I did try, initially, to purchase an additional IP. I got into a sort of transfer loop. Nobody seems to have the power to upgrade my account, so they push the first button they see on the phone and hope that person can.
I'd rather get it working when directly connected to the modem before I fork out the additional money.
And, in summary, I have not purchased additional IP addresses :P
Any other ideas on why it wouldn't be working? Especially, why it wouldn't work when connected *directly* to the cablemodem?

Tiberius

[Storm90]

With out a seconed Ip it will not work. You might have to get a software program that lets you share one Ip with both computers.The 169xxxx Is comeing up on the seconed machine because it will not pick up and Ip due to there is not one for it. The way you want to do it you will either need a router or software program.

[tiberius]

Am I to believe that it does not work when *plugged directly into the cablemodem* because I have not purchased an additional IP? Does this make sense to you?
And furthermore, the technician clearly stated that the billing would start automatically when the second computer tried to pull an IP address. What reason would he have to lie to me? Also in support of this is the Ring-O'-Transfer that I had the wonderful opportunity to ride for two hours before someone finally hung up on me. If it didn't automatically activate, they'd almost definitely have someone empowered to sell it.
Anyone have any clues why, when plugged directly into the cable modem, my second computer fails to pull an IP address, even after an appropriate power-down of the cable modem?
Tiberius

[Storm90]

Well I don't think he did. But with my provider they had to release the seconed Ip for me. I would call back and see if you can talk to someone eles. I had notice mine would pick up the Ip and soon as I hook it up but would Not stay connected till they released it. On the seconed computer try checking all the Tcp\ip protacal and the nic you are useing . They can cause these problems to. Plus that computer will not have the gateway settings till it acually has a Ip. Also Try checking your wire you use to connect it Could be bad and work intermittly. Had one like that and had to change it. You might also want to try and rebuild the network in win 98 computer this may help to.

[This message has been edited by Storm90 (edited 09-16-2000).]