Hoping someone can help here - please be patient with me as I am the untrained non-techie bod in a satellite office. Our systems staff are in the USA and are more confused than me! Anyway: here goes.....
We've moved to a new office from serviced offices and now have to manage our own connection. I have a BT Business Hub 3 on ADSL (we're in a sleepy non-tech backwater called Reading [sarcasm intended]....no fibre here for some reason). I need to connect our Fortigate VPN box so that staff can do their stuff. This was connected in our old office like this:
- Ethernet cable into the office (from building owner's network) plugs into Fortigate WAN socket
- TP-Link Wireless AP plugs into one of the Fortigate external sockets
This all worked fine. There's a network switch in there somewhere too, but that's irrelevant to my current problem. My current set up is:
- ADSL line from the BT box on the wall into the back of the Hub
- Ethernet cable from the Hub into the WAN socket on the Fortigate
- The TP-Link remains connected to the Fortigate as above
I have a single static IP from BT that is used for the Fortigate.
The BT Hub wifi (lets call it network A) works perfectly well - no problems there. However, I need to use the wifi from my TP-Link (network B) so that the Fortigate is involved (please be patient with my terminology). I can see network B and can connect to and configure the Fortigate, but I can't see the outside world. If I switch back to network A I can see the world but obviously not the Fortigate.
The problem is why can't I use network A? Everything is configured correctly using the credentials supplied by BT (static IP, default gateway etc). Our systems guy has remoted on to my machine to check the Hub's settings and everything seems fine there too. Is the Hub doing "something" to prevent network A accessing the world?
I've seen this post ...can someone more knowledgeable than me discern whether I have the same issue?
Thanks for any advice!