SBS2003 R2 Brand New Fully Patched Remote Access via VPN & WWP, Win XP SP3
Hello All
Im having a real problem with remote access, system details are as follows:
1 x DELL SC440 Server (LAN IP 10.0.0.4)
1 x Intel Xeon Dual Core 2.13Ghz Processor
2 x 146GB SAS HDD RAID1
4 x 1024MB ECC RAM
O/S MS SBS 2003 R2
A/V Kaspersky Business Secuirty Suite
IE v 7.0.5730.13
6 x DELL Optiplex
1 x Intel Core 2 Quad Q6600 Processor
4 x 1024MB RAM
1 x 160Gb SATA HDD (60gb/100gb Split)
O/S MS Windows XP Pro SP3
A/V Kaspersky Business Security for MS Win Desktops
IE v 7.0.5730.13
1 x HP Procurve 1800 8G Network Switch
1 x Linksys WRT54GS Modem (LAN IP 10.0.0.1)
All the kit is 7 days old, brand new fresh installation and its all configured and working fine except for the remote access, which has the following issues:
VPN
Attempts to VPN results in a connection being made, then it verifies username and password, thats where it stops, it never gets past the veryfing process. Ive run the CEICW and checked all the configuration, no issues are apparent. Ports 25, 80, 443, 444, 1723, 3389 & 4125 are set to port frowarding to 10.0.0.4 in the Linksys. VPN Passthrough is also checked.
OWA
No issues, you can access and use OWA as one would expect to.
Remote Web Workplace
You can get to the remote web workplace by entering static IP Address/remote but when you chose the option connect to my computer at work you get the following error message:
This Portion of Remote Web Workplace requires the Microsoft Remote Desktop ActiveX Control. Your browsers security settings may be preventing you from downloading ActiveX controls. Adjust these settings, and try again.
Terminal Service
From the SBS Managment Console select Client Computers and look at the list, highlight any of the PCs (they are all there) and click on the Connect to Computer via Terminal Services the connecting window appears for a plit second and nothing happens.
Given that the OWA works without issue and the Exchange server is receiving e-mail direct I know that the Static IP is poitning to the correct place.
Ive already tried the solutions posted on this site for the Remote Web Workplace which included:
Click on Tools -> Manage Add-Ons - > Enable or Disable Add-Ons in IE to enable Terminal Service ActiveX Control but its not there.
Ive logged in as every user on every PC and Deleted the System Registry Settings identified in the workaround.
Im back to square One, no remote access and no VPN does anyone have any other suggestions?
Help!
Im having a real problem with remote access, system details are as follows:
1 x DELL SC440 Server (LAN IP 10.0.0.4)
1 x Intel Xeon Dual Core 2.13Ghz Processor
2 x 146GB SAS HDD RAID1
4 x 1024MB ECC RAM
O/S MS SBS 2003 R2
A/V Kaspersky Business Secuirty Suite
IE v 7.0.5730.13
6 x DELL Optiplex
1 x Intel Core 2 Quad Q6600 Processor
4 x 1024MB RAM
1 x 160Gb SATA HDD (60gb/100gb Split)
O/S MS Windows XP Pro SP3
A/V Kaspersky Business Security for MS Win Desktops
IE v 7.0.5730.13
1 x HP Procurve 1800 8G Network Switch
1 x Linksys WRT54GS Modem (LAN IP 10.0.0.1)
All the kit is 7 days old, brand new fresh installation and its all configured and working fine except for the remote access, which has the following issues:
VPN
Attempts to VPN results in a connection being made, then it verifies username and password, thats where it stops, it never gets past the veryfing process. Ive run the CEICW and checked all the configuration, no issues are apparent. Ports 25, 80, 443, 444, 1723, 3389 & 4125 are set to port frowarding to 10.0.0.4 in the Linksys. VPN Passthrough is also checked.
OWA
No issues, you can access and use OWA as one would expect to.
Remote Web Workplace
You can get to the remote web workplace by entering static IP Address/remote but when you chose the option connect to my computer at work you get the following error message:
This Portion of Remote Web Workplace requires the Microsoft Remote Desktop ActiveX Control. Your browsers security settings may be preventing you from downloading ActiveX controls. Adjust these settings, and try again.
Terminal Service
From the SBS Managment Console select Client Computers and look at the list, highlight any of the PCs (they are all there) and click on the Connect to Computer via Terminal Services the connecting window appears for a plit second and nothing happens.
Given that the OWA works without issue and the Exchange server is receiving e-mail direct I know that the Static IP is poitning to the correct place.
Ive already tried the solutions posted on this site for the Remote Web Workplace which included:
Click on Tools -> Manage Add-Ons - > Enable or Disable Add-Ons in IE to enable Terminal Service ActiveX Control but its not there.
Ive logged in as every user on every PC and Deleted the System Registry Settings identified in the workaround.
Im back to square One, no remote access and no VPN does anyone have any other suggestions?
Help!
Also does Kaspersky Business Secuirty Suite have firewall software that could be blocking connections?
ASKER
EPOHL
1) Firmware Version 7.50.2
2) RWW yes added Trusted site to each and every user!
3) No Firewall in the KAV Security Suite (there is but it's turned off)
1) Firmware Version 7.50.2
2) RWW yes added Trusted site to each and every user!
3) No Firewall in the KAV Security Suite (there is but it's turned off)
Go ahead and update Linksys to the latest firmware. Do you happen to have another type of router you could try just to rule it out as a cause for VPN problem?
ASKER
EPOHL
The router is on the latest version of Firmware, no updates have been released for the Version 7.
No secondary router here to check for VPN Issue, I'll have to order another one from somewhere
The router is on the latest version of Firmware, no updates have been released for the Version 7.
No secondary router here to check for VPN Issue, I'll have to order another one from somewhere
If you have a WRT54GS version 7, then 7.50.5 firmware should be available.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
RWW - Have you tried adding this as a trusted site on the machine you are connecting from ? Also can you verify remote desktop is enabled on the PC you are attempting to connect to?