• May 22, 2012, 08:57:05 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: routing port 445 traffic specifically  (Read 471 times)

0 Members and 1 Guest are viewing this topic.

Offline Filmad

  • Rookie
  • **
  • Posts: 1
routing port 445 traffic specifically
« on: September 02, 2011, 05:15:50 AM »
Hi,

We have a network with 2 gateways - 1 MPLS 1 aDSL, the core is a 4548 stack which has some simple routes defined, we wanted to route specific traffic (port 445 microsoft-ds) only via the aDSL all other via the MPLS, I have set up a static to the specific server address, but going forward we wanted to route the protocol to a specific gateway, any ideas

All help greatly appreciated.

Cheers


Offline Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 2517
    • Michael McNamara
Re: routing port 445 traffic specifically
« Reply #1 on: September 02, 2011, 03:31:55 PM »
Hi Filmad and welcome to the forums!

You can use a more specific route (as it sounds like you've done already) other than that there aren't a lot of options. Also the route will covey all traffic to that specific host not just TCP/445.

Good Luck!
We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline MisterAG

  • Rookie
  • **
  • Posts: 22
Re: routing port 445 traffic specifically
« Reply #2 on: September 07, 2011, 01:48:00 PM »
Most full blown routing platforms will allow you to perform 'policy routing', which is static routing for packets based on things like source/destination addresses and source/destination ports. I don't think that the 4500 switches can do policy routing at this time.

I'm finding that the 4500 / 5500 switches are good at switching / routing packets at speed, but don't work as I would expect for any real decision making.

We use Fortigate and Vyatta solutions here as edge devices, and they seem to work fine for what we need them to do - including policy routing. Why in particular are you tring to send SMB traffic across a different link? Have you got a WAN extention to another building?