megamike
asked on
Using a switch and a router with XP
I have 7 computers in my basement. All XP, excpet one with ME. I have cable internet and a D-link 614+ router. I have always had a extra network card in my main PC which was connected to my 8-port switch via that card, while that main computer revieved it's internet through the onboard NIC via the router and modem.
Worked fine forever... Two days ago, my VOIP quit working, and I tried to figure out why... After messing with settings, I now have not VOIP and the NIC that saw the network keeps appearing as "limited or no connectivity". I also called the VOIP people and my account had problems, so that is why it wasn't working...
Still cannot get the lan up though. I let the D link be the DHCP server and it does a nice job with the cable/router connection, but cannot assign the second NIC's IP.
If I manually set the IP, the router dissapears for Windows.
If I check the IP when I get the Failed response for obtaining a IP it is like this. 169.254.4.111
Is there a second place that might be trying to assign IP's? Are Windows and my Router duking it out? I had my router set to 192.168.0.2 instead of .1 on the previous setup. Is 192.168.0.1 reserved or anything.
Thanks for your time.
Mike
Worked fine forever... Two days ago, my VOIP quit working, and I tried to figure out why... After messing with settings, I now have not VOIP and the NIC that saw the network keeps appearing as "limited or no connectivity". I also called the VOIP people and my account had problems, so that is why it wasn't working...
Still cannot get the lan up though. I let the D link be the DHCP server and it does a nice job with the cable/router connection, but cannot assign the second NIC's IP.
If I manually set the IP, the router dissapears for Windows.
If I check the IP when I get the Failed response for obtaining a IP it is like this. 169.254.4.111
Is there a second place that might be trying to assign IP's? Are Windows and my Router duking it out? I had my router set to 192.168.0.2 instead of .1 on the previous setup. Is 192.168.0.1 reserved or anything.
Thanks for your time.
Mike
Les Moore
Sounds like your onboard NIC just went sour on you. I had one do that to me last week. New NIC and back in business (well, blew the dust of an old nic in my desk drawer and popped it in, anyway).
ASKER
Yikees =) It is a onboard gigabit NIC... =) At first I thought your idea was groovy, it was just the Linksys card.
Anyhow. I have been playing and I can get connectivity if I do the following.
D link set at 192.168.0.2, I set the gigabit nic to 10.0.0.1 and another of the 7 to 10.0.0.2. I am able to browse the hard drive of the other systems now, I just cannot get the internet on them running...
Thanks for your comment. I will keep fiddling.
Anyhow. I have been playing and I can get connectivity if I do the following.
D link set at 192.168.0.2, I set the gigabit nic to 10.0.0.1 and another of the 7 to 10.0.0.2. I am able to browse the hard drive of the other systems now, I just cannot get the internet on them running...
Thanks for your comment. I will keep fiddling.
ASKER
I stated in my first post that the D-Link cannot assign IP's to the second NIC, but I wanted to clarify that it always has before. This is the first time the 169.254 stuff has appeared
ASKER
Solved it. I needed to bridge the two network cards. As soon as I bridged them the IP's started working and the other computers in the network were able to see the shared net connection.
Thanks again for your thoughts.
Mike
Thanks again for your thoughts.
Mike
ASKER
Since I solved it myself... What do I do now?
You can post in Community support and ask a moderator to PAQ this question (since it does have a solution) and refund your points..
- Cheers!
- Cheers!
ASKER
Thanks. Sure am glad it is working.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.