changed ISP and router, problems with XEP setup

newalarm

Active Member
Hi all,
 
So, after getting gouged by my charming ISP, I decided to switch companies. Got rid of their all in one modem/router/wireless that they were overcharging for.
 
Now i have a modem, and my own linksys router/wireless (with nat loopback).
 
Second, I just picked up a non managed gigabite switch: teg-s24d by Trendnet. I assume the router is the device that assigns all IP addresses right?
 
Problem is, the IP address the m1xep is still set up on and searching for is from the old router. can;t seem to reset it. When i search for the XEP, it comes up with the old IP.
 
thanks.
 
The switch is dumb and the router is what assigns the IP's on the LAN.
 
How was the XEP set up? Static or DHCP? Where are you searching for the XEP...in RP?
 
Have you tried connecting directly via a crossover and configuring the XEP?
 
It was set up as static.
 
I went into RP, in my account, but not connected to the control (since I can't). I did a find to find all XEPs, and it find it, with the old IP. I assume it is going through my network only at this point.
 
I need to get my Router to assign it a new one 192.168.1.1xx type.
 
But when i go through the router, i find all devices connected, except the xep, even though it is hooked up to switch.
 
If you have it set as static in the XEP...not knowing how your router is set up (DHCP, reserved IP's, what have you) that's going to require a little bit of homework on your part.
 
Do you know the subnet or range the router is providing? Have you reserved any IP's on that as of yet?
 
Take your computer, a crossover cable, set both for the same subnet and then change the IP to one within the range you need.....then reserve that IP in the router settings and leave the others DHCP. The router doesn't need to assign an IP to it unless you absolutely want to run DHCP on it, but that would introduce other items to consider.
 
Take your LAN out of the equation, it's not needed to put an IP into the XEP....l
 
Why not just change the new routers subnet to the same one you had before??
That way any other devices that were static will still be ok too.
 
Subnet mask seems similar on both, or new router has same subnet mask.
 
Router is set up for DHCP.
 
I returned the XEP to the factory static IP of 192.168.0.251 using the jumper. I pinged this address and nothing came up.
 
I an not very good at networking, so am not sure how to go about connecting with crossover cable. Is it just a matter of connecting, and typing the XEP IP?
 
Again, my router address goes 192.168.1.xxx. Not sure if that would prevent it seeing the elk factory IP. But I DID see the XEP when i went to RP with factory IP. I just can't connect to control.
 
Seeing as your router address is 192.168.1.x, you probably wouldn't be able to ping the XEP @ 192.168.0.251 unless you adjust your subnet mask accordingly.
 
That said, you should still be able to access the XEP via RP, since that connection is going through the serial connection on the Elk... which should allow you to change the XEP address to a static address on the 192.168.1.x network.
 
Not sure I follow how the serial aspect comes into play - at the moment, it's a networking issue.

Te easiest thing to do is to leave everything connected as it is, but put a static IP on the computer that's in the same range as the XEP... You'll lose Internet and access to everything else but you'll be able to access the XEP to fix the subnet.

It do the jumpers and try to get the XEP on DHCP then you can find it...

Subnet Mask doesn't have a lot to do with subnets we're talking about... Except in very rare cases, a home would always be a class C network with a subnet mask of 255.255.255.0. We're talkin about the range of the IP address - the 192.168.1.x which is a different subnet than 192.168.0.x. If you want to get technical it's the SN Mask that decides if the range is big enough to include both those or if they're separate...

Try getting the XEP into DHCP - if you don't know networking that would be far easiest because you don't need to change things on your computer.
 
newalarm said:
Subnet mask seems similar on both, or new router has same subnet mask.
 
Router is set up for DHCP.
 
I returned the XEP to the factory static IP of 192.168.0.251 using the jumper. I pinged this address and nothing came up.
 
I an not very good at networking, so am not sure how to go about connecting with crossover cable. Is it just a matter of connecting, and typing the XEP IP?
 
Again, my router address goes 192.168.1.xxx. Not sure if that would prevent it seeing the elk factory IP. But I DID see the XEP when i went to RP with factory IP. I just can't connect to control.
Not the subnet mask, the subnet. IOW, make the routers LAN 192.168.0.1.
If the XEP is 192.168.0.x, and the routers LAN is 192.168.1.x, you will not be able to connect.
Just make the router 192.168.0.1 and be done with this madness.
 
Don't forget to reboot all devices after changing the LAN IP.
 
You can just go into your PC's network settings turn off DHCP and assign a static IP for 192.168.0.x.  Then your PC and Elk will be on the same subnet and you should be able to communicate.  No crossover needed
 
If you want to have internet access at the same time, then assign the PC a primary static address (turn off DHCP) on 192.168.1.x and go under advanced and give it a 192.168.0.x as well.  Then you will be able to communicate on both networks.
 
Adjusting the subnet mask would work too (like 255.255.0.0) but you have to do it on both the PC and the Elk, since you can't access the Elk you can't do that.  Or change your router's subnet/dhcp scope like Frunple said and it should re-ip all your devices with DHCP.  You may need to reboot them or do an ipconfig /renew on the command line to pick up the new address.
 
My point was that you don't have to be on the same network address space (PC and XEP) to configure the XEP via ElkRP. To show this, I just changed the IP address on my PC to a completely different network (172.20.1.x) while I left my XEP settings alone. I could still connect via ElkRP and get to the settings page to change the IP address (see attachment).
 
However, with this configuration, I would not be able to ping the XEP from my PC because of the network differences.
 

Attachments

  • XEP_Setup.jpg
    XEP_Setup.jpg
    134.3 KB · Views: 7
Additionally, I will say that I have found a couple of ISPs who assign 192.168.0.1 to their modems. If that happened to be the case, and the OP assigned his router to that address, there would be an IP conflict. Just something to consider.
 
Ok. status update. I changed the routers IP to 192.168.0.xxx and it worked like a charm. Though I do not see it when i look up the DHCP devices (i guess i would not since it is static), I could now ping it, and was able to connect with RP.
 
I made then was able to update ekeypad and now only have one account since new router supports nat loopback.
 
So back in business. I am really not very good at networking, but learned a few things. I really need to brush up more.
 
Thanks for the help everyone. As always, appreciate people taking time to help me out.
 
One last question. does it matter for security if the XEP stays on factory setting IP? Or is it better to give it a different IP.
 
Back
Top