Bhai log yeh form filling me Details of Computer knowledge me kya fill karna hai..? I have bachelors only in computers but the options available in the form are only computer Operations and Computers language so what to fill there..?
Can anyone please tell me what is the syllabus for technical officer in electrical cadre for professional knowledge.Do we need to read basics of electrical or every thing of whole of engineering.Please reply guys...Need ur help
@kshinu16 go to the following link http://ibpsportal.blogspot.in/2013/01/ibps-so-professional-knowledge-syllabus.html. It says No Fixed Syllabus. You will also find some books from whereyou can prepare for the exam. ATB
@junefever said:@singh_mamtaa yes, you are eligible for Technical Officer(Scale I) exam.
I have completed B.Tech in EEE.Can someone suggest for which post i should apply?
puys, I have few queries ..
1.Does one need to have 60 % in aggregate to be eligible for IT officer scale I
2.What is the syllabus for professional knowledge?how to prepare for that,please tell some books available for the same...
3.What is the salary for scale I officer..(actual)?
4.If one clears interview and all...when will be called for joining?
frnds dont waste time on salary, scale.......... just prep well and come with flying colours....... :-)
hi..can anyone provide me ibps helpline
@Ani1308
Helpline Number: 022-29687111 (Available from 09:30 AM to 06:00 PM - Excluding Saturday and Sunday)
@anjali_sng said:@Ani1308Helpline Number: 022-29687111 (Available from 09:30 AM to 06:00 PM - Excluding Saturday and Sunday)
they r not picking ..hey tumhare saath jo form bharne mein problem huwe the..after that tumne form kaise bhara tha...
@Ani1308 said:they r not picking ..hey tumhare saath jo form bharne mein problem huwe the..after that tumne form kaise bhara tha...
aaj i went again to the bank n fee submit ho gyi!!!
ok..mine is also something like that..planning to fill the form again..havent paid fee yet..but form submit ho gya hain...k thanks..
@Ani1308 said:ok..mine is also something like that..planning to fill the form again..havent paid fee yet..but form submit ho gya hain...k thanks..
fees submit nai ho ri kya
@prateek987 Bhai log yeh form filling me Details of Computer knowledge me kya fill karna hai..? I have bachelors only in computers but the options available in the form are only computer Operations and Computers language so what to fill there..?
Doston....
Here is some Computer Network summary.....
Different sizes of networks
• Personal Area Network – smallest
• System Area Network (SAN)
• Local Area Network (LAN)
• Metropolitan Area Network (MAN)
• Wide Area Network (WAN) – largest
Protocols
Protocols define interactions, such as the way the programmer uses the network. They have many elements, such as links, switches, end-hosts, processes, and exist within a single layer of the network. A protocol is only used for one service. It defines a service. You get stacks and layers of protocols in order to complete a full operation, these are known as network layers.
Network Layers
OSI 7 Layer Model (A Theoretical Model)
The OSI 7 Layer model is a theoretical model, and isn't necessarily how the network is laid out. This model was developed to be follows theoretically and consists of seven key layers, as follows.
▪ Application – high level applications.
▪ Presentation
▪ Session
▪ Transport – getting data to the correct applications.
▪ Network – getting data between a source and destination computer.
▪ Data link
▪ Physical – physical cables.
Reference Model: Internet
This reference model tends to be how the internet was developed and is a more realistic interpretation of the layout of the network hierarchy.
▪ Application Layer – high level applications.
▪ Transport Layer – e.g. TCP and UDP protocols exist here.
▪ Network Layer – IP – joins different physical networks together.
▪ Access Link Layer – physical network layer., comprising of cables etc.
• Personal Area Network – smallest
• System Area Network (SAN)
• Local Area Network (LAN)
• Metropolitan Area Network (MAN)
• Wide Area Network (WAN) – largest
Protocols
Protocols define interactions, such as the way the programmer uses the network. They have many elements, such as links, switches, end-hosts, processes, and exist within a single layer of the network. A protocol is only used for one service. It defines a service. You get stacks and layers of protocols in order to complete a full operation, these are known as network layers.
Network Layers
OSI 7 Layer Model (A Theoretical Model)
The OSI 7 Layer model is a theoretical model, and isn't necessarily how the network is laid out. This model was developed to be follows theoretically and consists of seven key layers, as follows.
▪ Application – high level applications.
▪ Presentation
▪ Session
▪ Transport – getting data to the correct applications.
▪ Network – getting data between a source and destination computer.
▪ Data link
▪ Physical – physical cables.
Reference Model: Internet
This reference model tends to be how the internet was developed and is a more realistic interpretation of the layout of the network hierarchy.
▪ Application Layer – high level applications.
▪ Transport Layer – e.g. TCP and UDP protocols exist here.
▪ Network Layer – IP – joins different physical networks together.
▪ Access Link Layer – physical network layer., comprising of cables etc.
THIS COVERS E-MAIL.....
Tum log bhi kya yaad rakhoge......
Electronic Mail
Mail servers:
• Dedicated mail servers are used to hold all the user's messages.
• There's an outgoing queue of messages.
• Mail must be sent to the correct server, which must then go into the correct mailbox on the server.
• The server is often acting like a client in sorting these things out.
User agents:
• Accesses the correct mailbox on the correct server.
There are a large number of sending protocols:
• SMTP (Simple Mail Transfer Protocol)
⁃ Three phases of transfer:
1. Handshaking
2. Transfer of messages
3. Closure.
⁃ All messages must be 7-bit ASCII text.
It's about allowing your message to move backwards and forwards through the system. (It's like the envelope).
The end of the message is signalled by a single full-stop on its own line (because a blank line may be in the email message).
Basic email format:
• Header lines (to, from, subject etc.)
• These are followed by a blank line and body (the main message of the email and attachments via MIME).
MIME (Multipurpose Internet Mail Extensions):
• Allow non-ASCII character sets and file attachments to be sent via the e-mail ASCII-encoded systems.
• Additional header lines are defined in order to tell the client to interpret the data in the message in a different way.
• Content types – discrete types (e.g. image/gif, text/plain), application discrete types (the subtype is application, followed by the type e.g. “application/word” it means that this application is responsible for interpreting this section), multipart type means that the body can contain multiple types.
MIME Encodings:
Only 7-bit ASCII values can be transmitted, so a message that is a straight text message doesn't need any translation. However, non-ASCII characters have to be translated into ASCII values and then translated back at the other end.
Base64 is the main encoder. As previously mentioned, this encoding takes groups of 3 bytes and translates them into 4 ASCII characters.
Server access protocols for e-mail:
• POP
⁃ The user agent communicates with the server and downloads all the messages.
⁃ So you can really only use one client, as the emails are being downloaded to this single client.
• IMAP (Internet Mail Access Protocol)
⁃ More features but more complex.
⁃ The client manages the emails on the server, as opposed to getting a copy.
⁃ The messages stay on the server, so whatever client you use you always get the same state of your messages.
• HTTP (e.g. Gmail, Hotmail etc.)
⁃ Probably still uses POP and IMAP underneath.
Web Address Name Lookup
Humans can easily remember names e.g. ebay. When you use a name, the numerical address is looked up.
Characterised as middleware, as name lookup is part of an application protocol. It's a service for users so they can just use names.
Domain Name System (DNS) provides the mapping.
Resolution is the procedure that performs the mapping. The name server is an implementation of the resolution.
DNS
• Hierarchical namespace for internet objects (e.g. .co.uk, .com, .ac.uk are different hierarchies).
• Names have to be unique. But not worldwide unique, just within the hierarchy.
• Decentralising because there's a lot of name mappings out there, so the looking up of these names has to be optimised.
• It's a “decentralised database” (but not a real database).
• There's global coordination of the names.
• A top organisation manages the top-level names, for example .com names. The organisation delegates down to other organisations lower-level hierarchical names such as .co.uk. Further delegations are made, such as .ac.uk.
• Worldwide coordination.
• Looking up the address for a name is done by first querying the root name server.
• There is an implicit dot ('.') that's never written at the end of a web address. This is the root server. The principle is that the name server for the next level down is then looked up at the current name server, so the root server can be queried for a '.com' server, which can then be queried for 'google.com'.
• The implication is that the traffic levels for the root servers will be huge – so the root servers are distributed across the world to spread out the load. The root server that's closest is the one that's looked up.
• There are around thirteen major root servers across the planet, with the majority in the USA.
• ISPs, companies and universities have local servers.
• Host queries are sent via a local DNS server that can act as a proxy forwarding the query into the hierarchy.
• All name servers can cache mapping they discover, which speeds up the response to queries and minimises the remote load on the servers.
• DNS: Iterative Resolution for name lookup
⁃ A host sends the name of the server it's after to a local DNS server, which then asks all the other servers for the name before sending the name of the server that has the name back to the original host. Lots of network traffic.
• DNS: Recursive Resolution for name lookup
⁃ A host sends the name of the server it's after to a local DNS server, which then asks the next server if it doesn't know, which then asks the next server if it doesn't know and so on, until the server that knows which computer has that address responds, to the previous server, which responds to the previous server, and so on until the information is passed back to the original host.
• DNS Zone
⁃ A zone is a collection of resource records.
⁃ A record has the format,.
⁃ Type specifies how to interpret the file (A = address, NS = authoritative name server for zone, CNAME = true name of alias, MX = mail exchange/relay for zone, PTR = used to map addresses to names).
⁃ Class defines purpose, which is an extension mechanism because at the moment it's only ever set to IN (internet).
⁃ TTL is the time-to-live.
Mail servers:
• Dedicated mail servers are used to hold all the user's messages.
• There's an outgoing queue of messages.
• Mail must be sent to the correct server, which must then go into the correct mailbox on the server.
• The server is often acting like a client in sorting these things out.
User agents:
• Accesses the correct mailbox on the correct server.
There are a large number of sending protocols:
• SMTP (Simple Mail Transfer Protocol)
⁃ Three phases of transfer:
1. Handshaking
2. Transfer of messages
3. Closure.
⁃ All messages must be 7-bit ASCII text.
It's about allowing your message to move backwards and forwards through the system. (It's like the envelope).
The end of the message is signalled by a single full-stop on its own line (because a blank line may be in the email message).
Basic email format:
• Header lines (to, from, subject etc.)
• These are followed by a blank line and body (the main message of the email and attachments via MIME).
MIME (Multipurpose Internet Mail Extensions):
• Allow non-ASCII character sets and file attachments to be sent via the e-mail ASCII-encoded systems.
• Additional header lines are defined in order to tell the client to interpret the data in the message in a different way.
• Content types – discrete types (e.g. image/gif, text/plain), application discrete types (the subtype is application, followed by the type e.g. “application/word” it means that this application is responsible for interpreting this section), multipart type means that the body can contain multiple types.
MIME Encodings:
Only 7-bit ASCII values can be transmitted, so a message that is a straight text message doesn't need any translation. However, non-ASCII characters have to be translated into ASCII values and then translated back at the other end.
Base64 is the main encoder. As previously mentioned, this encoding takes groups of 3 bytes and translates them into 4 ASCII characters.
Server access protocols for e-mail:
• POP
⁃ The user agent communicates with the server and downloads all the messages.
⁃ So you can really only use one client, as the emails are being downloaded to this single client.
• IMAP (Internet Mail Access Protocol)
⁃ More features but more complex.
⁃ The client manages the emails on the server, as opposed to getting a copy.
⁃ The messages stay on the server, so whatever client you use you always get the same state of your messages.
• HTTP (e.g. Gmail, Hotmail etc.)
⁃ Probably still uses POP and IMAP underneath.
Web Address Name Lookup
Humans can easily remember names e.g. ebay. When you use a name, the numerical address is looked up.
Characterised as middleware, as name lookup is part of an application protocol. It's a service for users so they can just use names.
Domain Name System (DNS) provides the mapping.
Resolution is the procedure that performs the mapping. The name server is an implementation of the resolution.
DNS
• Hierarchical namespace for internet objects (e.g. .co.uk, .com, .ac.uk are different hierarchies).
• Names have to be unique. But not worldwide unique, just within the hierarchy.
• Decentralising because there's a lot of name mappings out there, so the looking up of these names has to be optimised.
• It's a “decentralised database” (but not a real database).
• There's global coordination of the names.
• A top organisation manages the top-level names, for example .com names. The organisation delegates down to other organisations lower-level hierarchical names such as .co.uk. Further delegations are made, such as .ac.uk.
• Worldwide coordination.
• Looking up the address for a name is done by first querying the root name server.
• There is an implicit dot ('.') that's never written at the end of a web address. This is the root server. The principle is that the name server for the next level down is then looked up at the current name server, so the root server can be queried for a '.com' server, which can then be queried for 'google.com'.
• The implication is that the traffic levels for the root servers will be huge – so the root servers are distributed across the world to spread out the load. The root server that's closest is the one that's looked up.
• There are around thirteen major root servers across the planet, with the majority in the USA.
• ISPs, companies and universities have local servers.
• Host queries are sent via a local DNS server that can act as a proxy forwarding the query into the hierarchy.
• All name servers can cache mapping they discover, which speeds up the response to queries and minimises the remote load on the servers.
• DNS: Iterative Resolution for name lookup
⁃ A host sends the name of the server it's after to a local DNS server, which then asks all the other servers for the name before sending the name of the server that has the name back to the original host. Lots of network traffic.
• DNS: Recursive Resolution for name lookup
⁃ A host sends the name of the server it's after to a local DNS server, which then asks the next server if it doesn't know, which then asks the next server if it doesn't know and so on, until the server that knows which computer has that address responds, to the previous server, which responds to the previous server, and so on until the information is passed back to the original host.
• DNS Zone
⁃ A zone is a collection of resource records.
⁃ A record has the format,
⁃ Type specifies how to interpret the file (A = address, NS = authoritative name server for zone, CNAME = true name of alias, MX = mail exchange/relay for zone, PTR = used to map addresses to names).
⁃ Class defines purpose, which is an extension mechanism because at the moment it's only ever set to IN (internet).
⁃ TTL is the time-to-live.
The Most awaited PO based Exam of the year has arrived..Gals n Guys..Do check.. 
With a Grand 1500 post offered.. SBI Rocks...
With a Grand 1500 post offered.. SBI Rocks...
guys need help.......i am b.tech in automobile eng....... am i eligible for cwe specialist xam dat?
hey hello guys n girls..dys is Manisha...i guess m too late to this forum.
well i am giving ibps cwe spl 2 exam(it officer scale 1) ..its my first attempt.
n i need your help..pls suggest me some good books and materials which will help me in preparing for dys exam..
i did my offline payment ...now what should i do? can anyone help please.