• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5449
  • Last Modified:

Win2K Wireless Lan Setup

I have a Toshiba Portege 4000 laptop with built in WIFI card and just purchased new DLink wireless router and ADSL hub.  I can get the desktop machine working on the workgroup fine, connect to the internet, ping the router etc... all fine using the built in DHCP in the router. The laptop says I have EXCELLENT Wifi connection but am unable to ping ANYTHING, when I use IPCONFIG it says the Wireless LAN connection DOES NOT have IP address, also says Wireless network cable is unplugged.

Have tried anything and everything, even assigning IP address by hand but cant seem to get through to the router at all, have opening up all necessary ports and turned off the router firewall, also allowed ICMP to work etc etc  I can ping localhost from the laptop so know TCPIP is working properly just seem to be unable to "attach" the TCP to the wireless LAN card and hence use internet / local LAN.

I am ready to throw everything out the window! Please help!
1 Solution
Disable all the firewall if any

Go to the web management of the router and check the SSID and channel are set the same in router and wifi card

go to status in web management of router and check to see if there is a button for connection or connecting.click on that

Make sure you have setup the router the correct way

Restart the machine and try

John Gates, CISSPSecurity ProfessionalCommented:
Make sure that you don't have any WEP enabled also for testing (Just until you establish connectivity)

Okay I will assume that you haven't set the wireless up correctly, so here's a brief tutorial on how to do it. Despite having an "excellent connection", that doesn't mean your wireless is correctly configured from a network perspective.

Firstly, your wireless access point must have an IP, unless it is a transparent bridge, but even then I would think it would still have an IP address. Oh and just for the sake of completeness, ensure that both your AP and laptop are using the 802.11b protocol.


Disable all firewalls just for testing.
Set your wireless AP to have a LAN IP.
Select a channel for your AP and an SSID. Use the same on your laptop wifi card.
You both will need your own UNIQUE "wireless network name".
Make sure that your laptop wifi card is set to be in wireless client mode. Yeah I know it will be but just check.
Now, assign your laptop an IP address on the same network as the AP. That means for example, the wireless AP could have and your laptop could have I don't think that the wifi card will require an IP address. If it does, place it on the same network, say
Disable WEP for the sake of testing.

You should now be within range, and if you are you should still have excellent signal strength. Try to ping your local IP and then the wireless AP. I would be suprised if it doesn't work.

Hope this helps.


Restore individual SQL databases with ease

Veeam Explorer for Microsoft SQL Server delivers an easy-to-use, wizard-driven interface for restoring your databases from a backup. No expert SQL background required. Web interface provides a complete view of all available SQL databases to simplify the recovery of lost database

alexcnAuthor Commented:
Thanks for comments thusfar, my first question on here so hope I pull this off correctly.  Anyway, in terms of further info in response to your kind suggestions:

1) Have tried with WEP disabled / enabled and all firewalls on desktop shutdown.  Laptop DOES NOT have any firewall software installed whatsoever.
2) D-Link DI-624 router has DCHP installed which works fine for desktop, IPCONFIG /ALL in laptop says no IP address assigned to internal Wifi card.  Tried setting an IP address manually, on either and both machines but still nothing on the TCP over Wifi.
3) DCHP on router set to allocated IP's in range thru .199.  Desktop correctly picks up, have set laptop manually to on previous attempts.  Router is set to (D-Link this morning suggested using for the router IP address, and keep for the D-Link ADSL modem instead but it should still work)
3) Can ping the localhost AND on laptop which, I think, would indicate that TCPIP is installed properly and DNS is being resolved? Yes?
4) Use the same network name (workgroup name as opposed to domain name?) on both machines.
5) Web-based management tool of D-Link DI-624 router says in Wireless Status page that laptop is connected.
6) Strange occurence that Network / LAN connection icon next to the clock (i.e. the two little monitor screens) has a red X against it, and hovering over the mouse brings up popup saying "Cable Disconnected"
7) Have even tried plugging the other network card in the laptop into the router directly, and that works fine!

Its almost like the wireless connection is there, but the laptop does not see using TCPIP and hence the workgroup network over the wireless part as being an option, and has left me wondering if there is a software switch somewhere to turn this bit on?

I just downloaded Laptop manual from Toshiba's website and am wondering if the setup of the profile as being of type "Access Point" for an enterprise network verses "Peer-to-Peer Group" for a workgroup is the reason? Am I right in thinking the AP is in terms of when a Domain Controller is in existence on the work?

I really appreciate your help and support!
Um, okay, your wireless in the laptop CANNOT be in Access Point mode. I didn't know it was possible for that. Your laptop's wireless component needs to be in a client mode. Try the peer-to-peer and using my instructions above.

Let me know how it goes.

John Gates, CISSPSecurity ProfessionalCommented:
The differences are Ad-Hoc (No AP just card to card) and infrastructure (With an AP) Your clients should be set up as Infrastructure.

Featured Post

Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now