How to add DHCP Scope Option 150 for Cisco CallManager

2.Sep.2012 | by Gusac | Filed in: Tutorials, Articles

By default, the DHCP Scope option 150 for Cisco TFTP Server is not available on Windows Server. Below are the steps to add the configure the option 150:   1.  First we need to define the option 150 so that it can be made available in the scope options list. For this, right click on the IPv4 and choose the option  Set Predefined Options… (screenshot below)   2.  Click on the Add… button and you will get another dialog box asking you the Option Type. 3.  Fill the details as mentioned below and shown in the screenshot: Name: Cisco TFTP Server Data Type: IP Address Array: Checked Code: 150 Description: Used for Cisco Call Manager TFTP Server .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; }   4.  Click OK and click Edit Array button to enter the IP address for the TFTP Server (Screenshot below). Once you are done, click OK to exit.   5.  Now, to configure Option 150 for any scope, go to its Scope Options, right click on and choose Configure Options and select the Option 150 from the list. You can edit the IPs if you required.

Configure Proxy settings for WinHttp on Windows server 8 or 2008 R2

6.Apr.2012 | by Gusac | Filed in: Articles

The steps mentioned in this article apply Windows server 8, Windows 8, Windows server 2008, Windows server 2008 R2 and Windows 7. In Windows 2003, there was proxycfg command line utility to configure proxy settings for WinHTTP services, however in Windows 8 / 2008 R2 it has been discontinued. Netsh.exe now does the configuration for WinHTTP proxy in this version.  Click here for a reference to proxycfg command Here are the list of available commands: ProxyName is the where you would enter your proxy server name. Advisable that you launch the command prompt as an administrator. Set WinHTTP proxy information: 1. netsh winhttp set proxy ProxyName 2. netsh winhttp set proxy ProxyName:80 3. netsh winhttp set proxy ProxyName:80 "<local>" 4. netsh winhttp set proxy proxy-server="http=Proxy1;https=Proxy2" bypass-list="*.winplat.net" .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; } Reset proxy information: Resets any proxy settings configured earlier; set to detect setting automatically. netsh winhttp reset proxy .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; } .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; } Import proxy information netsh winhttp import proxy ie .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; } Show WinHTTP proxy information netsh winhttp show proxy .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; }

Unable to access Samba shares from Windows 7 with error

4.Apr.2012 | by Gusac | Filed in: Articles, Troubleshoot

This article is to compile and suggest some of the common troubleshooting steps for the error while accessing the Samba shares on Unix or Linux based systems from Windows 7. They may or may not apply to your scenario. There could be some more steps which are not included in this post. The aim here is to help who are slogging through forums for solution like me. Issue: While connecting to Unix or Linux based samba shares from Windows 7 client network error stating: Windows cannot access \\SERVER and throws error code: 0x80070035. Whereas the Windows XP systems do not exhibit the same behavior.   Suggestions: 1. Basic IP Though this is a basic step but worth mentioning. If the error occurs with the server name, try connecting with IP address. If it works, it could be DNS issue. 2. Check Firewall 3. Services TCP/IP NetBIOS Helper service should be set to Automatic and Started. Try starting Computer Browser service, if its not. Try to stop and disable the Routing and Remote Access service, if its started 4. Network Card Binding Order A. Check the binding order. Go to network connections, go to Advanced menu then select Advanced Settings… B. Select the network connection you are using and move it to the top C. Click OK and exit. 5. Enable ‘Client for Microsoft Networks’ In network connections, go to the properties of network connection which you are using to connect to the server. Ensure that the ‘Client for Microsoft Networks’ is checked. 6. Enable NetBIOS over TCP/IP A. Open the properties of the network connection, select Internet Protocol version 4 (TCP/IPv4) and click on Properties button. B. On the new page, click on Advanced… button at the bottom. C. Click on WINS tab and under NetBIOS setting , select Enable NetBIOS over TCP/IP and click OK to exit. 7. Select Authentication level Check the below mentioned policy on Windows 7: Group policy editor: Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\ Network security: LAN Manager authentication level Ensure that it is not set to refuse LM & NTLM authentication or set to use NTLMv2 only. To be safe, you can select the following setting which enables LM, NTLM and NTLMv2 authentication: Send LM & NTLM - use NTLMv2 session security if negotiated Note: Ensure that this policy is not coming from Domain level group policy. And, if you are using Home or Home premium edition and do not have Group Policy editor then do it in registry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa Value Name: LmCompatibilityLevel  [DWORD] Set the value to: 1 Reboot your system.   8. SMB Signing Disable SMB signing and try: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManServer\Parameters Value Name: EnableSecuritySignature  [DWORD]. Set the value to 1. Value Name: RequireSecuritySignature  [DWORD]. Set the value to 0. 9. Disable SMB 2.0 Disable SMB 2.0 on Windows 7 and try again. Disable SMB 2.0 at client end: Open the command prompt (cmd.exe) and type the following two commands: sc config lanmanworkstation depend= bowser/mrxsmb10/nsi sc config mrxsmb20 start= disabled Click here for reference on this   I hope it helps!

Permalink | Tags: ,


How to Disable SMB 2.0

26.Apr.2011 | by Gusac | Filed in: Articles

Windows Vista/2008 server and later OS have version 2 of SMB (Server Message Block), which also has backward compatibility with SMB 1.0. Even though, SMB 2.0 is tested to be faster, it might cause some issues in some scenarios and you may wan to disable it. There are different ways to disable SMB 2.0 at client end and server end. Disable SMB 2.0 at server end: Open Registry Editor (regedit.exe) and navigate to the following registry key": HKLM\System\CurrentControlSet\Services\LanmanServer\Parameters Create a new DWORD value and rename it to: Smb2 Set the value data to 0. (0 denotes ‘Disable’) Restart the system Disable SMB 2.0 at client end: Open the command prompt (cmd.exe) and type the following two commands: sc config lanmanworkstation depend= bowser/mrxsmb10/nsi sc config mrxsmb20 start= disabled .csharpcode, .csharpcode pre { font-size: small; color: black; font-family: consolas, "Courier New", courier, monospace; background-color: #ffffff; /*white-space: pre;*/ } .csharpcode pre { margin: 0em; } .csharpcode .rem { color: #008000; } .csharpcode .kwrd { color: #0000ff; } .csharpcode .str { color: #006080; } .csharpcode .op { color: #0000c0; } .csharpcode .preproc { color: #cc6633; } .csharpcode .asp { background-color: #ffff00; } .csharpcode .html { color: #800000; } .csharpcode .attr { color: #ff0000; } .csharpcode .alt { background-color: #f4f4f4; width: 100%; margin: 0em; } .csharpcode .lnum { color: #606060; } Please note, there is a space after the equal to (‘=’) sign in the command.

How to remove Phantom Network adapter

20.Dec.2010 | by Gusac | Filed in: Articles, Troubleshoot

Phantom or Ghost Network adapters are created when the network adapter is removed without removing the drivers. These ghost network adapter (NICs) are hidden and are not listed in device manager. [More]

How to turn Windows 7 or Windows 2008 R2 as WiFi Access point

4.Aug.2010 | by Gusac | Filed in: Articles, Tutorials

How to make Windows 7 or Windows server 2008 R2 computer system as a WiFi access point or hotspot for other wireless devices. [More]

Managing Network Connections in Windows server 2008 Core

11.Jul.2010 | by Gusac | Filed in: Articles, Tutorials

Managing Network Connections in Windows server 2008 Core [More]

How to install Remote and Routing Service (RRAS) on Windows Server 2008

19.Sep.2009 | by Gusac | Filed in: Articles, Tutorials

How to install Remote and Routing Service (RRAS) on Windows Server 2008 [More]