Results 1 to 5 of 5

Thread: Problem with Desktop Network Connectivity

  1. #1
    Join Date
    May 2008
    Posts
    97

    Problem with Desktop Network Connectivity

    I have a wired network problem. I have a laptop has built in LAN and works fine over this network's ethernet, but the desktop PC just gets a limited or no connectivity signal. It cannot view other computers on the network and it cannot access the internet, but says it is connected.

  2. #2
    Join Date
    Jan 2006
    Posts
    4,221

    Re: Problem with Desktop Network Connectivity

    Start > Run > cmd
    At the command prompt type "ipconfig" (no quotes)
    if you have a 169.xxx.xxx.xxx address, you're not getting to the internet
    if not, then type "ping www.google.com" if it times out, you have a problem, if not, you're getting to the internet.

  3. #3
    Join Date
    Jan 2006
    Posts
    3,792

    Re: Problem with Desktop Network Connectivity

    If your ISP has provided with IP Address, Subnet Mask, Default Gateway, DNS Addresses, then, your router should not be set to DHCP, it should be set to Static IP...Set your router's Internet Connection type to Static IP and enter the information provided by your ISP and see if that works...
    Also adjust the Wireless Settings on your router if it does not connect wirelessly...
    Open an Internet Explorer browser page on a wired computer...In the address bar type - 192.168.1.1
    Leave username blank & in password use admin in lower case...
    For Wireless Settings, please do the following : -
    Click on the Wireless tab
    -Here select manual configuration...Wireless Network mode should be mixed...
    -Provide a unique name in the Wireless Network Name (SSID) box in order to differentiate your network from your neighbours network...

  4. #4
    Join Date
    May 2008
    Posts
    2,945

    Re: Problem with Desktop Network Connectivity

    Start > Run > regedit
    File > Export Registry (backup the WHOLE REGISTRY)
    HKLM > System > Current Control Set > Services
    Delete winsock and winsock2
    Go to Network Connections and right click on your LAN connection > Properties
    Select Internet protocol TCP/IP and click Install > Protocol > Add > Have Disk > type "c:\windows\inf" in the box > Next
    Reboot computer, you should get internets

  5. #5
    Join Date
    Feb 2008
    Posts
    2,635

    Re: Problem with Desktop Network Connectivity

    Set the Radio Band to Standard-20MHz and change the Standard channel to 11-2.462GHz...Wireless SSID broadcast should be Enabled and then click on Save Settings...
    Please make a note of Wireless Network Name (SSID) as this is the Network Identifier...
    For Wireless Security : -
    Click on the Sub tab under Wireless > Wireless Security...
    Change the Wireless security mode to WEP, Encryption should be 64 bits.Leave the passphrase blank, don't type in anything...
    Under WEP Key 1 type in any 10 numbers please(numbers only and no letters eg: your 10 digit phone number) and click on save settings...
    Please make a note of WEP Key 1 as this is the Security Key for the Wireless Network...

Similar Threads

  1. Server 2003 network connectivity problem?
    By locolobo13 in forum Windows Server Help
    Replies: 5
    Last Post: 17-12-2011, 05:44 AM
  2. Desktop Manager 6.0 lost the Bluetooth Connectivity
    By Cherilyn in forum Windows Software
    Replies: 7
    Last Post: 28-09-2011, 06:07 PM
  3. Wireless desktop card no connectivity
    By MARCIA in forum Networking & Security
    Replies: 3
    Last Post: 07-08-2009, 11:28 AM
  4. Network connectivity problem
    By MACY in forum Networking & Security
    Replies: 4
    Last Post: 26-11-2008, 08:12 PM
  5. Vista Network Connectivity Problem
    By Agilent in forum Windows Vista Network
    Replies: 3
    Last Post: 05-04-2007, 01:33 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,638,213.53785 seconds with 17 queries