xR34P3Rx's questions

I have an odd issue that i have not come across before.

I have a Fortinet firewall and i have a remote access L2TP VPN configured through the VPN Wizard, works great. The L2TP Client has a public IP address, its a VPS. While it is off the VPN, i am able to ping its public IP just fine from my firewall and internal LAN. As soon as i connect my VPS to the L2TP VPN, both my firewall and internal network are unable to ping the public IP of the VPS BUT, any other external computer like my cell phone or my work computer can access the VPS just fine. Only my firewall and LAN are affected.

I made sure that the VPN routes do not have priority over the public interface default route.

When i run traceroute <public ip> on my lan computer, it just times out giving me no info.

As soon as i disable the L2TP VPN on the VPS, connection is restored...

I don't even know where to begin troubleshooting with this one... Any ideas?

So i came across my HD space getting full too quickly and after doing some inspecting with wireshark and powershell. It seems my email server is being used as a relay for spam.

1. I closed port 25 on my firewall suspecting the spam was external but the queue kept filling up.
2. I ran wireshark and filtered ports 25,587 and 465 to see if any other device on the network was sending emails to my server but i did not see any external traffic coming into the server.
3. Ran TCP dump on the only 2 linux machines i have for the same ports and did not see any traffic as well.

right now im currently running virus scans on my exchange server to see if it somehow got infected. But the queue keeps sending emails to some domain called "desmondelliottprize.org.uk"

Is there any way i can block messages to a domain in ECP from sending or reaching the queue? I need to figure out what is spamming my server but in the mean time i figure i block it temporarily while i get it fixed so my IP doesn't get blacklisted.

So i have this customer who recently upgraded their Exchange server from 2007 to 2010.

Another pair of techs performed the migration and they left behind the old original database. Well the General Manager onsite wants to recover some emails from back a couple years but they are most likely in the old database.

So i tried recovering the database from 2010 by mounting it as recovery using:

New-MailboxDatabase -Recovery -Name <RDBName> -Server <ServerName> -EdbFilePath <RDBPathandFileName> -LogFolderPath <LogFilePath>

The EDB does add to exchange but it is unable to mount due to what we think is either disk space on the server (Which is a VM already maxing at 2TB, so expansion is not possible on a MBR table) or the database is corrupt somehow.

I did use ESEUTILS to make sure it was at a clean shutdown and tried mounting it again with a new copy but i still got the same error.

So the onsite IT guy made a VM on his PC and installed Exchange 2007 trial for use to try and recover the mailboxes in their original environment.

I have followed instructions on recovering from a Recovery Storage Group but I have not been quite successful with getting mailboxes restored, at least from the GUI.

Just now i tried using the CLI instead and ran:

Get-Mailbox

and this did not output anything. So from the Management Console i made sure that the Recovery Database was mounted then tried to specify what Storage Group to display using Get-StorageGroup -Identity RecoveryStorageGroup | Get-Mailbox, Get-Mailbox -StorageGroup RecoveryStorageGroup but i get 0 output.

I did some research on the database, somehow, maybe being empty? I'm assuming that even if its a recovery database, i should still be able to list the mailboxes that it contains, right?

I'm not sure what else i can try and i don't think we want to go get some Third Party software just to recover a hand-full of emails. Any other suggestions would be appreciated!

So this weekend i have been working on migrating my apache2 server to a docker container which i have no issues with.

I currently have a windows server with SSTP and Exchange 2016 both using port 443 for traffic.

The idea is to have incoming 443 traffic to be forwarded to my ubuntu server and apache will decide based on the aliases i gave the virtual hosts, where the user will be redirected to. This i have working BUT what if a user is trying to connect to the VPN that also uses port 443? How would i be able to redirect that traffic to my server?

What i had thought was to create a rule for IPTABLES to have the destination be vpn.domain.com and forward it to the server but since all subdomains/CNames are just aliases leading to the same host (my external IP), therefore all requests on port 443 will just be sent to the windows server bypassing my webhost which is not what i want.

What i also actually tried was to use apache to forward any incoming connections on 443 via ServerAlias vpn.domain.com to the windows server since its on 443 but that did not work.

Im not sure how i can go about this and im thinking i would just need to create a new VPN service on my ubuntu server afterall. If there is any way i can achieve what i need, that would save me the hassle.

Thanks

I have setup a VPN server with Server 2k12 and i have set it up behind an NAT and external/remote clients can connect via PPTP just fine. I was having issues with L2TP but i further read that L2TP has issues when the server is behind a NAT (if this is not entirely true, i would like to know how to get L2TP working as well). So now i am trying to setup SSTP for windows clients.

I already attained a legit certificate with COMODO and got it imported onto my server through IIS. I created the request and then completed it with the response i got from COMODO and i configured my VPN server to use that certificate. All ports are forwarded for L2TP, PPTP, IPSec, HTTPS (443 for SSTP). But i am unable to connect even from a client in the same network as the server. Because of that i marked off a firewall issue as being a possibility.

The error i get on windows 10 is "the remote server is not responding in a timeley fashion"

I have tried to change authentication settings on the client side but that has had no effect. I also have reviewed multiple tutorials on how to setup SSTP and even with the exact settings i still cant connect from either a local client or remote client.

I followed these tutorials:

Setup an SSTP SSL VPN in Windows Server 2012 R2

How to setup an SSTP VPN server with Windows Server

Im fairly new to VPN's so i have just gone with my gut on changing client settings hoping it would connect. From what i can say, the protocols are allowed through the server's firewall and also from the client and home router. Im not sure where its failing. im thinking it could be my certificate? perhaps i bought the wrong one?

Much help appreciated!

Ok so i have a Linux server handling the DHCP, and FTP server i have and Network Shares. Then i have a Server (Windows R2) with just the AD. None of the client computers can connect to the Domain. The way i fixed this before, was the DHCP was on the Windows Server, back then when i had it on there. Today i moved the DHCP to the Linux computer and now, like stated before, clients cant connect. I want to know if moving the DHCP was the error? When using an AD, does the same computer have to run the DHCP? or is there something else thats not letting the clients connect?

Im subnetting my network:
Scope is 192.168.1.0 /28
Range: 192.168.1.2-192.168.1.14 (leaving 192.168.1.0 as the Network, 192.168.1.1 as the       Router/DNS/Default Gateway, 192.168.1.15 as the broadcast address)
Server addresses:
Linux: 192.168.1.6
Windows: 192.168.1.2
rest are for clients, i am thinking of changing the ip of my linux server to 1.3, just to have them close together...