Google IT Solutions

Thursday 4 September 2014

Cloud Domain Controller for Branch office

Plan for Cloud Domain Controller.

Setup Remote Domain Controller via Direct access
Following Ports need to be opened in Firewall or Router on both side.
  • NAT Local IP of Domain Controller to Public IP or Internet IP
  • A domain name will be register on godaddy.com or register.com or etc
  • Additional Domain Controller will be setup in branch office and both Server will replicate to each other
  • UDP Port 88 for Kerberos authentication
  • TCP Port 135 for domain controllers-to-domain controller and client to domain controller operations.
  • TCP Port 139 and UDP 138 for File Replication Service between domain controllers.
  • UDP Port 389 for LDAP to handle normal queries from client computers to the domain controllers.
  • TCP Port 445 for File Replication Service
  • TCP Port 464 for Kerberos Password Change
  • TCP Port 3268 and 3269 for Global Catalog from client to domain controller.
  • TCP Port 53 for DNS from client to domain controller and domain controller to domain controller.
Opening above ports in Firewall between client computers and domain controllers, or between domain controllers, will enable Active Directory to function properly.

Setup Remote Domain Controller via VPN.

A best solution to secure your domain traffic is Site-to-Site VPN.

  • On both side site-to-site vpn will create
  • No need to purchase or register a domain name from godaddy or register.com etc.
  • If a firewall installed in Cloud then need to allow ports in firewall to communicate Domain Server and Client machines.
  • UDP Port 88 for Kerberos authentication
  • TCP Port 135 for domain controllers-to-domain controller and client to domain controller operations.
  • TCP Port 139 and UDP 138 for File Replication Service between domain controllers.
  • UDP Port 389 for LDAP to handle normal queries from client computers to the domain controllers.
  • TCP Port 445 for File Replication Service
  • TCP Port 464 for Kerberos Password Change
  • TCP Port 3268 and 3269 for Global Catalog from client to domain controller.
  • TCP Port 53 for DNS from client to domain controller and domain controller to domain controller.

Friday 11 July 2014

How to create CMAN listener


Installation & Configuration of Connection Manager (CMAN) Oracle 10g

Just follow below steps and make your life easier.

Click start menu ===> Oracle-OraDb10g_home1 ===> click on Universal Installer


 1. Run universal installer from installed oracle_home.


2. Click on Button “Next”.
 

3. Specify Setup files location and Click on Button “Next”.
 


4. Select option “Custom” and Click on Button “Next”.



5. Select installed DB oracle home and Click on Button “Next”.
 

6. Check both these boxes to be user verified and Click on Button “Next”.


7. Check “Oracle Connection Manager” and Uncheck “Oracle Services for Microsoft Transaction Server”. Click on Button “Next”.
 

8. Click on Button “Install”.
 




9. Click on Button “Exit”.
 

10. Copy this CMAN.ORA file from path “D:\oracle\product\10.2.0\db_1\NETWORK\ADMIN\SAMPLE” This file will auto creates just after CMAN installation. Make changes that are in red color and give following values.
cman <alias>
local IP of Database<192.168.1.54>
listener port <1620>



11.Open CMD and type follwing commands,
  • cmctl
  • administrator cman
  • startup


12. Change “Startup Type” of these services to Automatic. 

 


Friday 27 June 2014

How to delete Listener with Oracle

If you want to delete listener then just follow below steps and complete your task  very easily.

1. Window+R and "netca" and press enter. A configuration window will apear,
oracle

2. Select "Listener Configuration" and click next
3. Select delete and click next.
oracle

4. Click Next
oracle
5. A warning message will appear at your screen,
oracle
6. Click on "YES"
7. It will start deletion and new screen will appear "LISTENER WAS DELETED" and then click next
oracle
8. Click next and new window will apear with that message "Listener configuration complete" now click next.
oracle
9. Click on Finish button,
oracle
Cheer's

Wednesday 25 June 2014

BI Unable to connect to port 9705 on machine error [nQSError: 12008]


How to resolve [nQSError: 12008] Unable to connect to port 9705 on machine with OBIEE

Whenever facing following error;

Oracle BI Scheduler Error: [nQSError: 12008] Unable to connect to port 9705 on machine test-pc. [nQSError: 12010] Communication error connecting to remote end.

Point:  address = test-pc; port = 9705. [nQSError: 12002] Socket communication error at call=: (Number=-1)


Go to services and make sure the Oracle BI Scheduler Service is up and running.

Wednesday 18 June 2014

localhost does not work

Question: localhost does not work but website can be viewed both internally and externally.

Answer:

If you bind website with localhost then it will browse.

If you bind website with another static IP then website will browse with its static IP but not with localhost.

If you want to browse website via localhost then follow below steps;
  • Open IIS
  • Right click on website
  • Then click on Edit Bindings
  • Assign localhost or IP: 127.0.0.1
  • Click ok and close window
  • Now browse your website.

IIS



How to Create /Drop /DB link in oracle

Two way to create DB link in oracle Database
1. With TNS entry in tnsnames.ora
2. TNS entry given at the time of db link creation.

Create DB link

1st method: Create DBLINK with TNS entry name made in tnsnames.ora
Put a TNS in tnsnames.ora file with name like “TEST”

CREATE PUBLIC DATABASE LINK 'TEST'
 CONNECT TO 'USER Name'
 IDENTIFIED BY 'Password'
 USING 'TEST'

TNS entry like;
TEST=
  (DESCRIPTION=
    (ADDRESS=
      (PROTOCOL=TCP)
      (HOST=hostname)
      (PORT=1521)
    )
    (CONNECT_DATA=
      (SERVER=dedicated)
      (SERVICE_NAME=test)
    )
  )

2nd method with full TNS

CREATE PUBLIC DATABASE LINK “TEST”
 CONNECT TO “USER Name”
 IDENTIFIED BY “Password”
 USING TEST=
  (DESCRIPTION=
    (ADDRESS=
      (PROTOCOL=TCP)
      (HOST=hostname)
      (PORT=1521)
    )
    (CONNECT_DATA=
      (SERVER=dedicated)
      (SERVICE_NAME=test)
    )
  )


DROP DBLINK:

DROP PUBLIC DATABASE LINK ‘TEST’


Monday 16 June 2014

What is DNS

Domain Name Service (D.N.S)

The DNS (Domain Name Service) is a standard technology for managing the names of Websites and other Internet domains. DNS technology allows you to type names into your Web browser like (solutions-ever.blogspot.com) and your computer to automatically resolve that address on the Internet. A key element of the DNS is a worldwide collection of DNS servers.

DNS server is any computer registered to join the Domain Name System. A DNS server runs special purpose networking features public IP addresses and contains a database of network names and addresses for other Internet hosts.

DNS Root Server

DNS servers communicate with each other using private network protocols. All DNS servers are organized in a hierarchy. At the top level of the hierarchy, so-called root servers store the complete database of Internet domain names and their corresponding IP addresses.

DNS Hierarchy

The DNS is a distributed system, meaning that only the 13 root servers contain the complete database of domain names and IP addresses. All other DNS servers are installed at lower levels of the hierarchy and maintain only certain pieces of the overall database.
Lower level DNS servers are owned by businesses or ISP’s. For example, yahoo maintains various DNS servers around the world that manage the yahoo.com, and other domains. Your ISP also maintains DNS servers as part of your Internet connection setup.
DNS networking is based on the Client/Server architecture. Your Web browser functions as a DNS client and issues requests to your Internet provider's DNS servers when navigating between Web sites.
When a DNS server receives a request not in its database, it temporarily transforms from a server to a DNS client. The server automatically passes that request to another DNS server or up to the next higher level in the DNS hierarchy as needed. Eventually the request arrives at a server that has the matching name and IP address in its database and the response flows back through the chain of DNS servers to your client.