So, we ran into an issue the other day, when we were suddenly unable to access a few of our client's domains. This was only an issue from inside our office network. External resources and other users outside our network had no trouble connecting to these sites.
We never did get to the bottom of it. Instead, we removed our router and the problem went away.
But... this meant reconfiguring our modem from bridge mode to routing mode. To be clear, we did not have to do this. Shaw (our ISP) did this reconfiguration remotely.
Unfortunately, this meant that I had to add all of our previously forwarded ports to the "new" machine. I ran into a problem when I got to configuring the SSH forwarding. We are using the SMCD3GN modem/router we got from Shaw and when I tried to add the pre-configured SSH forward, I received an erro message telling me that my setting "Conflicts with Remote Management Ports!".
After cursing Shaw for making my life more difficult, I decided that there was more than one way to skin this cat. On my server, i reconfigured SSH to use a different port (I went with 222 rather than 22). ...then on the "router" (#scarequotes), I added a user-defined service which I called MySSH and set up the forwarding on port 222.
This solved the problem and I can now SSH into my server.
1 comment:
Post a Comment