problem with lan....

conuk · 12 Dec 2012 at 16:20

i have pc upstairs (windows 8)
hp micro server downstairs. (windows 7)

connected via ethernet to virgin super hub.
all connects - can transfer files between 2 no problem.

recently i cant connect via my nexus 7 or android phone via wifi. was using es file explorer to play films etc. if i search it finds the hp microserver ip address but just gives an error.

teamviewer works fine to access the hp server across wifi.

now i keep getting smb out of range etc etc... with file explorer

any ideas?

conuk · 12 Dec 2012 at 17:18

hmmm it seems to be working now after restarting the server. seems a bit hit and miss though. any reasons for this?

StarmanUK · 12 Dec 2012 at 17:36

One of those "Have you tried turning it off and on again?" moments?

Maybe related to the HDDs being spun down and the time out period expiring in the app while waiting for a response?

conuk · 12 Dec 2012 at 17:38

thanks never thought of that. will look into it.

conuk · 13 Dec 2012 at 18:51

had a look today. changed power settings on server.

went to connect via es file explorer....connection error.
hit teamviewer from nexus over wifi - connected no problem.

anybody know what i can try?

conuk · 14 Dec 2012 at 14:35

anybody guys?

bremen1874 · 14 Dec 2012 at 16:43

Have you looked at the Windows event logs?

blastman · 14 Dec 2012 at 17:13

sounds to me file the app es file explore is timing out when trying to connect.

how long does it take before it fails?

you do need to check the event logs as mentioned above. that'll stop you blindly stumbling around in the dark..

EDIT:: we run a sonic FW with a vpn client and I'm forever having to change peoples outlook settings from server names to ip addresses the dns lookup seems to nearly always timeout.

conuk · 14 Dec 2012 at 23:37

ok i checked the logs i see this error in the system log. this happens each i connect through es file explorer.

Level Date and Time Source Event ID Task Category
Error 14/12/2012 23:22:00 srv 2017 None The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.

lol this mean anything to you guys?

bremen1874 · 14 Dec 2012 at 23:41

Just stick 'The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations' into Google and there are plenty of suggested fixes.