Cant connect through Remote Reb Workspace around a specific time each day
Hello
Has anyone know of any issues with SBS 2003 Standard where they cannot connect to desktops or servers remotely (RDP) through the remote web workspace, between a set time? This may sound odd, but a fresh SBS 2003 Standard install, and sometime between the hours of 16-1630 and 1700hrs each day, Remote Web workspace refuses to let us connect to either desktops or servers. We've checked the router, using Draytek 2800, and all known ports forwarded correctly. If we VPN to the server, then start an RDP session to either desktops or server it allows us to connect ok? but RDP works perfectly up until this time. Cant find anything in the event logs at the time to suggest something is wrong, and using netstat, nothing uses port 4125 at the time either. When attempting to connect 4125 show's my IP address as established. I checked the process that uses 4125 at the time (w3wp.,exe) - running issapp.vbs showed it was linked to the DefaultAppPool application pool. I through that maybe recycling this application pool might have fixed it but no, still cannot connect. This odd thing about this problem is its now just started to happen to another known SBS 2003 Standard Server that has good health.
Any thoughts welcome.
Has anyone know of any issues with SBS 2003 Standard where they cannot connect to desktops or servers remotely (RDP) through the remote web workspace, between a set time? This may sound odd, but a fresh SBS 2003 Standard install, and sometime between the hours of 16-1630 and 1700hrs each day, Remote Web workspace refuses to let us connect to either desktops or servers. We've checked the router, using Draytek 2800, and all known ports forwarded correctly. If we VPN to the server, then start an RDP session to either desktops or server it allows us to connect ok? but RDP works perfectly up until this time. Cant find anything in the event logs at the time to suggest something is wrong, and using netstat, nothing uses port 4125 at the time either. When attempting to connect 4125 show's my IP address as established. I checked the process that uses 4125 at the time (w3wp.,exe) - running issapp.vbs showed it was linked to the DefaultAppPool application pool. I through that maybe recycling this application pool might have fixed it but no, still cannot connect. This odd thing about this problem is its now just started to happen to another known SBS 2003 Standard Server that has good health.
Any thoughts welcome.
ASKER
unfortuantely, no specific errors. Users can log in anytime 24x7. I can remote web workpace to a server or workstation if establish a VPN connection during the time it doens't work (between 4-5ish each day) - but otherwise I can get in all other times from outside the network via forwarded port on the NAT router?
We have changed the router, still no joy - same sympton I'm now starting to wonder if for some reason it could be ISP related?
We have changed the router, still no joy - same sympton I'm now starting to wonder if for some reason it could be ISP related?
Is there, perhaps, some kind of IIS or MSDE maintenance scheduled around this time? I would be leaning towards a server issue other than hardware/connectivity as you say it works going direct over VPN during the problem window.
ASKER
There isn't any scheduled maintenance that I know of, in fact its a clean SBS install with no frills?
I am also having this problem. Can get the OWA to work inside the LAN but cannot connect from the outside world. Have forward all the relevant ports via the NAT. I know this is working as I tested a web page running on a different server?
This has really stumped me as it has now happened twice on SBS 2003 Standard and SBS Premium 2003
This has really stumped me as it has now happened twice on SBS 2003 Standard and SBS Premium 2003
ASKER
I do not understand why this problem is happening, but I am putting it down to the ISP (Tiscali) - I've checked and changed routers, checkd configuration, all looks ok. I now know of someone else who has the same problem and they are with Tiscali also?
However, I have found a workaround - I changed the listening port that Remote Web Workspace uses for the RDP connections. - Since changing port 4125 to something different, it works perfectly during the time it would normally fail. - To do this, navigate to the follow reg key:
HKLM\Software\Microsoft\Sm
Change the dword "Port" from 4125 to something different - I chose 4445 but I'm sure this isn't relavent.
Hey Presto! - It works flawlessly!
However, I have found a workaround - I changed the listening port that Remote Web Workspace uses for the RDP connections. - Since changing port 4125 to something different, it works perfectly during the time it would normally fail. - To do this, navigate to the follow reg key:
HKLM\Software\Microsoft\Sm
Change the dword "Port" from 4125 to something different - I chose 4445 but I'm sure this isn't relavent.
Hey Presto! - It works flawlessly!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Any specific error messages?
I'm guessing logon times are configured 24/7 too even though it works via RDP...