Did you update? =P Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373
On Mon, Aug 15, 2011 at 5:15 PM, Rory McCann <rmm.li...@gmail.com> wrote: > Got it! > > I disabled/re-enabled the IP address on the interface to recreate the > dynamic route. Problem is resolved. Thanks Josh and everyone for the input. > > Rory McCann > *Minn-Kota Ag Products > P*: 701-403-4877*| E*: r...@mkap.com > > On 8/15/2011 4:08 PM, Josh Luthman wrote: > >> Can the MT ping a host in 72 and 1? >> >> What happens when you traceroute out from 72 or 1 to one another? >> >> Josh Luthman >> Office: 937-552-2340 >> Direct: 937-552-2343 >> 1100 Wayne St >> Suite 1337 >> Troy, OH 45373 >> >> >> On Mon, Aug 15, 2011 at 5:05 PM, Rory McCann<rmm.li...@gmail.com> wrote: >> >> Essentially, neither are talking to each other in any way, shape or form. >>> >>> I'm working on it remotely but the only device that can talk to both >>> subnets is the mikrotik that is on site. Due to cabling restrictions I >>> had >>> to run the .72.x subnet on the same layer 2 network as the existing .1.x >>> subnet. I have PPTP remote access set up and working. I am trying to get >>> the >>> PPTP client to talk to the devices on the .72.x subnet and it doesn't >>> want >>> to work. I can talk to the .1.x subnet just fine. >>> >>> I RDP'd into a server on the network and it also cannot talk to the 72.x >>> subnet, so I'm assuming there's a route that isn't getting distributed >>> properly or something funky. As I understand it, when a TCP/IP device >>> does >>> not know the location of something, it forwards the request upstream for >>> answers. Since all devices on the network have the same upstream router >>> (the >>> mikrotik) which already created the necessary routes dynamically for me, >>> I >>> am assuming no further static routes would be necessary. Is this the >>> correct >>> assumption? >>> >>> >>> >>> Rory McCann >>> *Minn-Kota Ag Products >>> P*: 701-403-4877*| E*: r...@mkap.com >>> >>> On 8/15/2011 3:58 PM, Josh Luthman wrote: >>> >>> What isn't talking to what? If the 72 machines can't talk to the 1 >>>> machines >>>> it may be because they're routing to a different router and the Mikrotik >>>> isn't sharing the subnets. >>>> >>>> Can a PC ping both 192.168.1.1 and 192.168.72.1 (or whatever IPs are on >>>> the >>>> MT)? >>>> >>>> Josh Luthman >>>> Office: 937-552-2340 >>>> Direct: 937-552-2343 >>>> 1100 Wayne St >>>> Suite 1337 >>>> Troy, OH 45373 >>>> >>>> >>>> On Mon, Aug 15, 2011 at 4:55 PM, Scott Reed<sr...@nwwnet.net> wrote: >>>> >>>> Put the addresses on the bridge, not the ports. >>>> >>>>> I have as many as 4 subnets on a an interface. Should work the same >>>>> for >>>>> a >>>>> bridge. >>>>> >>>>> >>>>> On 8/15/2011 4:37 PM, Rory McCann wrote: >>>>> >>>>> Is there some kind of limitation in ROS that prevents two subnets on >>>>> the >>>>> >>>>>> same interface from working properly? I have a 192.168.1.0/24 subnet >>>>>> and >>>>>> a 192.168.72.0/24 subnet on the same interface (it's actually a >>>>>> bridge >>>>>> of >>>>>> 3 ports) and for the life of me I cannot get them to talk to each >>>>>> other. >>>>>> >>>>>> Everything on the .72 subnet is static and the .1 subnet is assigned >>>>>> via >>>>>> DHCP by a Window Server. Am I better off moving .72 on to its own >>>>>> interface >>>>>> and tying it back into the switch from there or am I missing something >>>>>> basic? >>>>>> >>>>>> -- >>>>>> >>>>> Scott Reed >>>>> Owner >>>>> NewWays Networking, LLC >>>>> Wireless Networking >>>>> Network Design, Installation and Administration >>>>> >>>>> >>>>> >>>>> Mikrotik Advanced Certified >>>>> >>>>> www.nwwnet.net >>>>> (765) 855-1060 >>>>> (765) 439-4253 >>>>> (855) 231-6239 >>>>> >>>>> >>>>> >>>>> ______________________________******_________________ >>>>> Mikrotik mailing list >>>>> Mikrotik@mail.butchevans.com >>>>> http://www.butchevans.com/******mailman/listinfo/mikrotik<http://www.butchevans.com/****mailman/listinfo/mikrotik> >>>>> <http**://www.butchevans.com/****mailman/listinfo/mikrotik<http://www.butchevans.com/**mailman/listinfo/mikrotik> >>>>> > >>>>> <http**://www.butchevans.com/**mailman/**listinfo/mikrotik<http://www.butchevans.com/mailman/**listinfo/mikrotik> >>>>> <ht**tp://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik> >>>>> > >>>>> >>>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >>>>> RouterOS >>>>> >>>>> -------------- next part -------------- >>>>> >>>> An HTML attachment was scrubbed... >>>> URL:<http://www.butchevans.****com/pipermail/mikrotik/** >>>> attachments/20110815/ef2aaa01/****attachment.html<http://www.** >>>> butchevans.com/pipermail/**mikrotik/attachments/20110815/** >>>> ef2aaa01/attachment.html<http://www.butchevans.com/pipermail/mikrotik/attachments/20110815/ef2aaa01/attachment.html> >>>> > >>>> >>>> ______________________________****_________________ >>>> Mikrotik mailing list >>>> Mikrotik@mail.butchevans.com >>>> http://www.butchevans.com/****mailman/listinfo/mikrotik<http://www.butchevans.com/**mailman/listinfo/mikrotik> >>>> <http**://www.butchevans.com/mailman/**listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik> >>>> > >>>> >>>> >>>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >>>> RouterOS >>>> >>>> -------------- next part -------------- >>> An HTML attachment was scrubbed... >>> URL:<http://www.butchevans.**com/**pipermail/mikrotik/**<http://www.butchevans.com/**pipermail/mikrotik/**> >>> attachments/20110815/a47e39cc/****attachment.html<http://www.** >>> butchevans.com/pipermail/**mikrotik/attachments/20110815/** >>> a47e39cc/attachment.html<http://www.butchevans.com/pipermail/mikrotik/attachments/20110815/a47e39cc/attachment.html> >>> > >>> >>> ______________________________****_________________ >>> Mikrotik mailing list >>> Mikrotik@mail.butchevans.com >>> http://www.butchevans.com/****mailman/listinfo/mikrotik<http://www.butchevans.com/**mailman/listinfo/mikrotik> >>> <http**://www.butchevans.com/mailman/**listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik> >>> > >>> >>> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >>> RouterOS >>> >>> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL:<http://www.butchevans.**com/pipermail/mikrotik/** >> attachments/20110815/6c952343/**attachment.html<http://www.butchevans.com/pipermail/mikrotik/attachments/20110815/6c952343/attachment.html> >> > >> >> ______________________________**_________________ >> Mikrotik mailing list >> Mikrotik@mail.butchevans.com >> http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik> >> >> Visit http://blog.butchevans.com/ for tutorials related to Mikrotik >> RouterOS >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://www.butchevans.com/**pipermail/mikrotik/** > attachments/20110815/80d9aadf/**attachment.html<http://www.butchevans.com/pipermail/mikrotik/attachments/20110815/80d9aadf/attachment.html> > > > > ______________________________**_________________ > Mikrotik mailing list > Mikrotik@mail.butchevans.com > http://www.butchevans.com/**mailman/listinfo/mikrotik<http://www.butchevans.com/mailman/listinfo/mikrotik> > > Visit http://blog.butchevans.com/ for tutorials related to Mikrotik > RouterOS > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.butchevans.com/pipermail/mikrotik/attachments/20110815/cad80d28/attachment.html> _______________________________________________ Mikrotik mailing list Mikrotik@mail.butchevans.com http://www.butchevans.com/mailman/listinfo/mikrotik Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS
