1. Kabel Terbuka (open). Kondisi ini menyatakan bahwa telah terjadi putusnya kabel dalam jaringan yang menyebabkan kabel tidak dapat menghantarkan data.  
2. Konektor longgar (tidak terhubung). Kondisi ini terjadi pada pada koneksi antar kartu jaringan dengan konektor kabel. 
3. Kabel short. Kondisi ini menyatakan bahwa telah terjadi kabel yang hubung singkat dalam jaringan.
4. Resistor pada terminating Connector 
5. Short pada pemasangan kabel dengan plug konektor  
6. Longgar pada male connector

1. Konektor longgar (tidak terhubung)
2. Kabel short  
3. Kabel terbuka (open)

1. Alamat port I/O
2. Nomor Interupt 
3. Direct Memory Access Request line
4. Buffer memory Address

• Tidak bisa Login dalam jaringan, Tidak bisa masuk dalam jaringan berarti client tidak dapat mengakses jaringan secara keseluruhan. 

• Tidak bisa menemukan komputer lain pada daftar network neighborhood. Apabila secara hardware dan software tidak ada masalah komputer harus dilakukan restart untuk menyimpan semua data yang telah kita update ke sistem operasi. 

• Tidak bisa sharing files atau printer. Sharing file atau printer adalah membuka akses agar komputer lain dapat mengakses atau melihat data kita. Tidak dapat sharing file atau printer dapat dikarenakan data atau printer tersebut belum di sharing. untuk dapat melakukan sharing dapat dilakukan dengan klik kanan share.   

• Tidak bisa install network adapter. Kasus ini biasanya disebabkan oleh sorfware kartu jaringan yang tidak sesuai antara driver dengan kartu jaringannya atau pemasangan kartu jaringan yang tidak sempurna pada mainboard sehingga komputer tidak dapat mengenal kartu jaringan tersebut.  Hal yang harus dilakukan dengan pengecekan pada kartu jaringan apakah telah terpasang dengan benar atau kartu jaringan telah terinstall dengan driver bawaannya. 

• Komputer lain tidak dapat masuk ke komputer kita. Komputer lain yang tidak dapat masuk ke komputer kita padahal komputer kita dapat masuk ke komputer lain disebabkan karena kita belum melakukan sharing data atau sharing printer.

 Macam-macam Trouble shooting LAN :
1.Gejala :
Koneksi jaringan putus-putus.
Masalah
Kemungkinan Tidak berfungsinya komponen jaringan yang disebabkan oleh korosi (berkarat), aus dan rusak. Korosi terjadi dikarenakan ruang atau tempat jaringan yang lembab dan juga pemakaian yang sudah terlalu lama tanpa adanya perawatan yang berkala.
Solusi :
Mengganti komponen yang rusak dengan yang baru dan sering merawat komponen tersebut.
3. Gejala :
Lampu indikator tidak menyala pada kartu jaringan dan pada Hub/switch.
Masalah
Kemungkinan permasalahan pada kabel atau konektor tidak terpasang dengan baik (longgar) atau susunan kabel yang salah atau kabel terputus.
Solusi :
Cek kembali apakah konektor terpasang dengan baik dan pastikan tidak ada kabel yang terbalik susunannya serta tidak putus.
4. Gejala :
Muncul pesan IP conflic.
Masalah
Terjadi alamat / IP Address yang sama.
Solusi :
Melakukan setting ulang alamat IP Address dan subnetmasknya sesuai dengan jaringan yang digunakan.
5. Gejala :
Folder atau file tidak dapat diakses pada komputer lain.
Masalah
Dikarenakan folder atau file tersebut belum di sharing.
Solusi :
Cara masuk ke windows explorer pilih data atau directory yang akah disharingkan kemudian klik kanan lalu klik sharing
6. Gejala :
Icon Local Area Conection tidak tampl pada network conection di control panel.
Masalah
1.Kemungkinan Driver belum terinstall.
2.Pemasangan kartu jaringan kurang baik.
3.Kemungkinan slot pci kotor atau rusak.
4.Kartu jaringan rusak.
Solusi :
1.Cari dan install Driver yang sesuai dengan kartu jaringan.
2.Periksa pemasangan kartu jaringan.
3.Bersihkan slot pci yang kotor atau pindahkan ke slot pci yang lain.
4.Ganti kartu jaringan.
7. Gejala :
Komputer meminta user dan password pada saat diakses oleh komputer lain pada jaringan peer to peer.
Masalah
1. Pada windows xp belum ada data yang tersharing
2. Pada windows 7 atau Vista Password protected sharing belum di turn off kan
Solusi :
1. Sharing folder atau file terlebih dahulu pada windows xp.
2. Masuk keControl Panel lalu Network and Sharing Center kemudian Advanced sharing settings lalu turn off kan file protected sharing.
8. Gejala :
Tidak bisa Login dalam jaringan (Tidak terhubung dengan internet).
Masalah
Tidak bisa masuk dalam jaringan berarti client tidak dapat mengakses jaringan secara keseluruhan. (Tidak terhubung dengan internet).
Solusi :
Dibatasi oleh mikrotik, mintalah admin untuk mendaftarkan physical address komputer yang dipakai atau meminta untuk dibuatkan account.
9. Gejala :
Lampu indikator pada kartu jaringan dan pada switch/hub hidup, kabel utp yang digunakan dalam kondisi yang baik, akan tetapi tidak dapat terhubung.
Masalah
Kemungkinan terjadi kerusakan pada port kartu jaringan.
Solusi :
Mengganti Kartu jaringan (Network Interface Card) dengan yang baru.
10. Gejala :
Lampu indikator pada kartu jaringan dan pada switch/hub mati, kondisi kartu jaringan dan switch dalam keadaan yang baik.
Masalah
Kemungkinan ada masalah dengan kabel yang digunakan.
Solusi :
Ganti Konektor (RJ-45) dengan yang baru , dang anti apabila perlu. Dan juga periksa susunan warna kabelnya, juga kerapatan antara kabel dengan konektor.
11. Gejala :
Printer tidak dapat di akses pada komputer lain
Masalah
Dikarenakan printer tersebut belum di sharing
Solusi :
Caranya masuk ke control panel printers and faxes, lalu pilih printer yang akan di sharing lalu klik kanan, pilih sharing, kemudian pilih sharing this printer lalu klik ok.
12. Gejala :
Koneksi Internet lambat.
Masalah
Kemungkinan terlalu banyak pengguna/client sehingga menyebabkan koneksi internet lambat.
Solusi :
Sebaiknya kurangi pengguna/client, atau menambah bandwith.
13. Gejala :
Koneksi antara komputer dengan acces point lambat.
Masalah
Lemungkinan karena jarak yang terlalu jauh antara komputer dengan acces point.
Solusi :
Memperdekat jarak antara komputer dengan accespoint.

Masalah Jaringan Wireless

By Ki Grinsing

Pendahuluan

Sebelum kita membahas masalah jaringan wireless, terlebih dahulu kita juga harus mengerti bagaimana proses terjadinya koneksi wireless clients kepada jaringan wireless. Hal ini sangat membantu sekali dalam kita melakukan troubleshooting.
Pada artikel sebelumnya tentang cara melakukan troubleshooting jaringan, artikel ini sebenarnya merupakan kelanjutan dari artikel tersebut, akan tetapi disini akan focus pada masalah jaringan wireless. Seiring semakin banyaknya pemakai wireless network ini, wireless problems sudah menjadi sesuatu yang sering dihadapi dan dipertanyakan.

Proses koneksi wifi

Berikut adalah proses atau langkah terjadinya suatu koneksi wireless yang perlu difahami yang akan sangat membantu kita dalam menyelesaikan masalah.

1. Proses scanning wireless access point (AP)
2. Memilih wireless access points
3. Proses authentikasi terhadap wireless AP yang dipilih
4. Proses koneksi terhadap wireless AP yang dipilih
5. Mendapatkan konfigurasi TCP/IP address

1. Scanning wireless AP

Computer berbasis XP atau Vista yang mempunyai wireless adapter active yang supports Wireless Auto Configuration, akan selalu melakukan scanning adanya wireless AP pada jangkauannya setiap 60 sec. Saat scanning, wireless adapter mengirim sederetan frame Probe Request. Sementara itu wireless AP yg ada pada jangkauan wireless adapter yg sedang melakukan scanning adanya wireless AP, juga mengirim frame Probe response yang memuat capabilitas wireless AP seperti speed yang disupport serta opsi2 security lainnya.


Kita menganggap komputer mengalami masalah koneksi wifi jika tidak mendapatkan satupun wireless AP dalam jangkauan roamingnya.

2. Memilih suatu wireless AP

Dari frame Probe Response yang diterima, wireless client memilih wireless AP dimana ia akan mencoba melakukan authentikasi dan koneksi. Wireless client menggunakan faktor2 berikut saat menentukan wireless AP yang mana yang harus dipilih:

• Capabilitas wireless AP

Wireless AP memperkenalkancapabilitasnya didalam frame Probe response. Jika wireless clients tidak mendukung capabilitas yang diperkenalkan di dalam Probe response tersebut maka wireless client mengalami masalah jaringan wireless – tidak bisa memilih wireless AP. Misal wireless AP diactivekan security WPA2 sementara wireless clients tidak support WPA2 (wireless device 802.11b/g tidak support) maka wireless client tidak bisa memilih wireless AP tersebut. kita menganggapnya ada wireless problems.

• Nama jaringan wireless (SSID) cocok dengan jaringan preferencenya

Windows XP wireless auto configuration memelihara daftar jaringan wireless yang kita pilih (preferred wireless network). jika nama wireless network SSID tidak cocok dengan yang ada dalam daftar nama2 SSID yang ada, maka default Windows tidak bisa terhubung ke wireless AP. Jika clients wireless menerima beberapa Probe response yang ada dalam daftar nama SSID, maka client wireless memilih menurut urutan tertinggi dalam daftar preferred SSID.
Jika nama2 wireless network SSID dari frame Probe response yang diterima tidak cocok dengan jaringan dalam daftar preference, Windows akan memunculkan pesan “One or more wireless networks are available” atau “Connect to a wireless network”. jika user mengklik pesan ini, maka user memilih koneksi ke jaringan wireless baru.

• Kekuatan signal

Wireless clients adapter memilih wireless AP dengan signal terkuat dari daftar nama2 SSID yang ada yang paling tinggi dalam daftar preference wireless name.

3. Proses authenticasi terhadap wireless AP yang dipilih

Setelah memilih wireless AP yang akan dikoneksikan, proses selanjutnya adalah proses authentikasi. Jenis authentikasi tergantung capabilitas security wireless AP dan bagaimana client dikonfigure untuk melakukan authentikasi jaringan wireless.
Jika anda menambahkan wireless network dari tab Wireless network pada property wireless connection anda, maka by default adalah open system authentication dan kemudian IEEE 802.1X. Jika anda mengkoneksikan lewat dialog box Connect to Wireless Network atau Choose a wireless network, maka setting authentikasi ditentukan dari capabilitas frame Probe response wireless AP. Windows XP /Vista dapat menentukan dari frame probe response apakah menggunakan open system authentication tanpa encryption, opensystem authentication dengan inkripsi WEP, authentication WPA-PSK, ataupun authentication WPA2-PSK. Sering terjadi masalah jika gagal melakukan proses authentikasi ini.

4. Proses koneksi terhadap wireless AP yang dipilih

Setelah selesai melakukan proses aythentication, wireless adapter dan wireless AP saling bertukar serangkaian pesan untuk membentuk suatu koneksi.

5. Mendapatkan konfigurasi TCP/IP

Setelah koneksi terbentuk, wireless client dapat memulai mengirim frame wireless yang mengandung paket TCP/IP. Jika wireless clients dikonfigurasi untuk menerima IP address automatis, maka ia akan menggunakan DHCP untuk request suatu konfigurasi IP address. umumnya wireless AP mempunyai layanan DHCP server untuk menjawab request wireless clients untuk konfigurasi IP.
Dengan memahami ke lima proses diatas, akan memudahkan kita dalam melakukan troublehooting masalah jaringan wireless.

Masalah umum wireless – masalah konektivitas

Paling banyak dalam masalah wifi adalah sebagai berikut:

• Tidak berhasil melakukan koneksi wireless
• Koneksi yang intermittent

Kedua hal inilah yang paling banyak kita jumpai dalam hal wireless problems.

Tidak berhasil melakukan koneksi wireless

Yang paling banyak dalam masalah jaringan wifi adalah tidak berhasilnya melakukan koneksi ke jaringan wireless, dari proses scanning sampai mendapatkan IP address. Alasan yang paling banyak dengan wireless problems ini adalah sebagai berikut:

• Konfigurasi yang tidak klop / tidak matching
• Wireless auto configuration di enable sementara tool wireless configuration bawaan dari vendor juga di install
• Wireless AP dikonfigurasi dengan filter MAC
• Sumber sinyal interferensi
• Sumber sinyal attenuasi / pelemahan

Konfigurasi yang tidak matching

Beberapa property yang berbeda dari wireless connection haruslah matching antara wireless AP dan wireless clients sebelum berhasil terbentuknya koneksi. Beberapa masalah jaringan wireless yang menyebabkan tidak matching adalah berikut:

Technology 802.11 yang tidak matching

Ada 3 standard wireless 802.11 yang berbeda saat ini yaitu 802.11b; 802.11g; dan 802.11a. sementara satu lagi masih dalam draft walau sudah mulai booming yaitu draft 2.0 802.11n. Walau banyak sudah pabrikan yang memproduksi teknologi yang bisa support beberapa standard dalam satu kemasan, bisa saja terjadi ke tidak cocokan dalam teknologi ini. Misalkan wireless AP dengan standard 802.11a tidak akan bisa terhubung dengan wireless clients dengan standard 802.11b/g. Akibatnya wireless problems akan terjadi.

Methoda authentikasi yang tidak matching

Wireless problems jenis ini yang paling banyak terjadi. Wireless client tidak berhasil melakukan authentikasi jika antara wireless AP dan wireless clients tidak klop. Method authentikasi pada jaringan wireless rumahan meliputi open system, shared key, WPA-PSK, and WPA2-PSK. Verifikasi terlebih dahulu method authentikasi yang dikonfigurasikan pada wireless AP, dan sesuaikan pada setting yang ada pada wireless client.

Kunci WEP yang tidak matching

Jika menggunakan authenkasi WEP pada standard device 802.11b/g/n dan menspesifikasikan kunci WEP, adalah sangat mungkin terjadi kesalahan pengetikan atau salah eja. Hal ini akan mengakibatkan wireless problems karena kunci WEP tidak matching. Ketidak sesuaian interpretasi antara wireless AP dan wireless client ini bakal menghalangi terjadinya komunikasi – yang akibatnya tidak terbentuk koneksi. Hal ini sering kita jumpai computer kita hanya mendapatkan IP address APIPA dan menampilkan status “Limited or no connectivity” pada wireless connection. Kita pun menganggapnya ada masalah jaringan wireless.
Method konfigurasi kunci WEP tergantung pada versi Windows pada wireless client.

• Pada Windows XP tanpa di install service pack, anda harus mengetikkan kunci WEP pada kolom Network Key, spesifikasikan format pada kunci WEP (baik character ASCII maupun Hexa), spesifikasikan juga panjang kuncinya (40bit atau 104 bit pada kolom Key length).
• Untuk Windows XP dengan SP1/SP2, anda harus menspesifikasikan key WEP dua kali pada Network Key dan Confirm Network Key. Format panjang key tidak perlu karena akan ditentukan secara automatis menurut kunci yang diketikkan. Untuk Windows dengan SP2 anda harus memilih WEP pada Data Encryption.

Jika anda menggunakan Wireless Network Setup Wizard dalam Windows XP SP2, semua devices yg support Windows Connect Now secara automatic dikonfigure dengan WEP key yang sama.

WEP Key index tidak match

WEP Key index adalah suatu nomor yang menspesifikasikan WEP key yang mana yang akan dipakai untuk encryption frame wireless. Anda bisa menggunakan sampai 4 WEP keys yang berbeda. Dalam prakteknya hanya ada satu key index yang dipakai, yang sama dengan kemungkinan WEP key pertama. Wireless AP dan wireless client keduanya harus dikonfigurasi mengunakan kemungkinan WEP key pertama. Jika tidak, maka terjadi masalah jaringan wifi tidak terjadi koneksi.
Menspesifikasikan kemungkinan pertama WEP key tergantung bagaimana wireless client dan wireless AP memulai penomoran ke empat kemungkinan WEP key. Misal bisa saja penomoran dimulai dari 1 (1 ~4) atau dimulai dari 0 (0~3). Pilih kemunkinan pertama WEP key. Misal, Windows XP tanpa service pack memulai penomoran dengan 0, sementara pada Windows SP1/SP2 memulai pada nomor 1.

Tidak match WPA-PSK atau WPA2-PSK

Jika anda memakai authentikasi WPA-PSK atau WPA2-PSK, anda harus melakukan konfigurasi nilai preshared key pada kolom Network key dan Confirm network key. Pastikan kedua wireless client dan wireless AP mempunyai nilai preshared key yang sama. Untuk WPA anda harus memilih TKIP pada Data encryption dan WPA-PSK pada Network Authentication. Untuk WPA2 dengan Windows XP2, harus memilih AES pada Data Encryption dan WPA2-PSK pada Network Authentication.
Jika anda menggunakan Wireless Network Setup Wizard dalam Windows XP SP2, semua devices yang support Windows Connect Now secara automatis dikonfigure dengan nilai WPA preshared key yang sama. Wireless Network Setup Wizard tidak support configurasi dari nilai WPA2 preshared key.

Wireless auto configuration di enable sementara tool wireless configuration fihak ketiga juga di install

Windows XP Wireless Auto Configuration memberikan support integrasi pada wireless networking dan membantu mengautomasi konfigurasi wireless. Wireless network adapters menyediakan suatu tool wireless network configuration. Jika adapter tersebut support Wireless Auto Configuration, maka anda tidak memerlukan lagi software tool dari vendor adapter tersebut. Untuk mengetahui apakah wireless adapter anda support Wireless Auto Configuration, klik kanan wireless connection dalam folder the Network Connections dan pilih property. Jika ada tab Wireless Networks maka wireless network adapter anda support Wireless Auto Configuration. Untuk menghindari konflik yang bisa membuat masalah jaringan wireless, maka tidak usah di install tool dari vendor ini.
Karena seringnya terjadi masalah saat konfigurasi dan koneksi jika Wireless Auto Configuration di-enabled dan wireless network configuration tool juga di install. Karena dalam hal ini kedua Wireless Auto Configuration dan wireless network configuration tool bisa saja mengirim setting kepada wireless network adapter, akibatnya adalah konfigurasi yang tidak matching – anda akan mengalami masalah.
Makanya untuk menghindari masalah nantinya – gunakan salah satu saja baik Wireless Auto Configuration atau wireless network configuration tool, jangan keduanya.
Misal saja wireless adapter anda mempunyai tool yang bisa anda gunakan, sementara tidak support Wireless Auto Configuration, maka disable saja Wireless Auto Configuration dan gunakan wireless network configuration tool. Bagaimana disable Wireless Auto Configuration? Pada Wireless Networks tab pada property wireless connection dalam Network Connections, hilangkan contrengan Use Windows to configure my wireless network settings.
Jika anda memutuskan untuk menggunakan wireless network configuration tool bawaan dari vendor, untuk keperluan setting jangan lagi menggunakan Wireless Networks tab, gunakan tool ini untuk setting seperti wireless network name (SSID), authentikasi dan encryption.
Jika menggunakan Wireless Auto Configuration, maka remove saja program bawaan dari vendor dari Control Panel-Add or Remove Programs ataupun dari Uninstall program tersebut.

Wireless AP dikonfigurasi dengan fileter MAC

Wireless AP memungkinkan kita menspesifikasikan address MAC (media access control – atau lazim disebut juga address physical atau address hardware) tertentu saja yg bisa mengirim frame kepada wireless AP. Fitur ini disebut sebagai MAC address filtering yg dirancang untuk memberikan layer keamanan extra pada jaringan wireless. Akan tetapi hacker bisa saja dengan mudah menghalangi keamanan exta ini dengan cara menangkap frame yang dikirim dari dan ke wireless client yang diijinkan dan me-reprogram wireless adapter dirinya untuk menggunakan valid MAC address dalam daftar wireless AP.
Jika wireless adapter tidak terdaftar dalam MAC address list pada wireless AP, maka anda mengalami wireless problems – clients tidak bisa akses ke wireless AP. Jadi pastikan wireless clients terdaftar dalam list MAC address yang dibolehkan access ke wireless AP.

Sumber Interferensi Signal

Standard 802.11b/g bekerja pada frequency 2.4 GHz yang sama dipakai pada perangkat wireless lainnya seperti cordless phone, microwave, perangkat keamanan dan monitoring rumah, dan juga camera video wireless. Sumber interferensi ini sangat mengganggu yang bisa mengakibatkan wireless problems dimana client wi-fi komputer tidak bisa koneksi ke wireless AP.
Untuk memstikannya, matikan sementara sumber interferensi ini atau pindahkan wireless client dan wireless AP jauhan dari sumber interferensi ini, dan lihat apakah ada perubahan atau masih ada masalah jaringan wireless.

Sumber Pelemahan / Attenuasi Signal

Sumber pelemah / penghalang signal seperti dinding, atap, lapisan metal antara wireless clients dan wireless AP dapat menyebabkan gangguan signal wireless, atau hilangnya kekuatan signal. Pada beberapa kasus bahkan kehilangan signyal sama sekali yang menyebabkan masalah wifi – tidak bisa terhubung sama sekali.
Lihat juga artikel pertimbangan dalam instalasi wireless.

Koneksi Yang Intermittent

Dalam beberapa kasus, banyak terjadi masalah dimana awalnya mendapatkan signal kuat dan tiba-2 terputus tanpa interfensi si user. Paling banyak masalah jarigan wireless ini disebabkan oleh berikut ini:

• Authentikasi 802.1X di enable pada wireless client sementara pada wireless AP tidak
• Duplikat Nama jaringan wireless (SSID)
• Sumber interferensi
• Sumber attenuasi / pelemahan
• Virus komputer
• Kerusakan perangkat atau driver yang kadaluarsa / outdated

802.1X Authentication di Enabled pada Wireless Client dan tidak pada Wireless AP

802.1X authentication secara default adalah enable pada semua koneksi wireless maupun wired. Pada Windows XP SP1, Microsoft mengubah proses authentikasi untuk jaringan wireless. Jika 802.1X authentication di enable dan proses authentikasi tidak selesai sempurna, maka koneksi akan putus. Hal ini biasanya terjadi 3 menit setelah koneksi terbentuk menggunakan system authentikasi terbuka.
Untuk memperbaiki hal ini pada Windows XP SP1, lakukan berikut ini:

1. Klik Start => Settings kemudian klik Network Connections.
2. Pada Network Connections, klik kanna wireless connection dan kemudian klik Properties.
3. Klik Wireless Networks tab => dibawah Preferred networks klik wireless network name anda, dan kemudian klik Properties.
4. Klik tab Authentication, kemudian kosongkan contrengan Enable IEEE 802.1x authentication for this network.
5. Klik OK dua kali untuk menerima perubahannya.

Prosedur ini umumnya tidak diperlukan pada komputer yang jalan pada Windows XP tanpa Service pack atau Windows XP dengan SP2. Akan tetapi perlu juga mematikan 802.1X authentication di disable jika menggunakan open system authentication. Prosedur diatas juga berlaku untuk Windows XP SP2.
Untuk Windows XP tanpa SP, lakukan berikut ini:

1. Klik Start => Settings kemudian klik Network Connections.
2. Pada Network Connections, klik kanan wireless connection anda dan kemudian klik Properties.
3. Klik Authentication tab, kemudian kosongkan contrengan Enable network access control using IEEE 802.1x
4. Klik OK untuk menyimpannya.

Duplikat Nama Jaringan Wireless

Salah satu alasan koneksi yang intermittent adalah nama jaringan wireless duplikat dengan jaringan wireless lainnya didalam jangkauan wireless clients. Misalkan, dalam kampus yang berdekatan terdapat dua jaringan wireless dengan nama SSID yang sama yang saling overlap. Dalam hal ini semua wireless AP yang memperkenalkan diri dengan nama SSID yang sama dianggap berasal dari satu jaringan wireless yang sama. Wireless client dari wireless AP anda bisa saja mengambil jaringan wireless AP yang lain dengan nama SSID yang sama tadi. Jika wireless client anda tidak di configure menurut method authentikasi dan key dari jaringan wireless yang lain, maka anda akan mengalami masalah jaringan wireless yang intermittend sampai wireless client anda kembali memilih wireless AP anda kembali.
Kebanyakan kasus nama duplikat dari jaringan wireless ini adalah cara setup jaringan wireless AP dengan setting default tanpa mengubah nama SSID nya. Makanya pastikan selalu mengubah nama default dari pabrik agar tidak terjadi kemungkinan nama SSID yang sama dengan jaringan wireless lain yang tidak mengubah default namenya.
Untuk memastikan duplicat nama jaringan yang sama, matikan dulu wireless AP anda dan periksa apakah wireless client masih menerima SSID yang sama juga dengan nama jaringan SSID dari wireless AP anda. Untuk menghindari masalah jaringan wireless anda, configure wireless AP anda dengan nama SSID yang unik.

Sumber Sinyal Interferensi

Seperti halnya sinyal interferensi yang bisa menyebabkan masalah jaringan wireless – kurangnya konektifitas, sinyal ini juga bisa menyebabkan koneksi yang intermittent. Perangkat seperti microwave oven, cordless phone, system keamanan dan monitoring rumah, dapat menjadi sumber interferensi yang membuat masalah.
Untuk memastikan, coba uji dengan mematikan sementara sumber2 sinyal interferensi tersebut dan lihat apa ada perubahan atau tidak.

Sumber pelemahan sinyal

Sumber pelemahan signal disamping bisa mengurangi kekuatan sinyal koneksi, dia bisa juga menyebabkan masalah – koneksi yang intermittent. Anda perlu memperhatikan korelasi terjadinya intermittent dengan sumber pelemahan sinyal ini. Misal saja ada terjadinya intermittent saat ada seseorang yang sedang membuka pintu garasi yg terbuat dari metal.

1. Click Start => Control Panel => Click Network and Internet Connections
2. Dibawah Network and Internet Connection => Click Network Connection
3. Sekarang kita bisa melihat status dari koneksi NIC network adapter pada komputer kita dibawah Network Connections window dengan kemungkinan status sebagai berikut:

1. Pastikan terlebih dahulu dengan membuka browser internet kita dan check ke website tertentu misal saja ke www.computer-network.net atau ke www.wireless-router-net.com atau kemanapun. Jika anda bisa mengkases website tertentu akan tetapi website yang lain bagus, berarti tidak ada masalah pada sisi jaringan anda. Masalah terletak pada fihak ISP yang mungkin salah satu backbonenya rusak atau putus. Jika sama sekali anda tidak bisa membuka internet kemanapun, teruskan langkah berikut.
2. Lepaskan sambungan modem yang ke line telpon atau Cable line, tunggu beberapa saat barang semenit kemudian koneksikan lagi.
3. Lepaskan sambungan wireless router dari modem (sambungan antara port LAN pada modem dan port WAN pada wireless router), tunggu beberapa saat kemudian sambung lagi. Ini jika anda mempunyai perangkat terpisah antara wireless router dan modem.
4. Restart komputer anda dan ulangi untuk membuka dan akses website. Jika anda bisa mengkases website akan tetapi koneksinya lambat sekali sementara komputer lain bisa mengkases (jika ada lebih dari dua komputer dalam jaringan) anda bisa mencurigai beberapa komputer yang lain sedang mengkonsumsi bandwidth sangat intensive mungkin sedang streaming HD media dari internet atau banyak melakukan sharing files dengan beberapa komputer. tutup di komputer lain tersebut beberapa aplikasi yang mencurigakan dan bila perlu matikan sementara untuk memastikan masalah. Jika tak satupun website terbuka, maka lakukan langkah berikut ini.
5. Jika anda mempunyai modem dan wireless router terpisah, cobalah putuskan koneksi ke wireless router dan koneksikan komputer anda langsung kepada modem. Restart komputer anda dan coba lagi akses internet. Jika anda sukses akses ke internet, maka anda bisa memastikan ada masalah dengan wireless router anda.
6. Jika langkah tersebut masih juga belum berhasil akses internet, maka bisa dipastikan ada masalah dengan modem anda atau ada masalah dengan IS P anda. Telpon ISP anda untuk memastikan kalau ada masalah dengan layanan Internet.

1. Klik kanan adapter tersebut dan pilih Repair. Perhatikan apakah sudah normal connected atau masih limited. Langkah ini memastikan untuk mendapatkan IP address dari DHCP server.
2. Buka property TCP / IP dari adapter anda dan pastikan bahwa TCP/IP konfigurasinya adalah obtain IP address automatically.
3. Putuskan koneksi ke modem, tunggu sebentar dan koneksikan lagi.
4. Jika ada wireless router terpisah dengan modem, putuskan koneksinya – tunggu beberapa saat dan hubungkan lagi.
5. Restart komputer anda
6. Sampai langkah ini masih juga status limited, maka lihat konfigurasi router atau apakah konfigurasi DHCP nya sudah enabled.
7. Restart komputer anda. Jika status masih Limited or no connectivity , dan jika wireless komputer dan modem terpisah, cobalah putuskan modem dan router terus koneksikan komputer anda langsung ke modem. Restart komputer dan periksa apakah status sudah berubah.
8. Jika masih juga status limited, hubungi ISP anda. Status ini menunjukkan adanya DHCP gagal fungsi tidak bisa memberikan IP address ke clients. Biasanya fihak ISP memberikan konfigurasi DHCP kepada clients.

1. Periksa apakah ada kebel terlepas
2. Jika kabel sudah terhubung sempurna ke router / Switch, cobalah swap ke port lain pada router / Switch. Anda juga bisa memeriksa status lampu pada router atau switch saat kabel terhubung ke komputer nomor berapa port tersebut terhubung, biasanya lampu akan berkedip jika ada hubungan ke wireless router / switch pada port yang bersangkutan.
3. Jika masih juga status terputus, cobalah ganti kabel jaringannya dengan yang baru atau coba pinjam dengan kabel yang terbukti jalan dari komputer sebelah.
4. Jika masih status terputus, sementara komputer lain jalan – maka anda bisa mencurigai adapter anda rusak. Gantilah dengan yangbaru.

 

1. Buka [Wireless Network Connection] di taskbar Anda dan di bawah [Related Tasks], pilih [Change advanced settings]. Lihat gambar dibawah ini;
2. Pilih tab [Wireless Networks] dan pilih jaringan yang sedang berjalan dalam daftar di bagian bawah. Klik [Properties] untuk membuka jendela baru. Lihat gambar dibawah;
3. Klik pada tab [Authentication] dan sekarang hapus centang pada box [Enable IEEE 802.1x authentication for this network]. Jika kotak ini dicentang, maka itulah sebabnya Anda mendapatkan ” Windows was unable to find a certificate to log you on to the network” . lihat gambar dibawah;

Masalah Jaringan Komputer beserta solusinya dalam mengkomunikasikan data

• How do I get into Windows Device Manager?
• Identifying problems in Windows Device Manager.

• How do I remove a device in Windows Device Manager?
• Listing of network drivers and network card manufacturers.

1. Open the Windows command line.
2. From the command prompt type ipconfig and press enter. This command should give you an output similar to the example below.

1. Turn off the power to the computer and leave it off.
2. Unplug the power to your router and cable modem or DSL modem.
3. Leave the power cables disconnected for 10-15 seconds and then plug in your modem and then your router again.
4. Finally, turn on your computer again and repeat this step to see if you can ping your router.

1. Turn off the power to the computer and leave it off.
2. Unplug the power to your router and cable modem or DSL modem.
3. Leave the power cables disconnected for 10-15 seconds and then plug in your modem and then your router again.
4. Finally, turn on your computer again and repeat this step to see if you can ping your router.

Top 10 Basic Network Troubleshooting Tools Every IT Pro Should Know

Network troubleshooting tools are a necessity for every network administrator. When getting started in the networking field, it is important to amass a number of tools that can be used to troubleshoot a variety of different network conditions.
While it is true that the the use of specific tools can be subjective and at the discretion of the engineer, the selection of tools in this article has been made based on their generality and common use. This article reviews the top 10 basic tools that can help you troubleshoot most networking issues.

10. Ping

The most commonly used network tool is the ping utility. This utility is used to provide a basic connectivity test between the requesting host and a destination host. This is done by using the Internet Control Message Protocol (ICMP) which has the ability to send an echo packet to a destination host and a mechanism to listen for a response from this host. Simply stated, if the requesting host receives a response from the destination host, this host is reachable. This utility is commonly used to provide a basic picture of where a specific networking problem may exist. For example, if an Internet connection is down at an office, the ping utility can be used to figure out whether the problem exists within the office or within the network of the Internet provider. Figure 1 below shows an example of the ping utility being used to obtain the reachability status of the locally connected router.

Figure 1: Ping utility

9. Tracert/traceroute

Typically, once the ping utility has been used to determine basic connectivity, the tracert/traceroute utility can used to determine more specific information about the path to the destination host including the route the packet takes and the response time of these intermediate hosts. Figure 2 below shows an example of the tracert utility being used to find the path from a host inside an office to www.google.com. The tracert utility and traceroute utilities perform the same function but operate on different operating systems, Tracert for Windows machines and traceroute for Linux/*nix based machines.

Figure 2: Tracert/traceroute utility

8. Ipconfig/ifconfig

One of the most important things that must be completed when troubleshooting a networking issue is to find out the specific IP configuration of the variously affected hosts. Sometimes this information is already known when addressing is configured statically, but when a dynamic addressing method is used, the IP address of each host can potentially change often. The utilities that can be used to find out this IP configuration information include the ipconfig utility on Windows machines and the ifconfig utility on Linux/*nix based machines. Figure 3 below shows an example of the ifconfig utility showing the IP configuration information of a queries host.

Figure 3: Ifconfig utility

7. Nslookup

Some of the most common networking issues revolve around issues with Dynamic Name System (DNS) address resolution issues. DNS is used by everyone using the Internet to resolve commonly known domain names (i.e. google.com) to commonly unknown IP addresses (i.e. 74.125.115.147). When this system does not work, most of the functionality that people are used to goes away, as there is no way to resolve this information. The nslookup utility can be used to lookup the specific IP address(es) associated with a domain name. If this utility is unable to resolve this information, there is a DNS issue. Along with simple lookup, the nslookup utility is able to query specific DNS servers to determine an issue with the default DNS servers configured on a host. Figure 4 below shows an example of how the nslookup utility can be used to query the associated IP address information.

Figure 4: Nslookup utility

6. Netstat

Often, one of the things that are required to be figured out is the current state of the active network connections on a host. This is very important information to find for a variety of reasons. For example, when verifying the status of a listening port on a host or to check and see what remote hosts are connected to a local host on a specific port. It is also possible to use the netstat utility to determine which services on a host that is associated with specific active ports. Figure 5 below shows an example of the netstat utility being used to display the currently active ports on a Linux machine.

Figure 5: Netstat utility

5. PuTTY/Tera Term

When connecting to a variety of different types of equipment, a telnet, SSH or serial client is required; when this is required both the puTTY and Tera Term programs are able to provide these functionalities. The selection of one over the other is strictly a personal preference. Figures 6 and 7 below show both puTTY and Tera Term being used to connect to a host via SSH.

Figure 6: PuTTY

Figure 7: Tera Term

4. Subnet and IP Calculator

One of the most important tools in the belt of a junior network engineer is an IP network calculator. These can be used to unsure a correct IP address selection and with this a correct IP address configuration. While this type of tool is used by senior level network engineers, much of the information obtained from the tool becomes simpler to calculate the longer and more experience you have in the field. Two of the more commonly used free IP calculators include Wildpackets (Bitcricket) Network Calculator and Solarwinds Advanced Subnet Calculator which can be found at the links below.
http://www.bitcricket.com/downloads/IPCalculator.msi
http://downloads.solarwinds.com/solarwinds/Release/FreeTool/SolarWinds-Subnet-Calculator.zip

Figure 8: Subnet calculator

3. Speedtest.net/pingtest.net

A very easy test that can be used to both determine the Internet bandwidth available to a specific host and to determine the quality of an Internet connection is the use of the tools available at the speedtest.net and pingtest.net websites. The speedtest.net site provides the ability to determine the amount of bandwidth that is available to a specific host at a specific point in time; this is often a good tool to use when measuring how long it is going to take to upload or download information from a local to remote host. This measurement can also be used to determine whether the connection is offering the amount of bandwidth that was purchased from the Internet provider; keep in mind however that some amount of bandwidth difference is expected between the quoted bandwidth purchased and the measured bandwidth. The pingtest.net website is used to determine the quality of the connection by measuring the ping response times and jitter amounts over a short period of time. This information can be used to determine a likelihood of how well the measured connection will deal with certain types of high demand traffic like Voice over IP (VoIP) or gaming. Figure 9 and 10 below show example output from both of these sites.

Figure 9: Speedtest

Figure 10: Pingtest

2. Pathping/mtr

In an effort to take advantage of the benefits of both the ping and tracert/traceroute commands, the pathping and mtr utilities were developed. Both of these tools take the functionality and information that can be obtained from these types of tools and provide a more detailed single picture of the path characteristics from a specific host to a specific destination. Figure 11 and 12 below show examples of these two tools and what information they provide.

Figure 11: Pathping

Figure 12: Mtr

1. Route

The last of the tools covered in this article is the route utility. This utility is used to display the current status of the routing table on a host. While the use of the route utility is limited in common situations where the host only has a single IP address with a single gateway, it is vital in other situations where multiple IP address and multiple gateways are available. Figure 13 below shows an example of the route utility being used on a Windows machine.

Figure 13: Route Utility

Summary

As with any job, the type of tools that are quickly available can greatly influence the amount of time that it takes to complete a job. When troubleshooting a networking issue, the amount of time that it takes to find and fix a problem directly affect the wasted costs that it causes to any system relying on the network. This article has taken a look at the 10 most commonly used tools that can help in ensuring that the time that it takes to find and fix a problem is as short as possible. I hope the information in this article can be helpful in future troubleshooting.

Local area networks (LAN) are integral to the operation of many businesses today. The most common LANs use Ethernet, a data link layer protocol, and Internet Protocol (IP), a network layer protocol. A LAN is comprised of many elements: printers, monitors, PCs, IP phones, servers, storage hardware, networking equipment, security software, network applications, enterprise applications, office productivity applications, and more. Devices on the network are linked physically by twisted pair copper, fiber or wireless access points. Troubleshooting LAN networks is typically the job for the frontline network support staff - engineers and technicians. Common network troubleshooting problems include user connection issues and slow networks. Root causes of network troubleshooting problems are frequently caused by one of these three sources: 1. Physical layer: copper, fiber or wireless Possible causes: Damaged or dirty cabling or terminations Excessive signal attenuation Insufficient cable bandwidth Wireless interference 2. Network Layer: Ethernet and IP Possible causes: Damaged networking devices Incorrect or sub-optimal device configurations Authentication and association issues Insufficient network bandwidth 3. Switches and VLANs Possible causes: Excessive utilization Too many errors Incorrectly assigned VLAN membership Traffic priority (CoS/QoS) issues Best practices for successful LAN troubleshooting include these steps: 1. Identify the exact issue or problem: Have the person who reported the problem explain how normal operation appears, and then demonstrate the perceived problem. 2. Recreate the problem if possible: Ask yourself if you understand the symptoms, and verify the reported problem yourself if possible. 3. Localize and isolate the cause: Attempt to isolate the problem to a single device, connection, or software application. 4. Formulate a plan for solving the problem: Research and/or consider the possible solutions to the problem. Consider the possibility that some solutions to the problem at hand may introduce other problems. 5. Implement the plan: Your actual solution to the problem may be replacing hardware, implementing a software patch, reinstalling the application or component or cleaning a virus infected file. If the problem is the user account, the user’s security settings or logon scripts may need to be adjusted. 6. Test to verify that the problem has been resolved: After you have implemented the solution, ensure that the entire problem has been resolved by having the user test for the problem again. 7. Document the problem and solution: Documentation can be used for future reference to help you troubleshoot the same or similar problem. You can also use the documentation to prepare reports on common network problems for management and/or users, or to train new network users or members of the network support team. 8. Provide feedback to the user: This encourages users to report similar situations in the future, which will improve the performance of your network. If the user could have done something to correct or avoid the issue, providing feedback may reduce the number of future network problems. Importance of LAN troubleshooting tools and training Giving frontline network support staff the proper training, the right tools, and a solid network troubleshooting methodology results in faster LAN problem solving - saving staff time, closing trouble tickets quicker, minimizing downtime, and getting network users back to productivity faster.

Related Products Optiview XG Network Analysis Tablet AirCheck Wi-Fi Tester LinkRunner AT Network Auto-Tester OptiFiber Pro OTDR OneTouch™ AT Network Assistant Related Resources Network Problems on the Frontline: Turning techs into fast problem solvers Test your Frontline Troubleshooting IQ Frontline LAN Troubleshooting Guide (with 8 steps listed on this page) WLAN Troubleshooting Guide using AirCheck Wi-Fi Tester For Solution or Product Advice: U.S. / Canada: 1-800-283-5853 International: 1-425-446-4519 info@flukenetworks.com Gold Maintenance and Support Program

Troubleshoot Network & Internet Problems in Windows 7 & Windows 8

Share on

• Facebook
• Google+
• Twitter
• Print

When you have problems with your network and/or Internet connection, don’t hesitate to use the troubleshooting wizards bundled with Windows 7 and Windows 8. They are easy to use and they can help you identify what’s wrong and how to fix your problems. In this tutorial I will show how to start these network and Internet troubleshooting wizards and how to work with them in order to fix problems.

How to Find the Network & Internet Troubleshooting Wizards

One of the easiest ways to access the network and Internet troubleshooting wizards is to open the Network and Sharing Center and click or tap the "Troubleshoot problems" link.
This is how the Network and Sharing Center looks like in Windows 7.

In Windows 8, the Network and Sharing Center is a bit different. However, the "Troubleshoot problems" link can still be found at the bottom of the window.

This opens the list of Network and Internet troubleshooting wizards available in Windows.

As always, you can also use search to launch these wizards. In Windows 7, type the word "trouble" in the Start Menu search box. Then, click the Troubleshooting search result.

In Windows 8, go to the Start screen, type the word "trouble" and filter the results by Settings.

Then, tap the Troubleshooting search result.
Another way is to type the word "trouble" in the search box found on the top right of the Control Panel.

Clicking or tapping or Troubleshooting reveals the Troubleshooting window, where you find all the troubleshooting tools included in Windows.

To display the troubleshooting wizards we are interested in, click or tap Network and Internet.
You can start any of the available wizards, depending on the problem you are facing:

• Internet Connections - this wizard helps when you are connected to the network but the Internet doesn't work or you have trouble accessing particular websites;
• Shared Folders - use this wizard when you have problems accessing shared files and folders on other computers and devices from your network;
• HomeGroup - when you have problems viewing computers or shared folders that are part of the Homegroup, use this wizard;
• Network Adapter - this wizard is useful when you have problems with your wireless or network adapters. It helps with anything that is related to your network connection;
• Incoming Connections - this wizard is helpful when other computers have trouble connecting to your computer's shared files and folders;
• Connection to a Workplace Using DirectAccess - this wizard can be used when you have problems connecting to enterprise network domains. It is available only in Windows 7 Ultimate, Windows 7 Enterprise and Windows 8 Enterprise.

Start the Network & Internet Troubleshooting Wizards from the Command Prompt

The network and Internet troubleshooting wizards can also be started using the Command Prompt or the Run window.
Copy and paste the following commands:

• To open the Internet Connections troubleshooting wizard - msdt.exe -id NetworkDiagnosticsWeb;
• To open the Shared Folders troubleshooting wizard - msdt.exe -id NetworkDiagnosticsFileShare;
• To open the HomeGroup troubleshooting wizard - msdt.exe -id HomeGroupDiagnostic;
• To open the Network Adapter troubleshooting wizard - msdt.exe -id NetworkDiagnosticsNetworkAdapter;
• To open the Incoming Connections troubleshooting wizard - msdt.exe -id NetworkDiagnosticsInbound.

How to Use the Network & Internet Troubleshooting Wizards in Windows 7 & Windows 8

Each troubleshooting wizard is a bit different because it solves the specific problems it is supposed to solve. To help you understand how to use a troubleshooting wizard, I ran the Network Adapter wizard in order to understand what is wrong with the wireless network connection on my Windows 8 laptop. Using other wizards works the same way, using the same principles.
At the beginning of the troubleshooting wizard, before you press Next look for a link named Advanced.

Click or tap on it. This reveals some interesting options. For example, the Network Adapter wizard can automatically apply repairs. Check the appropriate box to enable this feature and click or tap Next.

The troubleshooting wizard detects that I have several network adapters and asks me to select the one I want to troubleshoot. In this case, I selected WiFi and pressed Next.

NOTE: The Network Adapter troubleshooting wizard displays also virtual network adapters, if you have installed virtualization software that uses such devices (e.g. VirtualBox).
The troubleshooting wizard starts the diagnostics process and displays a progress bar like the one shown below.

When it detects problems, it also tries to apply the fixes it believes are appropriate and then verifies if the problem still exists.

At the end of the whole process, the troubleshooting wizard shares details about the problem and its status.

In my case, the problem remained unfixed. The Network Adapter wizard proposes additional options via the "Explorer additional options" button. If you want to view detailed information about the problem(s) it identified and what it has done to fix things, click the small link that says "View detailed information".
To close the wizard, click or tap Close
Click on Close and you are done.
NOTE: If the troubleshooting wizard you have used hasn't detected any problems but you still have issues, you may have not used the correct wizard. In this case, try another troubleshooting wizard, which is related to the problem you are experiencing.

Troubleshooting Problems with a Wireless Network

If you have troubles connecting to wireless networks, we recommend reading the following troubleshooting guides:

• Troubleshoot Internet Connection Problems over a Wireless Network - this guide shows how to use the Windows built-in troubleshooting tools, to fix problems when connecting to wireless networks;
• Troubleshoot Wireless Network Connection Problems by Yourself - this is a step by step chart with questions and answers. Answering a series of questions takes you to the most probable root-cause and its solution;
• Fix Troublesome Wireless Connections by Removing their Profile - if you have problems with a wireless network which worked in the past, it can happen that its profile in Windows was changed or corrupted. This tutorial helps you fix problems in such scenarios.
• The Layman’s Guide to Solving Wireless Network Interference Problems - an awesome guide, sharing how easy it is to fix problems generated by the signal interference, caused by other networks in your area or by other devices.

Conclusion

Both Windows 7 and Windows 8 provide a complete list of troubleshooting wizards which can help you identify the root cause of your networking problems. When I have an issue, I use these wizards and, in most scenarios, they are able to identify the root cause.
Even when they cannot help me fix the problems I encounter, they provide information that is valuable to technical support staff that can fix things for me.

Share on

• Facebook
• Google+
• Twitter
• Print

Comments

I just installed a new windows 7 computer, it found my home network/internet connection with no problem. It sees the wireless laptop (vista machine) also on the network, but can't access it, and the other way around. I have a netgear wireless router, and hardline installed. I have also gone through several of the trouble-shooter dialogs, and all come up with the same thing, unable to fix the problem. Also have even gone thru and disabled password requirements as well.

• reply

I also have the same problem, I can't seem to connect to my vista laptop from my windows 7 laptop but I can connect the other way around. Any ideas on how to fix this issue?

• reply

Windows 7 has a very complete list of troubleshooting wizards which can help you identify the root cause of your networking problems and ways to fix them. In two months of using it, I never had a networking problem which Windows 7 couldn't identify correctly. The instructions I received helped me fix most issues by myself. When not, they contained very useful information which helped in the dialog with my Internet provider and their technical support people understood what's happening and what they need to fix.

• reply

I just installed Windows 7 on a machine that was running Vista previously. I have a wireless network up using a DLink router. On this network I have no issues connecting with Vista, a Blackberry Wifi, iPhone and an older laptop with XP. Windows 7 just will not connect. This is the laptop that was connected using Vista the day before I put Windows 7 on it, so I know the hardware works. I'm really disappointed that something as simple as connecting to Wifi is such a challege with Windows 7. I'm an IT person myself, and the wizards are useless. I see it disable and enable the ethernet adapter and ultimately just tells me it doesn't work. Wonderful.

• reply

The problem is not with Windows 7, it lies with the firmware of the DLink router. Please update it to the latest version and most probably it will work. With a new operating system you cannot keep out-of-the-box compatibility with lots of older hardware. Something will not work, you have to give up on some devices. And for you, the easiest solution is to go to the DLink website, download the latest firmware for your router and update it.

• reply

Hello! I bought a new laptop for my husband with Windows 7 64bit. I transfered his settings from his Windows XP Pro laptop using the Easy Windows Transfer cable.
This is where I think the problem is. But not positive, because my daughter also got a new windows 7 laptop, (they are both Toshiba's) .
OK so the issue is I have been trying to get the wireless network connection to connect automatically. Every time I either start or put the computer to sleep, I have to manually click on my network, and then click connect, even though the button is checked to connect automatically, then the biggest pain is I have to put in the network key each and every time. Now my daughter's laptop, no problem it does it like it should. That is why I said about the Easy Transfer. I did not use it on hers. So I am pretty sure it is not the router, Linksys. It has been updated to the lastest firmware. I can also see all the other computers in my network. And windows troubleshooter never ever has helped me solve anything. It just says no problems were detected. So I am at a loss. It is more of pain in the butt than anything. I just can't stand having to type in my key every time. Thank you

• reply

Hi
I have a problem regarding windows 7 and I will really appreciate it if you can assist me,
I am running windows 7 32 bit and I have a Vodafone K3765-Z and it doesn’t connect to internet I am thinking that maybe I need to find a different software to connect it and initially I was using Win7 64bit and it was connecting perfectly.
Please tell me what I need to do in odder to make it work.

• reply

Unfortunately we don't have the vodafone model you have and cannot help you. Did you try Vodafone support? or maybe the Hwawei forums?

• reply

I just set up my network manually like I always do with XP on my WIN 7 laptop and it works great. When I shut down and restart it it tells me I am on a public network and have now connection. I did manage to get it back to a home network and got it working again.
How do I get the settings to stay?
As soon as I get all the drivers I will install XP and get back to something that works for me.

• reply

Yahoo msgr on win 7 ultimate
i'm using windows 7 ultimate and i can't download yahoo messenger 10. i've been trying to download it for days... i've turned off my firewall, etc...but it doesnt seem to work. what seems to be the problem?
can anyone help me please???? thank you..

• reply

Can you please share some screenshots, error messages, etc?
Yahoo Messenger 10 is compatible with Windows 7 so it should work without problems.

• reply

thanks for the quick response!=)
i have figured out what the problem is.it's not about my laptop or windows 7. it's about the internet connection that's limiting me to download something...

• reply

Hi
My laptop works fine at home via a wireless router but I cannot get online when away from home. I have tried a friend's secure network (with key) and various open ones.
I have tried to connect to open networks at home but my laptop automatically switches to my own security enables network. Could it be that there are settings that I have to alter so that my laptop will work on other networks?I thought this should work automatically?

• reply

First, I really like windows 7 however I can not connect to the wireless router at work. I can connect to my new Net Gear router at home with no problems. From everything I 've read the work router most likely needs updated firmware. I tried unistalling Norton to see if the fire wall was preventing connection but that wasn't it. I tried the wizards but they said my computer was configured correctly, that the router was not responding to it. I see that this is a reacuring problem and am starting to think its the routers firmware. I just wanted to exhaust every possibility before I give my IT guy a fit. Dose anyone have any input? Thanks

• reply

The most probable root-cause is the age of the router and its firmware. Try to speak with your company's IT department so that they have it updated and fixed.

• reply

So, the problem is that the router needs an update so that Mr. windows 7 can connect! Havent you thougt about "old" routers in cafes and in foreign countries wich simply are not going to be updated so quikly... Could all the engeneers at Microsoft not think about this. Honestly: thats making life complicated!

• reply

Blaming it on Microsoft is not really going to help anybody. There are more problems with vendors of network devices which don't really update their products, have buggy firmware, than with Microsoft not ensuring wide-spread compatibility of their products across a large variation of devices.
If there is blamed to be placed, it is more with the vendors of such products than with Microsoft. What Microsoft tries to do is push the world forward and introduce newer and better technology. They have their shortcomings too, but not as many as people tend to think. We are too used to blaming Microsoft for everything and we are simply blind to the actual problems and who is generating them.
Anyway... not trying to start a "flame war". Just trying to explain things.

• reply

I have windows 7 on my computer but I have a problem that I can not conect the printer on the newtwork .The printer is hp laserjet 1300

• reply

Check this article: http://www.7tutorials.com/how-share-printer-your-network

• reply

you have to update the o/s or try to get fix the errors with the help of customer care from HP..... you get toll free number in hp site......

• reply

Thanks for your suggestion

• reply

I recently bought a Dell1400 inspiron laptop with windows 7 operating system and the hard drive was bad via tech support looking at thew system through the internet,conecting remotely (right up front they could'nt get me to connect through the wifi and had to plug in a hard line. The diagnostic outcome was a bad hard drive.They came to replace the hard drive and now I cannot get the intrernet with hard line or wifi. I have multiple x-box live accounts connecting cordless as well as two other laptops and they have no problems. I'm wondering if there is possibly something That the tech could have left unplugged inside or what? I've already tried tech support with dell and they want money to go any further. (even though I've never been able to get onto the web)
Any sugestions????

• reply

DELL E5500 with Windows 7 will not auto connect to WiFi.
I have four Dell laptops. Three running XP and a new Dell Latitude E5500 with Windows 7.
The Windows 7 Dell WILL NOT automatically connect to ANY wireless network. I have to manually connect every time. It is not the router firmware. It is not hardware. There are enough people having the same problem here that Dell or Microsoft need to solve this and post the solution.
It's also not router dependent. I travel every week to several locations. I have an ATT Uverse router at home, Linksys, Belkin, and Verizon Mifi that I regularly connect to with the other XP laptops.

• reply

Recently had some problems connecting to a network.
Connected fine until brother decided to unplug modem and router whilst I was connected. Replugged and rebooted everything, restarted computer; it now is unable to find the network. The profile is saved, and 'automatically connect' checked, but fails to do so. Have removed network profile and added but hasn't changed anything. The network I want to connect to doesn't appear in 'list of available networks'. I know that the router is definitely broadcasting the network because I am still able to connect to it via my laptop.
Any suggestions? It's extremely frustrating...

• reply

Ive been having the same problem, I could not connect to the network because its like saved or something.... you would think it would be in the registry or something in that case.... I could be wrong... Have you found a solution to this problem yet?

• reply

THE WIZARDS ARE CRAP --
Do a search -- thousands of people are having horrible problems networking Windows 7 -- IP6 conflicts with some older routers, which the wizards don't pick up, computer names that contain characters (like dashes) cannot be read and the wizards don't pick this up, several services must be active and the wizards don't pick those up (I had to go in manually and activate one, the wizard did NOT notify me the service wasn't running (the DNS)) -- after six weeks of trying everything, I am paying to have my computers downgraded to XP. Networking in Windows 7 is insanely difficult and the wizards don't even pick up on any of the problems.

• reply

Can't figure out why you are having such a problem. My home network consists of computers running Windows XP, Vista, Windows 7 and even Ubuntu and all are able see each other - and share files - with no problem. My router is a Linksys wrt54g model.

• reply

I have a similar set up and the exact same router; however, I've had problems with my brand new desktop running Windows 7 - got a new adapter (also Linksys - WUSB600N with updated driver) and once I over-rode the power settings, at least I'm not losing my connection every time it hibernates or sleeps. HOwever, I continually get a low signal and it's slow to load - even though I've changed *NOTHING* about the location of the machine or the router.
I truly believe it's the adapter's driver and compatibility issues with Dell. After hours on the phone with various techies at both Dell and Cisco (maker of Linksys), I gave up. I am now debating whether I should get a new router (more compatible with Win 7) or a repeater (to strengthen the signal).
I have to repeat - when I had a desktop in this exact same location running XP against the same network, albeit with an older adapter (WUSB54G), I never had connectivity or signal issues.
My XP laptop has *no* issues, even if wirelessly connected from the same location as the desktop.
My daughter's Vista laptop has no issues.
Another daughter's HP Win 7 has no issues, though it is not wirelessly connected.
I could cheerfully scream.

• reply

I don't know

• reply

I have to agree that the root cause of the network and internet connectivity is NOT the router firmware- after 6 weeks of phone-based trouble shooting and 5 visits by my DSL provider (Verizon), the fix has FINALLY come in the form of an old (yes, OLD) Westell 6500 modem (provided by Verizon) in tandem with my Cisco router. The previous system configuration dropped my network offline every 7 minutes- like clockwork, for over 6 weeks.
The real shame is that Verizon even replaced 300 plus-feet of underground wire trying to eliminate this problem.
It is hopeful that eventually, providers such as Verizon and others will recognize that M$ 7 has been the culprit. Gees, hate to see that invoice!!!
Just a very very disgruntled Lenovo and M$ 7 user.

• reply

I`m trying to setup a wireless network at home and something is`nt right, not sure how to proceed. I have a Tenda wireless_N Router, a Speedstream DSL modem, and my computer is running Windows 7. Everything is recognized by Windows, and I am connecting, but when I go to load a webpage or check email, the "connecting to Ameritech DSL" box keeps popping up; it`s like I`m connected, but my computer insists on dialing my DSL modem again. When this happens, my system bogs down badly, and hard-drive activity is crazy. I finally have to unplug from the router, which is Win 7 certified, and go back to using just the DSL modem, knocking out my network. I`m new at networking, so i`m at a loss here. The other end of the network is a Win XP box upstairs, and no problems there, it shows the network and is connected. Thanks for any help.

• reply

i have dell xps1530 laptop. i have this lan connection from office and after connecting it my internet works fine but i cannot browse the other computers but every other person can. i have turned my firewall off, shared everything, turned mt security to minimum, network exploring is on but when click on the computer name it cant open the location. tried troubleshooting too...plz help me out here guys :(

• reply

What kind of Windows do you have on this dell xps1530?

• reply

windows 7

• reply

Try the following:
Make sure you've set the network location correctly. It should be home or work.
See details here: http://www.7tutorials.com/network-locations-explained
Then, double check all network sharing settings. See details here:
http://www.7tutorials.com/how-customize-network-sharing-settings-windows-7
Then use this guide for sharing stuff with other computers:
http://www.7tutorials.com/share-libraries-or-folders-using-sharing-wizard
Maybe there's a small wrong setting on your computer (like Network Discovery turned off).
Hope it helps.

• reply

I just received a new laptop from work that has a built in wireless card. I seem to have everything set up, and am currently using it to search this forum. The problem is that occasionally I get disconnected, and when this happens, the network list won't repopulate, even after I click on refresh. I even turn off the wireless adaptor and turn it back on, it still will not refresh the list of networks. The only way to reconnect is to shut the computer down and restart it... Is there some kind of setting that is causing this issue?

• reply

Hi,
I've just completed a build of a home PC with the P7P55D LE motherboard.
Previously I had XP on another PC and my internet was rock solid.
Now when I reboot my new windows 7 PC it reports that the internet is down.
I have to reset the router or sometimes by disabling and re-enabling the on-board NIC on the m/b it comes back up.
I have tried the following:
reducing the lan speed to 100 full.
disabling all the wol features
disablign the green feature within the network card.
Any ideas before I purchase a PCI network card to see if the problem IS the m/b?
Cheers.
Just to add when the internet locks up I can still access the Routers setup page via a browser session.
All the lights on the router appear as normal, however windows 7 reports there being a problem with the internet...which the "helper" tries to diagnose and comes back with "unknown error"

• reply

Can you borrow a network card? It sounds like your on-board one has issues. Better to check though with another card before spending money on one.

• reply

Hi,
I have a Dell, Inspiron 11 with Windows 7 & 1397 WLAN Mini-Card. It does not detect the wireless network.
I have tried manually adding the net work, disabling/enabling it, also uninstalling/intalling Wifi & adapter from Device Manager, as well as turning off & on wireless button, but no use!
Please help.

• reply

i have 2 computers in the same network,one of them does not access the internet and the other does.This happened after i formatted my pc,installed the drivers my second accessed the internet and when i did windows 7 updates and i restarted the pc,i couldnt access the internet.my other computer did the same updates and its fine,tell me pls what to do?im desperate i tried everything i know.

• reply

I don't think the updates have anything to do with your problems unless you have installed the wrong driver to your network card and now it malfunctions. Have you tried the troubleshooters mentioned in this tutorial? They can definitely help you understand what is going on.

• reply

hi am using windows 7 in my dell laptop
actually i tried to connect through wireless internet
status is connected
but it is showing no internet acess
like
access type: No internet access
wat can ido for this plz help me

• reply

Hi, guys. I got same problem with you. I bought my Dell inspiron last Christmas. It worked sharp at the first few months, but got slow after that. It took about 15 mins to start up. I can even walk away and brew my coffee during waiting! I even thought about reinstall my computer! My friend recommended the software tuneup360 and Norton systemwork. I tried both. Norton did look really powerful and could do lots of thing, but it was too difficult for me and too expensive, while Tuneup360 is my type. I just need to click one big “fix now” button and get my computer fixed. Now my computer takes only 30 sec to start up.

• reply

I have recently bought a new laptop with windows 7 and it connects perfectly to my wireless router at home when im in the same room as it but not any further away, when signal is good, fair etc. I know other laptops have been able to connect further away and my blackberry has no problem. It seems it will only connect if signal strength is at its maximum which is very frustrating! can anyone help?

• reply

My computer has been working perfectly with wireless connection until 2 days ago. It's Lenovo laptop with Windows 7 Home Premium. My another Lenovo laptop has no problems with wireless connection. The problem is: Access Type: No Internet Accecess
I have tried the following methods and none of them work:
(1) reboot many times
(2) no connection even in safe mode
(3) in services there's no "##Id_String2.6844F930_1628_4223_B5CC_5BB94B87 9762 ##"
(4) restart the DHCP service
(5) stopped windows defender, and disabled it. Rebooted.
(6) start/run/and type services.msc /go to Bonjour service and click on properties / change it to delayed start
(7) cmd run as administrator run netsh winsock reset
What can I do?

• reply

What about - reinstall the drivers for the wireless card? Uninstall them completely, reboot and install the latest version.

• reply

One of the simple way to troubleshoot the internet problem is OpenIE(internet explorer)and type the address u want to open if the connection is good than the page will open otherwise it will open button like (diagnose problem). click the button and it will detect the problem and show the details and what are the steps to take solve the problem. I have done many times like these to solve many internet problems.

• reply

..with the win 7, we are having problems accessing internet. we are getting good connectivity but acess type states "no internet". Does anyone have a solution? tks

• reply

I have installed new operating system i,e win 7. I am facing problem connecting to my wireless connection. Every time I try to connect it says wrong key for router whereas the key I am entering is correct. I can connect my cell phone using same key. Yesterday I was at my friends home and I was able to connect to his internet but I can't connect one at my place.
someone please guide me.

• reply

Absolutely right.. With the help of the network and Internet troubleshooting wizards, we can easily fix this network issues.. if the troubleshooting wizard hasn't detected any problems but you still have issues, it might mean that you used the wrong wizard.. In this case, try another wizard from the list which is related to the symptoms you are

Windows Networking: Troubleshooting Tips

Households are increasingly becoming multiple-PC homes. And as people add extra PCs to a home, they naturally want to share files between those systems. Typical multi-PC households also tend to have different operating systems; you may have a business laptop still running Windows XP, for instance, as well as an older media-center system using Vista and a Windows 7 computer that serves as a shared resource or specializes in gaming. Getting such disparate machines to talk to one another can be daunting.
In this article, we'll examine how to troubleshoot some common Windows networking problems. Let's start with basic connectivity troubleshooting.

Connecting to Your Network

You'll typically have network-connection issues when you fire up a new computer or upgrade to a new version of Windows. The lack of a network connection has no single cause, so here's a look at several potential problems and solutions.
Problems after upgrading Windows: Installing a new version of Windows on your system can wreak havoc on network connections. You may encounter different issues, depending on whether you upgraded or performed a clean install.
If you've upgraded from Windows Vista to Windows 7, it's possible that you'll simply need to reinstall the drivers for your networking hardware; that is more often the case if your connection is Wi-Fi rather than wired. The best approach is to download the new drivers from the Website of the motherboard or system manufacturer prior to performing the OS upgrade--but if you forgot to do that, the driver CD that came with your system or motherboard will very likely have drivers that work, even if they aren't the most current versions.
My main production PC and my Windows Home Server were both running only IPv4. A new Windows 7 install, which I performed on one of the systems, implements both IPv6 and IPv4. You would think that a machine running both the IPv6 and IPv4 protocols could connect to a system running only IPv4, but for whatever reason, that wasn't the case: The PC running both protocols would simply not connect to the one running only IPv4. At first, I simply deleted IPv6 from the new system. After this problem occurred several times, I wised up--and all my systems are now running both IPv6 and IPv4.
Laptop fails to connect: About 90 percent of the time, this happens because your laptop's Wi-Fi hardware is turned off.
Many laptops have an actual physical switch on the side that turns the wireless hardware on or off to save battery life. On some models it's a touch-sensitive button near the keyboard that resembles an activity light but is also the control for powering up the various radios in your laptop. The least-obvious kind are "soft" switches--applications that you need to run to enable or disable the wireless radios.
If you can't connect, the Windows network troubleshooter will typically launch; if it does, just follow the prompts. If the troubleshooter tells you that the laptop's wireless hardware is turned off, you'll have to figure out how to turn the radios back on. The method will vary from system to system. If the switch is a soft switch (a software utility), sometimes the Windows troubleshooter can turn the radios on for you. You'll have to deal with a physical switch yourself, of course.
The other 10 percent of the time, you're trying to connect over a wired network, but can't. The cause: Lots of laptops disable wired networking to save juice if you haven't plugged them into the wall. The solution here is to connect the power brick. If you can't do that, you'll need to enable wired networking manually in the Windows power management control panel, which you can find in the 'System and Security' control panel applet.

Sharing Files in Windows

All you want to do is share a few files between machines. Or maybe you want to copy files from one system to another. But you can't seem to actually move files around the network, even if networking seems to be functioning properly. Here are a couple of fixes.
If you're not using WHS, or if you don't need the security, you can always enable Windows Simple File Sharing. Bear in mind that you're giving up considerable security if you do this, but if all your systems are behind a hardware firewall on a router, you should be okay.
Next, bring up the Windows 'Network and Sharing Center' (one of the Windows panels). Click the Change advanced sharing settings link in the left panel.
Once you get to the advanced-networking panel, make sure that several radio buttons are turned on. You'll definitely want network discovery (so that you can see other systems) and file and printer sharing enabled. If you want simple file sharing, you should disable password-protected sharing by clicking the Turn off password protected sharing button.
Disabling login for Windows Home Server: Again, if you happen to be using Windows Home Server, you can't really take advantage of simple file sharing. WHS requires user accounts, logins, and passwords. On the other hand, the annoyance of having to log in every time you connect--especially if you frequently access network shares--is bigger than you might think. You have an easy way around that, provided you know the login IDs and passwords for all the users on your network. This trick works with Windows XP, Windows Vista, and Windows 7.
First, bring up the Run box by clicking the Start menu button and typing Run. When you get the dialog box, type:
control userpasswords2
First, select the correct user account from the account list. Make sure that it's highlighted. Then uncheck the box labeled Users must enter a user name and password to use this computer.
When you click Apply, another dialog box will pop up, and you'll have to enter the user password twice. But once you've done that, you should never see a login screen again. When you boot up the PC, it will automatically boot into the account of the user whose name you specified. If that account name and password is the same one used on the Windows Home Server system, the user won't have to log in to that as well.
Note that this trick also works if you want to access another Windows system that has user accounts with passwords. If all the systems in your network have the same login and password, you can bypass the login screen but still retain some semblance of security. I don't actually recommend this approach, though: It's better to have multiple accounts with different passwords, particularly if you're using a normal Windows system as a de facto server. Just remember that you'll be limited to ten maximum connections if you do this.

Windows XP Network Troubleshooting Troubleshooting TCP/IP - Detailed Steps This article shows how to troubleshoot TCP/IP connectivity between computers on a Windows network.  If you haven’t already done so, disable XP’s Internet Connection Firewall on all local area network connections, and remove all firewall programs on the network.   Improperly configured firewalls are the most common cause of TCP/IP problems. Open a Command Prompt Window For many of these steps, you’ll be typing at the command prompt.  To open a command prompt window in Windows 2000 or XP, click Start | Run, type cmd in the box, and click OK.  To open a command prompt window in Windows 95, 98, or Me, click Start | Run, type command in the box, and click OK.  Type one command per line, and press Enter after each one to execute it.  To close the command prompt window, use the exit command. Determine the TCP/IP Settings Determine the TCP/IP settings of each computer on the local area network.  In XP, open the Network Connections folder, right click the LAN connection, and click Status | Support | Details.  For example, here are the Status and Details views for the LAN connection on an Internet Connection Sharing host. In Windows 95/98/Me, click Start | Run, type winipcfg in the box, and click OK.  Select the LAN adapter from the menu, and click More Info.  Here’s the winipcfg view for an ICS client running Windows Me. You can also see the TCP/IP settings from the command prompt.  This is especially convenient if a computer has more than one network adapter.  Use the ipconfig /all command, which is available in all versions except Windows 95.  The output from this command can be long, so it’s best to write it to a file.  Specify the file name in the command this way:    ipconfig /all >ipconfig.txt Here’s the output for a Windows XP ICS host that’s sharing its cable modem connection: Description of TCP/IP Settings Here are the TCP/IP settings that are used in network troubleshooting: IP Address – Unique address assigned to a network adapter.  A computer with multiple network adapters has an IP address for each one, and each one must be in a different subnet. Subnet Mask – Used in conjunction with the IP address to determine which subnet an adapter belongs to.  At the simplest level, communication is only possible between two network adapters when they’re in the same subnet. Default Gateway - IP address of a computer or router, on one of this computer’s local area networks, that knows how to communicate with subnets not present on this computer.  For an Internet connection, the default gateway is a router belonging to your Internet service provider, and all access to sites on the Internet goes through it.  For an ICS client, the default gateway is the ICS host.  If you use a hardware router, it serves as the default gateway. DHCP Server – If an adapter is configured to obtain an IP address automatically, this is the address of the server that provides it.  It could be your ISP, an ICS host, or a hardware router. DNS Servers – IP address of one or more Domain Name Server computers. DNS servers translate Internet names (like www.practicallynetworked.com) to their IP addresses (like 63.146.109.227). Subnets See our article on subnets for a brief description of how they work.  For more details, see this Microsoft Knowledge Base article. If two computers are supposed to be on the same subnet, but aren’t, something is wrong with the network hardware or software configuration.  This is most likely to happen when one of them receives an IP address of 169.254.x.x, which indicates that: It’s configured to obtain an IP address automatically. It couldn’t find a DHPC server on the network to make the assignment. Windows assigned it an Automatic Private IP Address. See our article on Specific Networking Problems and Their Solutions for more information. Pinging The ping command is the basic tool for testing TCP/IP connectivity.  It sends a special packet (called ICMP Echo) to a particular IP address and looks for a reply.  If everything is working right, the reply comes back.  If not, the ping times out in a few seconds.  By default, the ping command repeats the process four times.  Here’s an example of an ICS client computer pinging a Windows XP Home Edition ICS host, using the host’s IP address and its computer name. When ping fails, you’ll see one of these error messages: Request timed out - The IP address is valid, but there’s no reply from it.  If the IP address is on a local area network, the most likely cause is a firewall program blocking the ping. Unknown host or Ping request could not find host - The computer name doesn’t exist on the local area network.  Make sure that NetBIOS over TCP/IP is enabled. Destination host unreachable – The IP address isn’t on a local area network, and the default gateway can’t access it.  Either there’s no default gateway, its address is wrong, or it isn’t functioning. Pinging the Local Area Network Here is a series of ping commands to use in finding where a problem occurs on a local area network.  Run them in the order shown, and don’t go on to the next command until all of the previous commands work properly.  In this example: The computer being tested is named Winxp, with IP address 192.168.1.101. There’s another computer on the network, named Win98, with IP address 192.168.1.123 Substitute the appropriate IP addresses and computer names for your network. Command Target What Ping Failure Indicates ping 127.0.0.1 Loopback address Corrupted TCP/IP installation ping localhost Loopback name Corrupted TCP/IP installation ping 192.168.1.101 This computer’s IP address Corrupted TCP/IP installation ping winxp This computer’s name Corrupted TCP/IP installation ping 192.168.1.123 Another computer’s IP address Bad hardware or NIC driver ping win98 Another computer’s name NetBIOS name resolution failure To fix a corrupted TCP/IP Installation on Windows XP, follow the steps in this Microsoft Knowledge Base article. For Windows 95/98/Me, un-install the TCP/IP protocol in Control Panel | Network, reboot, and re-install it. If that doesn’t fix it, use this procedure on Windows 95 or 98. Pinging the Internet You can also use ping to find a problem with Internet access.  Run these commands in the order shown, and don’t go on to the next command until all of the previous commands work properly.  Use the Default Gateway and DNS Server addresses that you got from the winipcfg or ipconfig /all command. Command Target What Ping Failure Indicates ping w.x.y.z Default Gateway Default Gateway down ping w.x.y.z DNS Server DNS Server down ping w.x.y.z Web site IP address Internet service provider or web site down ping www.something.com Web site name DNS Server down or web site down