Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

softconsole not able to see ipo on same network??? 1

Status
Not open for further replies.

Wallysworld

Technical User
Feb 20, 2007
255
CA
Hi All;

IPO 8.1.73 with latest softconsole

This was working for 2 months! Friday reception started complaining about not being able to connect to the IPO.
Same office, same network, same subnet.

The pc cannot ping the ipo i.p. either.

Can anyone tell me if these routes (that I did not put into the system) are to blame?

172.168.10.0 255.255.255.0 LAN 1 Directly Attached
172.168.10.0 255.255.255.0 Lan2(WAN) Directly Attached
172.168.10.0 255.255.255.0 Lan2(WAN) DHCP RAS

This one I did put in:
0.0.0.0 0.0.0.0 172.168.10.5 Static

The system ip is 172.168.10.145
The router ip is 172.168.10.5

If they ARE to blame, how would I get rid of them?

Thanks, as always.
 
It seems you have both LAN ports in the same address range, this isn't allowed :)



"No problem monkey socks
 
Is that even if LAN 1 is not connected to the network? I only have LAN 2 connected right now.
 
connect using the lan 1 connection

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.
 
Yes, they cannot be in the same range, it confuses the system.... put on or the other on another range :)



"No problem monkey socks
 
You are the MAN amriddle!
I started on LAN 1, was having issues, ported everything over to LAN 2 and just picked an available ip (within the same range).
Lesson learned.

Thanks again.
 
Cool, the system really should throw an alarm up... that's why people do it without realising :)



"No problem monkey socks
 
Why shpuld it trow a alram as it is plain stupid to give two nics on the same device the same ip address, anyone with ethernet skills knows that it will cause ip conflicts.
You don't give your second kid the same name as the first do you?
 
George Foreman did.

AND as I said, the 2nd port was not connected, so it "shouldn't" cause a conflict if they aren't both on the network.
As I said, lesson learned.
 
Even not connected it still is used internally, try it on your pc with a wireless and a wired nic, have fun.
Well, it will never hapen to you again and that is worth it, the best way to learn is to learn how not to do it and what happens if you made a mistake.
I was a bit harsh with the statement "plain stupid", I meant that only for those people who are supposed to be ethernet network pro's and we don't see them a lot here on the forum so please don't feel offended.
 
NO OFFENCE TAKEN!!!

Really, this place has been an awesome in assisting my learning curve. You could have mixed in a few more 4 letter words, then given the answer, and I would have happily toddled off on my merry way. HA!

Thanks again to all that reply, it is always appreciated.
 
Although in the past you could this is not an option anymore.
Even when you have both nic's in the same IP range.
It is a Lan and Wan port thus why you cannot do this.


BAZINGA!

I'm not insane, my mother had me tested!

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top