Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 785
  • Last Modified:

Remote Web Workplace stops working in SBS 2008

I am having a problem with Remote Web Workplace on SBS 2008. The remote.domain.com website stops working several times a day. If I restart the website it works again for awhile then stops again. It also works fine from the server and the problem only happens from workstations.
This link documents the exact issue I am having:
http://www.petri.co.il/forums/showthread.php?t=33408

There is one caveat to all of this. I never had a problem until a couple weeks ago when I had to re-IP the network when the office changed locations. The prior IT guys had setup the office on a 192.168.1.0 network that naturally created problems for VPN access. I changed everything to a class A range and updated all the IPs in DNS/Echange/IIS, etc. Everything works fine except for this problem.
Any ideas? There are no errors that I can find in the Event Logs or IIS logs.
0
csandlin
Asked:
csandlin
  • 4
1 Solution
 
MSWarriorCommented:
Sounds like there might be some sort of IP filtering setup. Check this:
http://www.eggheadcafe.com/conversation.aspx?messageid=31615560&threadid=31615331
0
 
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
There is a proper way and a not proper way to change the IP range for SBS 2008 networks.

Here is the proper way:
http://blog.mpecsinc.ca/2009/03/sbs-2008-how-to-change-servers-ip.html

Philip
0
 
csandlinAuthor Commented:
MSWarrior:
The website works fine most of the time but intermittently stops responding to requests, I doubt it is an IP filtering issue since the site is being accessed by the same IPs and no settings or filter rules are being changed. Plus restarting the website fixes the problem.
Hi Philip, is this officially documented somewhere as the correct way or did you create this from the 2003 SBS documentation? I did not follow that exactly but the process was similar. I first changed the IP address on the server. Then I changed all DNS records accordingly, scavenged and then manually deleted old records and searched the DNS file to make sure there were no old/stale records. I set the DNS server to only listen on that IP and incremented the serial number. I also updated the IPs in Exchange. Running the Fix My Network wizard gave the message that Component ID #3 is broken (because only Windows auth was enabled on the RPC virtual directory). I doubt that is related but I fixed it.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
csandlinAuthor Commented:
Ended up calling Microsoft to figure out the solution.  They had me follow the steps listed here: http://blogs.technet.com/sbs/archive/2009/02/10/slow-connectivity-for-outlook-anywhere-and-sites-that-use-the-sbs-web-applications-app-pool.aspx and also install hotfix 367928 and reboot. Problem seems to be resolved.
 
0
 
csandlinAuthor Commented:
Correction, that is KB959816, not 367928.
0
 
csandlinAuthor Commented:
PAQ
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now