I've mostly used combination modem/routers in the past so I hadn't really come up against this till now. I have an ADSL modem which serves DHCP, but only to one device. It also doesn't have a configurable IP. I plugged my router into it (connected to the WAN port, of course), but when I do that, I can't use the same subnet on the LAN as on the WAN. (The modem serves 192.168.1.x, so I have to use something else, e.g. 192.168.0.x.)
What I don't understand is why those can't be the same. Aren't they separate networks? Doesn't the router's NAT take care of stuff like that? Is this just an arbitrary limitation of this router, or is there some reason it must be this way?
Doesn't that create a problem in the way things are modularized? For example, when I was first configuring my router, I had the modem disconnected, and I was configuring it on 192.168.1.x. As soon as I plugged in the modem, it changed my LAN subnet to 10.0.0.x. This leads to the situation in which, if I switch out the modem, and it decides to serve some subnet supposedly 'in conflict' with my LAN, my whole LAN is screwed up because it's dependent on some modem which isn't even on the LAN. Likewise, it makes for a restriction in the way I can configure my LAN, based on some silly modem that isn't on the LAN.
What I don't understand is why those can't be the same. Aren't they separate networks? Doesn't the router's NAT take care of stuff like that? Is this just an arbitrary limitation of this router, or is there some reason it must be this way?
Doesn't that create a problem in the way things are modularized? For example, when I was first configuring my router, I had the modem disconnected, and I was configuring it on 192.168.1.x. As soon as I plugged in the modem, it changed my LAN subnet to 10.0.0.x. This leads to the situation in which, if I switch out the modem, and it decides to serve some subnet supposedly 'in conflict' with my LAN, my whole LAN is screwed up because it's dependent on some modem which isn't even on the LAN. Likewise, it makes for a restriction in the way I can configure my LAN, based on some silly modem that isn't on the LAN.
![A port address conflict has been detected lan messenger download A port address conflict has been detected lan messenger download](http://i.imgur.com/o6CpNBn.png)
Assigning TCP/IP Ports for In-House Application Use. THE IANA WILL ASSIGN THE NUMBER FOR THE PORT AFTER YOUR APPLICATION HAS BEEN APPROVED. Hard-coded port numbers are a bad idea, particularly if you later find a port conflict with another application and need to change yours. Share improve this answer.
Overnight, 4 different computers (including one server) have gotten IP conflicts. The IPs are static. The assigned IPs have been assigned for quite some time.
All addresses are within one range.
No apparent official IP assignments have occurred in this time frame.
I am working under the following limitations:
-Only my supervisor has access to the Cisco switches (including the backbone) to do any sort of troubleshooting
-We still have a LOT of legacy crap, including 4 different 10base2 runs.
-We have limited access to tools (my boss has the Fluke and is using it with a vendor for something else)
The event viewer on the affected server says the IP conflict is with a computer with the same mac address as it.
In the same time frame, my supervisor was experimenting with DHCP on this side of the network, but has since disabled the service and deauthorized the DHCP servers from the 2003 Domain Controller/Wins Server. We are running in hybrid mode with Win2003, Win2k and WinNT4 in our server mix.
ARP has not been very useful, unless I'm doing it very wrong. It returns the MAC address of the computer that's supposed to have the IP address, rather than the one that is allegedly causing the conflict.
The temporary fix of changing the server's IP isn't very useful, because I can't get into our database for the free IP list and that server with the IP conflict is also acting as a web server
What is the best and quickest way with the aforementioned restrictions to find the computers/devices causing the conflicts without walking around to every desk on campus?
P.S. Yes, a lot of the things are half assed. This is what happens when you are given unfunded mandates and NO resources.
All addresses are within one range.
No apparent official IP assignments have occurred in this time frame.
I am working under the following limitations:
-Only my supervisor has access to the Cisco switches (including the backbone) to do any sort of troubleshooting
-We still have a LOT of legacy crap, including 4 different 10base2 runs.
-We have limited access to tools (my boss has the Fluke and is using it with a vendor for something else)
The event viewer on the affected server says the IP conflict is with a computer with the same mac address as it.
In the same time frame, my supervisor was experimenting with DHCP on this side of the network, but has since disabled the service and deauthorized the DHCP servers from the 2003 Domain Controller/Wins Server. We are running in hybrid mode with Win2003, Win2k and WinNT4 in our server mix.
ARP has not been very useful, unless I'm doing it very wrong. It returns the MAC address of the computer that's supposed to have the IP address, rather than the one that is allegedly causing the conflict.
The temporary fix of changing the server's IP isn't very useful, because I can't get into our database for the free IP list and that server with the IP conflict is also acting as a web server
What is the best and quickest way with the aforementioned restrictions to find the computers/devices causing the conflicts without walking around to every desk on campus?
P.S. Yes, a lot of the things are half assed. This is what happens when you are given unfunded mandates and NO resources.