|
|
I have just come across a strange problem accessing ftp site via IE7 on a client machine on an SBS 2003 nework specifically the companies house website, when the client tried to right click and save as, they would get ‘ The connection the the server has been reset ‘ error message and the good old ‘ This page cannot be displayed ‘ when trying to browse the ftp site.
On their particular setup they have a adsl modem connected to the 2nd nic on the sbs server so all the internet traffic is routed via the server.
To cut a long story short the solution was to disable Receive Side Scaling on the Server (Broadcom) nic not the internet nic i right clicked the Local Area Connection and clicked properties, click configure next the to the network adaptor, click the advanced tab, choose Receive Side Scaling and set to disable, (Warning this temporarily disconnects the server from the network).
After a little bit more research on this problem i came across a KB article on the subject appearently it effects serveral versions of Windows server 2003 SP1 & SP2 and SBS 2003 & R2, in this article Microsoft suggest disabling RSS via a registry key although i have not tried this solution. KB927695
First of all can i just say how completely rubbish CA’s website is you can’t find anything on.
But appart from that they have released a patch for CA Integrated Threat Management r8.1 for Windows 7 support. It allows the product to download updates which is always nice in a anti virus product
Instructions:
1) Stop the eTrust ITM Services:
CA Pest Patrol Realtime Protection Service (If present)
eTrust Antivirus Realtime Service
eTrust ITM Job Service
eTrust ITM RPC Service
2) Rename the current c:\Program Files\CA\SharedComponents\CAUpdate\CAUpdate.dll to CAUpdate.old
3) Copy the appropriate file, CAUpdate x86 or CAUpdate x64 to the SharedComponents\CAUpdate folder and rename to CAUpdate.dll
4) Restart all of the stopped eTrust ITM services
*Note, after ITM Agent machine updates to ITMCommon version 8.1.664 it will overwrite the CAUpdate.dll that was replaced.
You will need to replace the CAUpdate.dll (again) by following steps 1-4.
I can’t remember where i got this info from but thank you.
This is something i am always forgetting so here it is, the best way to find your optimal MTU setting is to use the ping command, open your command prompt and use the following command.
ping www.google.com -f -l 1500 (lower case F and L not a 1)
you will receive something similar to this.
Pinging www.l.google.com [66.102.9.105] with 1500 bytes of data:
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Ping statistics for 66.102.9.105:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Now you need to drop the packet size down by 10 bytes until you find one that doesn’t fragment in this case it was dead on 1430 but you can increase the byte size by small factors eg 1431, 1432 etc until you find that largest possible packet for your situation.
Pinging www.l.google.com [66.102.9.103] with 1430 bytes of data:
Reply from 66.102.9.103: bytes=64 (sent 1430) time=100ms TTL=54
Reply from 66.102.9.103: bytes=64 (sent 1430) time=70ms TTL=54
Reply from 66.102.9.103: bytes=64 (sent 1430) time=64ms TTL=54
Reply from 66.102.9.103: bytes=64 (sent 1430) time=64ms TTL=54
Ping statistics for 66.102.9.103:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 100ms, Average = 74ms
Now you need to add 28 to the maximum size for the overhead the IP headser and the ICMP Echo Request, so I end up with 1430+28=1458 then you can use a tool like DrTCP to change the MTU value
Just in case i ever need to repair the database again which seems to go funny more often than you would expect.
Yosemite KB TID:001583
Yosemite Backup incorporates a “self repairing” (ha!!!) database, however it may
occasionally be desirable to manually initiate a database repair operation.
TO REPAIR THE YOSEMITE BACKUP CATALOG MANUALLY:
1. Close Yosemite Backup
2. Stop the Yosemite Backup Service:
A. Open a Command Prompt (Start > Run > CMD {ENTER})
B. To change to the Yosemite Backup Directory type the following at a
Command Prompt:
1) CD\ {ENTER}
2) CD “Program Files” {ENTER}
3) CD Yosemite {ENTER}
4) CD “Yosemite Backup” {ENTER}
C. Type the following at the Command Prompt:
ytwinsvc -x {ENTER}
D. This will stop the Yosemite Backup Service on the local machine.
3. Open the ytconfig.ini file in the Yosemite Backup directory
([Install_Path]\config, by default) on the Master Server.
4. In the [configuration] section, add the following line:
repairDatabase=Yes
5. This section should now look like this:
[configuration]
lastUser=admin
lastDomain=Yosemite Backup Storage Domain
nodeGuid={00001001-421F132A-0003F771-FFE580D7}
databaseServerAddress=localhost
isDatabaseServer=Yes
databaseServerName=Yosemite Backup Storage Domain
disableNetwork=No
remoteAdmin=No
repairDatabase=Yes
6. Save and close this file.
7. Open Yosemite Backup 8 – DO NOT RESTART THE SERVICE.
8. The catalog repair will run automatically.
9. After the repair has completed the Login screen will appear. Close this
window.
10. Restart the Yosemite Backup Service:
A. Open a Command Prompt (Start > Run > CMD {ENTER})
B. To change to the Yosemite Backup Directory type the following at a
Command Prompt:
1) CD\ {ENTER}
2) CD “Program Files” {ENTER}
3) CD Yosemite {ENTER}
4) CD “Yosemite Backup” {ENTER}
C. Type the following at the Command Prompt:
ytwinsvc -s {ENTER}
D. This will start the Yosemite Backup Service on the local machine.
11. Login to the Yosemite Backup Administrator.
I needed to restore an exchange 2003 database the other day and getting info from the yosemite website or stickleback or whatever they are called nowadays is like pulling teeth, i eventually found this on their site so i made a note of it then i never have to go back there again.
Yosemite KB TID: 001614
| Applicable OS |
Windows, (Linux, NetWare) – wtf since when did wither of these support exchange |
| Applicable Products |
Yosemite Backup 8.0, Yosemite Backup 8.1, Yosemite Backup 8.5 |
| Issue Type |
Restore |
| Last Updated |
3/26/2007 |
WARNING:
When attempting to restore data from a previous backup, never place media into
the device unless that media is write protected. Inserting media into a device
without the write protection turned on, could result is loss of all data on that
media.
NOTE:
The Exchange connector in Yosemite Backup does NOT allow you to restore
individual mailboxes or individual databases with a single Storage Group.
The restoration process restores the entire Storage Group.
The following steps will assist you in restoring your Exchange database to a
consistent state.
1. Open Exchange System Manager.
2. Navigate to the Storage Group you would like to restore. By default the
first Storage Group installed with Exchange is named, “First Storage Group”.
3. Expand the Storage Group to expose the Private and/or Public Stores.
4. Make the following changes to the properties of each store:
A. Right click each store and select Properties:
1) In the Properties of each Store, select the Database tab.
2) Select ‘This database can be overwritten by a restore’.
3) Select OK.
B. Right-click on all stores and click Dismount.
5. Close Exchange System Manager.
NOTE:
If a Storage Group is highlighted in the Exchange System Manager, Yosemite
Backup will NOT be able to restore that item, as it is locked by the
System Manager.
6. Navigate to the location where the transaction logs and database files are
located (C:\Program Files\Exchsrvr\Mdbdata, by default). Based on
Exchange Best Practices, these could be in different locations.
7. Delete all files associated with the Storage Group. These files are the
*.edb, *.stm, *.chk and *.log. If you are not sure which files to delete
we recommend that you create a Backup folder and MOVE the files into that
folder.
8. Open Yosemite Backup.
9. Create the Restore Job:
A. Select the Favorites desk bar (in the left column).
B. Select “Jobs and Media” in the Favorites desk bar.
C. Double click the Admin item in the right pane.
D. Right click in the blank space in the right pane.
E. Select “New” from the context menu.
F. Name the Job, and highlight “Restore Job” in the “Available types” box.
This will open the “Properties of (job name) window.
G. In the “Pages” desk bar (in the right column) click “Selection.”
1) Expand the Network item in the Right pane (click the “+” to the left
of the Network item).
2) Locate the Storage Group you want to restore under the Exchange
connector.
3) Place a check in the box next to the Storage Group you want to
restore.
4) On the menu bar (located at top), select “Versions”.
5) Select the Version you want to restore.
6) Select the “OK” button to the right of the this window.
H. In the “Pages” desk bar (in the right column) click “Device/Media.”
1) Select the device you want to use for the restore:
a. Highlight what is in the “Devices to be used” box and select the
“Delete” button at the bottom of this box.
b. Select the “Add” button at the bottom of this box.
c. Double click the Network item in the resulting window.
d. Double click the Devices item.
e. Highlight the device you want to use for the restore, and select
the “OK” button at the bottom of this window.
f. Verify that under “Types of devices to use” that a check is
placed in the type of device you are restoring from.
I. Select the “OK” button on the Restore Job.
10. Right-click on the Restore Job.
11. Select Run.
A couple of our SBS servers were very slow to shutdown this was taken from the MS website KB827610 it is todo with the WaitToKillServiceTimeout registry entry not being set to two minutes. To do this, follow these steps.
- Start Registry Editor. To do this, click Start, click Run, type regedit in the Open box, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
- In the right pane, double-click the WaitToKillServiceTimeout value.
- In the Value data box, type 120000, and then click OK.
- Quit Registry Editor, and then restart Windows Small Business Server 2003.
Here’s a useful tip i was wondering what version of sql was installed on a server if it was the standard or express edition, open the management studio and click new query type
select @@version
and execute it it should bring up a dialog box with what version you are running.
I came across a strange problem in Excel 2007 today it wouldn’t be the first i might add, where it wouldn’t print graphs properly it wouldn’t print one of the lines on the graph out of two, at first i thought it might be a problem fixed in a service pack so i downloaded all 200 odd mb of sp2 but that didn’t work, so thought it might be printer drivers but it wasn’t.
What it turned out to be was a tick box that says smoothed lines, i right clicked on the problem line, clicked format data series, click line style and untick smoothed line it then printed ok.
I can across offline files trying to sync data from several old locations on a laptop but there is no obvious way to remove the locations from the sync manager i can across this solution on the interweb.
Click start run mobsync
uncheck all locations in sync manager, then click the setup tab and uncheck all the locations under Logon/Logoff
Once this is done open a command prompt and type
reg add “hklm\SOFTWARE\Microsoft\Windows\CurrentVersion\netcache” /v FormatDatabase /t reg_dword /d 00000001
reg delete “hkcu\Software\Microsoft\Windows\CurrentVersion\netcache\shares” /f
reg add “hkcu\Software\Microsoft\Windows\CurrentVersion\NetCache\Shares” /ve
reg delete “hkcu\Software\Microsoft\Windows\CurrentVersion\netcache\AssignedOfflineFolders” /f
reg add “hkcu\Software\Microsoft\Windows\CurrentVersion\NetCache\AssignedOfflineFolders” /ve
Reboot your computer and offline files will start to rebuild, restart again for the redirected folders to rebuild.
To stop the error messages appearing when offline files try to sync pst and mdb as well as various others, you can add some exclusions using group policy goto Computer Configuration – Administrative Templates – Network – Offline Files and the is a setting called Files Not Cached, where you can add the file extensions you wish to exclude.
|
|
