Jaydien Network Solutions Blog

We're up when your technology is down.

If you do not use the SBS provided ways to add new users they will not show in the SBS Console > Users and Groups > Users tab, because the user’s Active Directory (AD) attribute msSBSCreationState value is not “stamped” to Created.

To view the Active Director attribute, make sure that the advanced options are enabled by clicking View/Advanced Features in AD Users and Computers. This will add the addtional tabs when you view an object.

Go to the effected user, click on Attribute Editor, scroll down to msSBSCreationState and double click. Change the value to Created. Ok out of everything and you should now see your user in the SBS Console.

Here is a quick review of the two SBS provided ways adding user accounts from the SBS Console:

 

To perform a hard reset on the BlackBerry PlayBook:

Hold down the volume up key, volume down key, and power button at the same time and hold it for about 15 seconds.

TIP: Its easier if you hit the volume up key then the volume down key and then the power key.

 

Outlook prevents the automatic download of pictures in email messages as a security measure to help prevent possible spamming. It permits images from sites in your Trusted Zone to show but blocks all others. You can override this feature by following this tech recipe:

 

1. Open Outlook 2010.

2. Go to the Ribbon and select File.

3. Click Options.

 

comes with a unique feature called AirPrint which allows you to print your documents, photos, emails and web-pages over a Wifi connection with your Apple iOS device. To enable iOS 4.2 AirPrint feature on Windows, follow the step-by-step guide below. This guide is applicable to Windows 7, Windows Vista and Windows XP users.

Prerequisites:

  • iTunes 10.1
  • Make sure the printer is setup as a shared printer on your local PC
  • Make sure you have full administrator privileges to enable/disable services on your PC

Steps to Enable AirPrint on Windows 7/Vista/XP:

  1. If you have 64-bit Windows OS, go to C:Program Files (x86) and create a new folder called AirPrint as shown in the screenshot below:
     

Make a Dreamweaver shortcut to add ColdFusion comment tags

Don’t hold it against me, but I like to use Dreamweaver to code ColdFusion. However, like most people I have some gripes. For instance, I really want a shortcut to comment out ColdFusion code. There’s just two problems with this…

  • By default Dreamweaver doesn’t have a shortcut key to insert comments.
  • Dreamweaver inserts HTML comments (<!– –>), not ColdFusion comments (<!— —>).

Here’s how to fix both problems:By default Dreamweaver doesn’t have a shortcut key to insert comments.You can easily edit short cut keys in Dreamweaver. Simply click Edit > Keyboard Shortcuts… This will open the Keyboard shortcuts window. With Menu Commands selected in the Commands dropdown expand the Insert and then Text Objects tree items. Select Comment at the bottom of the list. Select the Press Key textbox and hit whatever shortcut keys you want. I use CTRL-ALT-C.Now, whenever you want to add a comment simply hit your chosen shortcut and Dreamweaver will wrap your selection in comment tags!And that leads us to the second problem… Dreamweaver inserts HTML comments (<!– –>), not ColdFusion comments (<!— —>).After much digging around and guessing in the Dreamweaver configuration directory I found a file which can be used to change the default comment formatting. The file can be found under [yourDreamweaverInstallDirectory]ConfigurationObjectsTextComment.js.Shutdown Dreamweaver and open the Comments.js file. Find the line which reads:dom.source.wrapSelection('<!-- ',' -->');Change this line to read:dom.source.wrapSelection('<!--- ',' --->');Now, when you restart Dreamweaver your shortcut key will wrap you current selection in wonderful ColdFusion comments. One less Dreamweaver headache!

 

If you have ever tried to setup remote access or perform remote testing on a network with a cellular internet connection, you are probablly aware of the difficulties associated with the defualt dialer configuration.

The problem is that after a short time-out period, the 3G interface goes into a spoofing mode where it show as UP/UP but the connection to the cell phone tower is shut down to save on your bandwitdth or minutes usage.

The alternative to this, assuming that you have an unlimited data plan, is to configure the 'Dialer Persitent' setting.


Configuring Dialer Persistent

To configure a dialer interface as persistent, use the following commands beginning in global configuration mode:

 


Command
Purpose

Step 1

Router(config)# interface dialer number

Creates a dialer interface and enters interface configuration mode.

Step 2

Router(config-if)# ip address address mask

Specifies the IP address and mask of the dialer interface as a node in the destination network to be called.

Step 3

Router(config-if)# encapsulation type

Specifies the encapsulation type.

Step 4

Router(config-if)# dialer string dial-string class class-name

Specifies the remote destination to call and the map class that defines characteristics for calls to this destination.

Step 5

Router(config-if)# dialer pool number

Specifies the dialing pool to use for calls to this destination.

Step 6

Router(config-if)# dialer-group group-number

Assigns the dialer interface to a dialer group.

Step 7

Router(config-if)# dialer-list dialer-group protocol protocol-name {permit | deny | list access-list-number}

Specifies an access list by list number or by protocol and list number to define the interesting packets that can trigger a call.

Step 8

Router(config-if)# dialer remote-name user-name

(Optional) Specifies the authentication name of the remote router on the destination subnetwork for a dialer interface.

Step 9

Router(config-if)# dialer persistent [delay [initial] seconds | max-attempts number]

Forces a dialer interface to be connected at all times, even in the absence of interesting traffic.

 

See the configuration example in the section "Configuration Examples" and the "Examples" section in the dialer persistent command reference page for additional commands that might be entered for this configuration.

Shutting Down an Interface Configured for Dialer Persistence

To fully tear down (shut down) a dialer interface configured for dialer persistent, use the following commands beginning in global configuration mode:

 


Command
Purpose

Step 1

Router(config)# interface dialer number

Enters interface configuration mode on the specified dialer interface.

Step 2

Router(config-if)# shutdown

Fully tears down a persistent connection and prevents the software from attempting more dialing.

 

Verifying Dialer Persistent

To verify that dialer persistent is configured correctly, perform the following verification steps:


Step 1 Enter the show dialer interface EXEC command with the interface type and number to display statistics on the physical interface bound to the dialer interface. Output includes the configured timers. The "Idle timer (never)" and "Dial reason:" lines indicate that persistent dialing is configured.

Router# show dialer interface dialer 1

 Di1 - dialer type = DIALER PROFILE

 Idle timer (never), Fast idle timer (20 secs)

 Wait for carrier (30 secs), Re-enable (15 secs)

 Dialer state is data link layer up

 Number of active calls = 1

 Dial String      Successes   Failures    Last DNIS   Last status

 7135551234 4          0    00:00:06       successful   Default

 BRI1/0 - dialer type = ISDN

 Dial String      Successes   Failures    Last DNIS   Last status

 0 incoming call(s) have been screened.

 0 incoming call(s) rejected for callback.

 BRI1/0:2 - dialer type = ISDN

 Idle timer (never), Fast idle timer (20 secs)

 Wait for carrier (30 secs), Re-enable (15 secs)

 Dialer state is data link layer up

 Dial reason: Dialing on persistent Dialer Profile

 Interface bound to profile Di1

 Time until disconnect never

 Current call connected 00:00:06

 Connected to 7135550134 (7135550134)

Step 2 Enter the debug dialer EXEC command and verify that the following message appears:

Di1 DDR: Persistent Dialer Profile nailed up successfully

 

 

I recieved a very similar problem on two machines, one was a Windows 2003 SBS Server and another was WinXP SP3, within a 2 hour period of each other so I though it warranted discussing the solution.

For the server issue, I was recieving error code 150 when trying to start the ICS service. I disovered this error because the server could not browser the internet, download AVG virus updates or downoad POP mail. Basically anything internet related. Clients we OK as far as internet and local file/print sharing.

For the XP issue, I just could not browse the internet. I think it is noteworthy to mention that malware was discovered on the XP machine (Trojan.FakeAlert) as well. After removing the maware, lack of internet still existed.

The resolution on both was to reset the Winsoxk TCP/IP stack. The command on both computers is the same.

From a command prompt:
netsh winsiock restart
*A reboot is required.

Other usefull Winsock repair / maintenance commands:
To backup a configuration :
netsh -c interface dump > c:configsofficeinterface.txt

To restore a configuration :
netsh -f c:configsofficeinterface.txt

Repair/reinit the TCP/IP protocol if it has gone bad (Useful as WinXP cannot uninstall the TCPIP stack netsh int ip reset
More info MS KB Q299357

 

By default, if you try to modify your hosts file in Vista, it will not let you save it.  It tells you that you don't have permission.  To successfully modify the hosts file, run notepad.exe as an administrator and open the file.

1)  Browse to Start -> All Programs -> Accessories
2)  Right click "Notepad" and select "Run as administrator"
3)  Click "Continue" on the UAC prompt
4)  Click File -> Open
5)  Browse to "C:WindowsSystem32Driversetc"
6)  Change the file filter drop down box from "Text Documents (*.txt)" to "All Files (*.*)"
7)  Select "hosts" and click "Open"
8)  Make the needed changes and close Notepad.  Save when prompted.

Technorati tags: Vista, Hosts file, UAC
 

Follow these steps to revert from lightweight mode to autonomous mode by loading a Cisco IOS release using a TFTP server:

  1. The PC on which your TFTP server software runs must be configured with a static IP address in the range of 10.0.0.2 to 10.0.0.30.
  2. Make sure that the PC contains the access point image file (such as c1200-k9w7-tar.122-15.JA.tar for a 1200 series access point in the TFTP server folder and that the TFTP server is activated.
  3. Rename the access point image file in the TFTP server folder to the default image name - it will c1200-k9w7-tar.default for an 1200 series AP c1130-k9w7-tar.default for an 1130 series AP
  4. Connect the PC to the access point using a Category 5 (CAT5) Ethernet cable.
  5. Disconnect power from the access point.
  6. Press and hold the MODE button while you reconnect power to the access point.
  7. Hold the MODE button until the status LED turns red (approximately 20 to 30 seconds), and release the MODE button. For the 1130 APs, hold the button until the console indicates that the button is pressed (the R LED will be solid red): button is pressed, wait for button to be released... button pressed for 25 seconds process_config_recovery:      set IP address and config to default 10.0.0.1

    process_config_recovery: image recovery image_recovery: Download default IOS tar image tftp://255.255.255.255/c1130-k9w7-tar.default

    Once it starts uploading, the E & R LEDs will both be blinking (1130 AP). Once you release the button, you should see the console extracting files from the tarball on the TFTP server.
  8. Wait until the access point reboots as indicated by all LEDs turning green followed by the Status LED blinking green. You can also observe the console to see when it reboots - this is a better bet, as some APs behave differently than others in terms of LED operation.
  9. After the access point reboots, reconfigure the access point using the GUI or the CLI

CLI REFERENCE 

http:/www.cisco.com/en/US/partner/docs/wireless/access_point/ios/release/notes/b311jx1.html

 

The following screen shots show the proper configuration of the Linksys/Sipura SPA400 as a PSTN gateway interface for the 3CX IP PBX software.

Linksys/Sipura SPA400
Admin Guide



Basic Setup
basic_setup

 
<< Start < Prev 1 2 3 Next > End >>