Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Ip Address Conflict


  • Please log in to reply
1 reply to this topic

#1 Stacy Jamie

Stacy Jamie

  • Members
  • 77 posts
  • OFFLINE
  •  
  • Local time:07:40 AM

Posted 29 February 2008 - 11:35 AM

For as long as I remember, we had wireless connection at home on our linksys wrt54gs (ver6) router. Just yesterday, the dsl connection was cut off. Now, after calling our ISP, our port at the main network was changed and everything seemed to go well ... when the dsl modem is plugged to the pc. When we went back to the router wireless mode, there was no connection until I reset to factory settings and used Automatic Configuration DHCP instead of the PPPOE which my friend set up initially and no longer works.

Anyway, apart from that why PPPOE no longer works (meaning we dont get any internet at all ... even the wired pc), I'd like to know why I've just got this error only now ---> "there's an IP address conflict with another system on the network"

Automatic configuration didn't cause that problem. The message only showed up after I followed the instructions from this website (http://www.technicallyeasy.net/2007/09/securing-linksys-wrt54g-wireless-router.html) because, after resorting to default settings, I no longer have security enabled, hence I had to just follow someone who knew how.

Things to take note of:
I never assigned any static ip addresses. they have always been on automatic
Only two comps are present. wired pc and a laptop on wireless.
I upgraded my firmware to the latest version

If someone could suggest a way of solving this problem without having me assign static ip addresses or do any complicated stuff then i'd be most gratefull

BC AdBot (Login to Remove)

 


#2 Cyb3r_Ninj@

Cyb3r_Ninj@

  • Members
  • 169 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Silicon Valley
  • Local time:04:40 PM

Posted 29 February 2008 - 12:53 PM

If you are familiar with the Command Prompt, there are a few things that you can do from the command line, that could give you some clues.

First thing i'd do is to get the detailed IP address information for both computers, by running the ipconfig command:

Click Start >> Click Run >> type cmd.exe >> Press Enter

Once you have brough up the Command Prompt, what you are looking for is the detailed IP address information, you want this from both computers. Issue the following command:

ipconfig /all >> Press Enter

This will output the IP Configuration information for all your NIC devices that are present on your computer; you can write this information down, take a screen shot of it, or redirect the output from on-screen to a text file as in the following:

ipconfig /all > %filename%.txt

In this case %filename% is a variable which you can name whatever you like. NOTE: when you redirect [>] the output of the ipconfig command, it will save the file into the directory that is present on the command line, which by default is C:\Documents and Settings\%username%, where %username% is your login username.

Do the same thing on both / all computers. This is so you can make a comparison between all machines to determine if in fact there is an IP Address Conflict or duplicate IP addresses between your machines. Pay attention to the following:
* - Dhcp Enabled (may OR may NOT be set on both machines, this could be by design)
1 - IP Address (should NOT be the same on both machines)
2 - Subnet Mask (should be the same on both machines - unless you have subnetted)
3 - Default Gateway (should be the same on both machines)
4 - DHCP Server (should be the same on both machines)
5 - DNS Servers (should be the same on both machines)

You need to confirm that the IP Address | Subnet Mask for all machines is NOT the same, that would indicate an immediate problem - in a single network no two machines should ever have the same IP address.

IF DHCP is enabled, you know that the IP addresses are being automatically assigned, and should therefore, be relatively close in numerical sequence. If you see a huge gap in the numerical sequence, there is a possibility that one of the machines is configured with a Static IP address while the other may not be. The problem with configuring Static IP addresses, is that if it is not reserved in the DHCP server, there is the possibility of manually assigning an IP address to a computer to which the DHCP server has already assigned the address, resulting in 2 machines with the same IP address.

If all machines have DHCP enabled, you can release and renew the IP addresses on all machines to rule out the possibility of duplicated DHCP IP address leases as follows:

ipconfig /release >> press Enter
ipconfig /renew >> press Enter

If you have one or more machines that have DHCP disabled, you need to determine if this was done as part of the design of the network; meaning if you wanted or needed to use Static IP addresses, then you would not want to use DHCP OR create DHCP reservations for the Static IP addresses which your machines were going to use. This is a little advanced and probably impractical for a SoHo network.

Since you have the network information on both your machines, you want to test network connectivity and transmission next - just because you can't get to the Internet, doesn't necessarily mean that you aren't connected to the network. So issue the ping command from one machine to the other and see if they are talking to each other, as follows:

ping ipaddress
Where "ipaddress" is the IP address of the machine that you want to send a ping packet to.

If both machines are talking to each other, you should get a response without loss of packets. If you can confirm that both machines are talking to one another, then you want to ping your router or modem to ensure that it is talking to your machine - most likely the answer is yes if you got this far, the router is the Default Gateway and that should be issuing out the IP addresses and allows your machine to connect to the Internet. In my experience Linksys WRT45G routers are usually setup with IP address 192.168.1.1 and assign IP addresses to connected clients in the range 192.168.1.2-192.168.1.254.

In any case, the IP address of the Default Gateway is the IP address that you want to ping in order to determine Internet connectivity. Again, you may be able to ping back and forth from two machines that are which have network connectivity, but are still unable to get to the Internet because traffic may be blocked or dropped at the Default Gateway or Router.

I'd start with those steps first; try it out see what results you get and provide some feedback for ideas on what to do next.
***********************************************************************
Bill Gates recognizes the skills... so i suggest you start there and recognize them too...
***********************************************************************
:: digital.ronin ::

| MCP - ID 5646435, other certifications pending... |




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users