cannot see/ping remote ipo 500v2 8.1.67 1

[Wallysworld]

Hello all;

I cannot seem to find which little tab or setting is messing with my mind.

I've got 2 ipo's that I connect to through an rdp connection.
Both systems are 500v2's @ 8.1.67 and up until a week ago I was able to program both sides.

I can program the local side (A) no problem but not the remote side (B).
From my local computer I'm able to ping the local router, the remote router, and a computer on the far side but not the ipo (on the far side).
If I go into System Status (A) I can ping (B), but I can't connect to (B) through System Status, Monitor or Manager!

I know the i.p. is right because a computer on the remote side IS able to ping (B) AND can connect using manager.
I had the customer shut off the IPO (B) and ping the i.p. address to verify there wasn't a conflict on the remote side.

I.T. claims they haven't changed anything.

Does this seem like there is an obvious fix? Any suggestions always appreciated.

Thanks.

 

[DavidCT]

Sounds like the default gateway at Site B has been changed, with the ONLY exception being your statement, "If I go into System Status (A) I can ping (B), but I can't connect to (B) through System Status, Monitor or Manager!".

I would check the local PC at Site B for what the subnet and gateway address is.
Then on the IPO at Site B I would verify the subnet matches (LAN1 or LAN2 tab) and the gateway matches (IP Route).

 

[Wallysworld]

Thanks for the reply DavidCT;

I've doublechecked the ip route several times. My route(B)is:

ip: 0.0.0.0
ip Mask: 0.0.0.0
gtwy: definitely the gateway ip for the remote router @ site B

The ip address & subnet was also not changed from the beginning (I've doublechecked that several times as well).

Is there anything else which could affect remote connection?
I'm wondering if this could be a problem with the SD card?

Thanks again.

 

[amriddle01]

Can the IPO(b) ping anything outside its own subnet? Can it ping its own router?



"No problem monkey socks

 

[Wallysworld]

I'll verify that later this morning.
Thanks amriddle01.

 

[Wallysworld]

So, I've finally gotten onto a local pc and loaded the Administrator programs on it.
From the local pc I can open manager and make changes.
I can open Monitor but not connect to the system and I CANNOT open SSA. It says "No response on this ip address and port".

While I'm able to connect, does anyone have any suggestions?

 

[amriddle01]

Sounds like an IP conflict to me



"No problem monkey socks

 

[amriddle01]

I have also seen such issues when idiot IT folks use a Sonicwall to route between VLANs



"No problem monkey socks

 

[amriddle01]

VLANs/subnets I should have said



"No problem monkey socks

 

[Wallysworld]

Thanks again amriddle;

that's what I thought too, but I had the customer unplug the system last night and try to ping it, he says there was nothing else there. I'll try and reboot it now and see if there's anything else.

 

[Wallysworld]

Ping the IPO get a reply.
During a reboot of the IPO, no replies.
Back up again, get a reply.

Dang.

 

[Wallysworld]

When I go into "Network Viewer" and do a discover, it finds both systems and has the proper names associated with them.

Just one last thing, there are no firewalls on the pc I'm trying to connect to the IPO with.

Double Dang.

 

[amriddle01]

Try changing the port on the system, so re address the ports and change your route accordingly



"No problem monkey socks

 

[Wallysworld]

Ya lossed me.

Do you mean change the ip address of the system? or change the port that SSA is accessing the IPO?

 

[Wallysworld]

*lost

 

[amriddle01]

Swap the address of LAN and LAN2/WAN ports in case the port is buggered



"No problem monkey socks

 

[amriddle01]

BTW is the "local" PC actually in the same subnet/address range or is it routed at some point



"No problem monkey socks

 

[Wallysworld]

Hmmm...

that would imply that I have the LAN 2 port connected... short answer is it's not.

Now I will have to wait until tomorrow to have them plug in the 2nd port.

Thanks Andy, hopefully, it proves to not be a physical port issue as this box has only been onsite for 6 weeks.

 

[Wallysworld]

And the pc is in the same subnet/address range.

 

[Wallysworld]

Just a follow up, I was at 8.1.67 and upgrading to 8.1.73 resolved my issue.
It was odd that I was able to connect to the 2nd system for almost 3 months and then not able to... just upgrading to .73 has fixed it?

Thanks again for your quick responses.