Associate
- Joined
- 25 Jun 2009
- Posts
- 440
- Location
- UK
Afternoon,
Hoping someone with a bit of knowledge on networking might be able to help with this one. I've got a server PC that sits on standby which is set to wake on pattern match so as soon as I try to access it over the network, it will come on. That side of it works fine.
However, on the machine I am using to access the shared folders on the server, I will get one of two scenarios:
a) Windows file explorer pauses for a few seconds while the server powers on (maybe, 3-4 seconds) and then I instantly get access to the shares. This is the ideal situation.
b) Windows file explorer pauses for a few seconds, then returns an error that the network location cannot be accessed, and will refused to access the shares for a good 20-30 seconds.
At the moment I am getting scenario B and it's getting on my **** - it started when I changed my router from a TP-Link with Gargoyle f/w to a Netgear R7000, so I'm going to assume there is something different going on in the firmware that's causing it. It was never an issue before this, nor was it an issue when I was using an old BT Homehub 4.
I've tried searching online for an answer to this but I'm turning up blanks. The best I found was that it might be something to do with ARP tables but I'm into unknown territory, so hoping someone here might have an idea what's going on.
Cheers
Hoping someone with a bit of knowledge on networking might be able to help with this one. I've got a server PC that sits on standby which is set to wake on pattern match so as soon as I try to access it over the network, it will come on. That side of it works fine.
However, on the machine I am using to access the shared folders on the server, I will get one of two scenarios:
a) Windows file explorer pauses for a few seconds while the server powers on (maybe, 3-4 seconds) and then I instantly get access to the shares. This is the ideal situation.
b) Windows file explorer pauses for a few seconds, then returns an error that the network location cannot be accessed, and will refused to access the shares for a good 20-30 seconds.
At the moment I am getting scenario B and it's getting on my **** - it started when I changed my router from a TP-Link with Gargoyle f/w to a Netgear R7000, so I'm going to assume there is something different going on in the firmware that's causing it. It was never an issue before this, nor was it an issue when I was using an old BT Homehub 4.
I've tried searching online for an answer to this but I'm turning up blanks. The best I found was that it might be something to do with ARP tables but I'm into unknown territory, so hoping someone here might have an idea what's going on.
Cheers
Last edited:
