Posts Tagged ‘lan cable’

Fixing Compaq Presario CQ71-330ED can’t connect to wireless on 64-bit Windows 7

Thursday, January 10th, 2013

Fixing Windows 7 Wireless Compaq Presario CQ71 330ED notebook  / What makes it not to connect to wi-fi

I had to fix one Notebook Compaq CQ71-330ED which was failing connecting to a home Wireless Router. The notebook was running 64 Bit Windows 7 installed from scratch just few weeks ago. The PC could connect normally via a LAN cable to the Internet, but can't connect to the Wireless Router. I thought the issue might be due to the Wireless Router, thus checked with my laptop if I can connect to the WPA2 network with the pass key. Being able to connect from my own PC make it clear the problem is somewhere in Windows 7 (most likely the drivers). I checked in

Control Panel -> Device Manager

 

to make sure the Wireless drivers were appearing as properly installed, there all seemed fine, Wireless was detected as:

Intel (R) Centrino Wireless-N 1000

I tried playing with Wireless settings from
 

Control Panel -> Network and Internet

stopped Wireless Power Saving, as I know with some wireless devices it creates problems. Also tried settings the default wireless network support from A B G N to A B G. I tried playing with changing the Workgroup name to WORKGROUP., Disabling / Enabling the Wireless Network, checking if settings for IP obtain for IPv4 are not messed up etc., but all seemed okay and still the PC weirdly was unable to connect to Wi-fi network.

I suspected, the drivers though reporting as properly installed and working with the Wi-Fi card are the point of failure. So removed driver for Wireless card and tried re-installing.

As the model of laptop was COMPAQ Presario CQ71-330ED, I looked for this model driver, but again strangely CQ71-330ED was not among the Presario models on www.hp.com drivers section.

I improvised and dfecided to download 64 bit Wi-Fi drivers for the model which seemed to be closest to CQ71-330ED – Compaq Presario CQ71-120ED.

Install the Intel 64-bit Wireless Driver for notebook CQ71-120ED solved the Wi-Fi Router connection issues. Re-connecting once again to the WPA network just worked 🙂

A mirror of Wireless driver that worked for me . After installing the driver the Wireless was detected as:
 

Intel (R) Wifi Link BGN

 

 

Howto remote access Windows PC which is behind Vivacom ADSL (Commtrend SmartAX MT882 router) modem with VNC server

Wednesday, May 11th, 2011

I had been assigned the not easy task to make a Windows XP Pro which is located behind an ADSL modem to be remotely accessible via VNC

The Windows is connected to the Bulgarian Vivacom Intrnet provider through their ADSL service and hence there is an ADSL router modem which is configured to disallow all inbuond connections by default.

The Windows Pro PC where the VNC server was needed to be accessible did not have a real IP address (e.g. was assigned a virtual IP address by the ADSL modem.

The exact ADSL model used to connect the computer via a lan cable to the internet was Huawei SmartAX MT882

As the device is owned by Vivacom (the ex BTK tele communication company) I did not have any admin user and pass credentials for the ADSL modem to configure the ADSL router to do a port NAT forwarding of port 5800 and 5900 used by the VNC software I installed on the PC (TightVNC)

Nevertheless the missing user and password I decided to check in google if I can find some default passwords that Vivacom ADSL modems are configured to work with

After a few minutes spend in Google I already had found few passwords which were said to work fine with the Vivacom ADSL router.
Here are the passwords I found for the Vivacom ADSL Internet modems:

ZTE ZXDSL 832
username: root
password:GSrootaccess

ZTE ZXDSL 831
username:root
password:GSrootaccess

ZTE
username:root
password:831access

Huawei SmartAX MT882
username:root
password:MT882rootaccess

ZTE ZXDSL-531b
username: root
password:warmWLspot

I tried some old school brute force techniques 😉 by trying all the passwords via the ADSL web interface located on http://192.168.1.1 (I was not sure which model the Vivacom ADSL modem is as on the router there was nothing written concerning the modem type but only the Vivacom logo was present.

After a bit of time I already knew that the ADSL modem model, user and pass was:

Huawei SmartAX MT882
-------------------------------
user: root
pass: MT882rootaccess

My next step was to configure port forwarding for the SmartAX MT882 ADSL in order to achieve from modem’s web administrator I had to follow the menus:

Advanced Setup -> Virtual Servers

ADSL virtual servers menu screen

Next in the NAT — Virtual Servers section I pressed the Add button to create new automatic redirection (port forwarding) rule.

Virtual Server port forwarding screenConfiguring ADSL SmartAX MT882 TightVNC NAT port redirection screenTightVNC requires also NAT port redirection rule for port 5900 in order to be able to connect to the VNC server behind the dsl, so analogically I added a Virtual Server NAT rule for port 5900.

Note that the private IP address of the Windows host was assigned by the ADSL router to the ip 192.168.1.3

Further on I expected the adsl port forwarding created rule would now allow me to connect to the VNC server on the pc located behind the dsl firewall, but I was wrong… even though all seemed to be configured just fine in the ADSL router still the port unmbers 5800 and 5900 were showing up as closed during nmap scan as well as a simple telnet connection to port 5800 and 5900 failed to get established.

My logical assumption was that some configured Firewall on the Windows PC is blocking port connections to 5800 and 5900 thus I decided to check the default Windows Firewall settings as a first possible cause for the vnc ports being blocked.

I did that via the Windows menus:

Start -> Settings -> Control Panel -> Windows Firewall

However weirly enought it seemed the Windows Firewall was disabled e.g. the Off (not recommended) option was set for the firewall.

A bunch of other lookup over all the running system and services on the windows hosts I have found the PC is protected by NOD32 Antivirus – Personal Firewall

The default behaviour of NOD32’s Persnal firewall was extremely restrictive and I found it’s causing a port filter of the 5800 and 5900 vnc connection ports.

To solve the filtering nod32 did I had to open NOD32 and navigate to the following menus:

Setup -> Personal Firewall -> Configure rules and Zones

In the Zone and rule setup menu config window I had to further press on:
New button to add new personal firewall rule.

In the New rule: menu I filled in the following info:
In the General tab:

Name: vnc
Direction: Both
Action: Allow

In the tab Local

I pressed over the Add Port

Number: 5800

in the Remote tab once again I had to fill in:
Number: 5800

Then to confirm settings just pressed OK

Next on I added in the same manner an allow rule for port 5900.

After this settings I restarted the NOD32 firewall to make sure the new settings takes place by pressing over the Personal firewall button Disable filtering: allow all traffic and right after enabling the firewall once again.

Now remote tightvnc connections to the Windows XP Pro pc works like a charm once again, Thanks God 😉