Hi, I'm sorry to resurrect this thread, however because my experience at the moment is pretty much exactly the same I thought I would use this thread and it's current info rather than start a new one. I have tried to follow this thread, as well as the tutorial already mentioned and then a couple of...

<Fred Rogers voice> See, I knew you could. </Fred Rogers voice> Good job. That trick of enabling and disabling rules is invaluable as you're trying to hack your way through a problem. Also very good, is LOG action rules - which do nothing other than log the packet patch to the logs. Glad you found ...

It's really unlikely that I'd have time anytime soon. Still, I think your best bet is to look and see what's different between the two port configurations. The things I've asked you to do, really shouldn't take more than 30 minutes or so. Yes, they are a pain. But they are invaluable in narrowing d...

Then you need to start looking at other things. Mangle rules. NAT rules I seriously doubt there is a bug, and the RB sees every port, essentially the same. There's no difference between one port and another. So, if it connects on eth2, and not on eth0, then you must have something configured on eth...

Just got off the phone with cox and they verified that the cisco modem is wide open and no ports are being blocked. this is a business account.

If you connected via the LAN [another port on the RB] then it's one of two things. 1) Something in the MTK is blocking connections to the WAN port. Firewall rule is a prime example here. 2) Something in the path is blocking PPTP connections. I've given you some hints on #1 - but I'm not sure how yo...

Well guys I'll be honest and say that it doesn't seem like the clients are even hitting the router when performing the pptp connection. This really baffles me because I have this router on the edge connected to cox's modem with a static IP from Cox. When I ping the WAN ip and have the packet sniffer...

After further testing from within the same network as the microtik I was able to connect a client just fine. Does this mean that you essentially put the client hanging off one of the WAN ports of the MicroTik - just via an ethernet cable. Gave both appropriate IP addresses and it worked. Correct? I...

After further testing from within the same network as the microtik I was able to connect a client just fine. So I know the pptp server is setup correctly. what other WAN requirements are needed for this to work? there must be something missing on the microtik.

thanks

In Winbox, go into your firewall rules and place three rules right at the top. One to allow all input One to allow all output One to allow all forwards. Then you can "enable" or "disable" them for your test. Enable them and try the PPTP connect. If it works, then you have a fire...

Sure does, and ppp, pppoe etc. :D I do not see any actual PPTP entries in the log though. We need to confirm the PPTP packets are arriving at the Mikrotik as the issue may be at the client side ? Is the client a fixed IP ? If so add an Input rule with the necessary source address and action of LOG ...

thanks for your help. does this look like i've enabled pptp-info logging

http://wiki.mikrotik.com/wiki/Manual:Li ... nse_Levels

Level 4 allows 200 PPTP clients so I do not think that is the issue.

What does the Mikrotik Log show ?

There is an excellent article at Greg Sowell's site http://gregsowell.com/?p=680 You might also like to turn on logging for PPTP /system logging add action=memory disabled=no prefix="" topics=pptp This should help in debugging. Are you using L2TP over IPSEC or PPTP on the Windows PC ? Dou...

I have seen countless articles and howto's on doing a PPTP Server from the MikroTik and connecting a Windows XP or Windows 7 client but with all the different options I still can't connect. I usually get the Error 800. I'm basically connecting a Windows 7 Client over the Internet and into the Router...