Articles

LAN gateway address conflict

May 18, 2008 at 07:19:04
Specs: XP, 512

I input static ip addresses on my lan card and wireless network card on my laptop which is behind a d-link router.It brought a message (two or more card with the same gateway may cause your system not to work very well,do you want to continue)which i said yes,then my system stopped browsing and when i ping the gateway 192.168.0.1 it times out.

See More: LAN gateway address conflict

Report •


#1
May 18, 2008 at 13:25:21

Why did you hardcode the ip addresses?

Life's more painless for the brainless.


Report •

#2
May 18, 2008 at 14:37:55

Whatfor do you need 2 network cards for the same network?
Disable one of the cards and it will work.
So you can enable the one card you'd like to use while diableing the other card.

Report •

#3
May 19, 2008 at 06:30:52


Jennifer
=Sorry i dont understand what you meant by "Hardcode the ip address"

Paul
=Not 2 network cards but one lan and one wireless on laptop.I disabled the Lan and later the wireless but it wasn't still working...the ip i used were 192.168.0? and 192.168.1.?
Still not browsing and not pinging the gateway (d-link router)


Report •

Related Solutions

#4
May 19, 2008 at 06:54:28

So you manually configured the IP-adresses, but it seems, that your d-link router has another IP-address, not part of 192.168.0.x and 192.168.1.x.
Therefor, read the routers manual to figure out the correct IP-address of your router.
Then, configure one of your 2 network cards (doesn't matter whether it's internal wireless or pcmcia, network card is network card), to an IP address of the range, your router uses.

E.g.: If your router has the IP address 192.168.2.1, your network card must have an IP address of the range 192.168.2.2 to 192.168.2.254.
Otherwise you can't ping the router or surf the internet.


Report •

#5
May 19, 2008 at 07:01:42

My router as ip 192.168.0.1 and when the problem started i changed it to 192.168.1.1 even to 192.168.2.1.but the problem wasn't solved.
seems when the error message"two cards cant be on the same gateway,do you want to continue" was shown and i clicked ok.there was a conflict and thsi as messed up the cards.so what to do to bring them back to life is the issue now.

Report •

#6
May 19, 2008 at 08:01:05

If you're using the wired NIC, disable the wireless NIC and shut it off and vice versa for when you wish to use wireless.

It would be a lot simpler to allow DHCP to automatically assign your TCP/IP information.


Report •

#7
May 19, 2008 at 08:18:53

"My router as ip 192.168.0.1 and when the problem started i changed it to 192.168.1.1 even to 192.168.2.1.but the problem wasn't solved."

babasemi you have some learning to do concerning ip addressing.

Using x.x.1.1 and x.x.2.1 when your router is at x.x.0.1 is wrong because .1.1 and .2.1 are in very different subnets than .0.1

You could have assigned 192.168.0.2, .3, .4 etc.

Imagine the power of knowing how to internet search
http://www.lib.berkeley.edu/Teachin...


Report •

#8
May 19, 2008 at 08:44:45

Curt R
=I have tried your solution too.disabeling one for the other (wireles for lan and vice versa)but my laptop couldn't still browse.

Wanderer
=You didnt quite get what i was saying.lol
The ip 192.168.0.1 is the initial ip after the problem started i changed it to 192.168.1.1 just to check if it will browse,when it wasn't working i then changed again to 192.168.2.1 all with subnet 255.255.255.0 and ping the router each time shows time out.

Tnx.


Report •

#9
May 19, 2008 at 08:54:04

If your router actually is at 192.168.0.1, your network card must have an IP of 192.168.0.x, where x is of the range from 2 to 254.


Report •


Ask Question