Associate
- Joined
- 20 Aug 2007
- Posts
- 1,333
- Location
- Solihull
Hi guys,
One of my customer has recently had new broadband go live with a 3rd party provider called Aonix, who use Gamma connectivity - I'm experiencing some issues with stability and could use some advice/comments on the best patch forward. I'll first highlight the existing layout/scenario before the broadband provider changed:
All email/documents are held in office 365, so all the server is currently acting as is DHCP, but I believe there is one device that still logs into it as a domain (they had loads on their roaming profile desktop they didn't want to move at that point and it's the MD).
The new broadband, as mentioned, has been provided by Aonix on Gamma connectivity - I wasn't involved in the setup and just received confirmation that it had gone live a few weeks ago, users apparently hadn't noticed much change after a few days so I went in and did a few tests. It was then I noticed on speedtest.net that it was still showing up as MDNX as the provider. I had expected an engineer would have gone on site to set up their new connection but apparently not, I contacted them and was provided DSL login information, which I entered into the DSL router at 17:30 yesterday. I restarted the server and dsl router and once they had rebooted we were able to run speedtests and they would show up as Gamma instead of MDNX, meaning that the new settings were surely working, so we left the office for the night.
I had hoped that was the end of it, sadly I got a call this morning at 8.30am from the MD saying that everything kept dropping off. I got him to do some ping tests at google public dns, they went through just fine. However everytime he tried to access a webpage from any browser the connection would hang for ages then the page would fail to load; sometimes flushing the cache and using ipconfig /renew/release helped but the problem would just appear again later.
I tried changing the ipv4 adapter settings on the MD's PC and the Server to use 8.8.8.8 and 8.8.4.4 as primary and secondary DNS servers and it's still unstable.
Can anyone advise what could be causing this? Ping tests work consistently at a nice, low MS but web pages are intermittent - this suggests to me (in my decent networking experience) that it is going to be a problem with DNS or DNS caching somewhere.
Would it be wise to rip the server out from doing DHCP completely? If I do rip the server out, should I enable DHCP on the DSL router or could I even do it on the wireless access point? My brain hurts from this so be nice please!
Cheers,
Jamie
One of my customer has recently had new broadband go live with a 3rd party provider called Aonix, who use Gamma connectivity - I'm experiencing some issues with stability and could use some advice/comments on the best patch forward. I'll first highlight the existing layout/scenario before the broadband provider changed:
- ADSL connection from MDNX, connected to a DSL router using PPPoE
- DHCP disabled on DSL router
- Router is cabled into the back of their old Server 2003 machine, which has DHCP enabled
- Server routes back to a switch/wireless access point
- Multiple PC's and laptops connected to the Wireless access point, a few use ethernet via switch
All email/documents are held in office 365, so all the server is currently acting as is DHCP, but I believe there is one device that still logs into it as a domain (they had loads on their roaming profile desktop they didn't want to move at that point and it's the MD).
The new broadband, as mentioned, has been provided by Aonix on Gamma connectivity - I wasn't involved in the setup and just received confirmation that it had gone live a few weeks ago, users apparently hadn't noticed much change after a few days so I went in and did a few tests. It was then I noticed on speedtest.net that it was still showing up as MDNX as the provider. I had expected an engineer would have gone on site to set up their new connection but apparently not, I contacted them and was provided DSL login information, which I entered into the DSL router at 17:30 yesterday. I restarted the server and dsl router and once they had rebooted we were able to run speedtests and they would show up as Gamma instead of MDNX, meaning that the new settings were surely working, so we left the office for the night.
I had hoped that was the end of it, sadly I got a call this morning at 8.30am from the MD saying that everything kept dropping off. I got him to do some ping tests at google public dns, they went through just fine. However everytime he tried to access a webpage from any browser the connection would hang for ages then the page would fail to load; sometimes flushing the cache and using ipconfig /renew/release helped but the problem would just appear again later.
I tried changing the ipv4 adapter settings on the MD's PC and the Server to use 8.8.8.8 and 8.8.4.4 as primary and secondary DNS servers and it's still unstable.
Can anyone advise what could be causing this? Ping tests work consistently at a nice, low MS but web pages are intermittent - this suggests to me (in my decent networking experience) that it is going to be a problem with DNS or DNS caching somewhere.
Would it be wise to rip the server out from doing DHCP completely? If I do rip the server out, should I enable DHCP on the DSL router or could I even do it on the wireless access point? My brain hurts from this so be nice please!
Cheers,
Jamie
