1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

New network: Wireless working, Wired not working

Discussion in 'Networking Issues' started by Davestar, Jan 11, 2007.

  1. Davestar

    Davestar LI Guru Member

    Hi, I hope someone here can help me. My scenario is this:

    I just connected a WAG354G (V.2) and connected it to the NIC on my main PC running Windows 2000 Pro and it worked fine, I set up my ADSL connection on it fine as well.

    I then installed a Linksys wireless NIC in my secondary PC running Windows XP and it connected immediately and worked fine as well.

    To set them up, I just went through what is said in the quick start guides.

    But after I restarted my main PC, it hasn't been able to reach the gateways admin page and can barely load a single Internet page although it seems to be able to get them eventually!

    The wireless PC is still working flawlessly however and can access the router settings page.

    I've no idea why or how this is happening, I really need the Internet at an acceptable speed on that machine. Can anyone help me find out why it is doing this? and help me resolve it?

    Thanks.
     
  2. Esquire

    Esquire Mesquire Staff Member Member

    Can you post the results of your IPCONFIG?
    (masking any external/Internet/WAN IP if applicable)

    Start > Run
    Load: CMD
    At the Command Prompt, execute: IPCONFIG/ALL
     
  3. Davestar

    Davestar LI Guru Member

    Hi, here it is:

    From my wireless PC:

    Windows IP Configuration
    Host Name . . . . . . . . . . . . : FAMILY
    Primary Dns Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Unknown
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Wireless Network Connection:
    Connection-specific DNS Suffix . : domain_not_set.invalid
    Description . . . . . . . . . . . : Linksys Wireless-G PCI Adapter
    Physical Address. . . . . . . . . : 00-18-F8-30-76-0B
    Dhcp Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IP Address. . . . . . . . . . . . : 192.168.1.65
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : 62.24.128.18
    62.24.128.17
    192.168.1.1
    Lease Obtained. . . . . . . . . . : 11 January 2007 21:36:29
    Lease Expires . . . . . . . . . . : 12 January 2007 21:36:29

    And here it is from my wired PC:

    Windows 2000 IP Configuration
    Host Name . . . . . . . . . . . . : Skynet
    Primary DNS Suffix . . . . . . . :
    Node Type . . . . . . . . . . . . : Hybrid
    IP Routing Enabled. . . . . . . . : No
    WINS Proxy Enabled. . . . . . . . : No
    DNS Suffix Search List. . . . . . : domain_not_set.invalid

    Ethernet adapter Local Area Connection:
    Connection-specific DNS Suffix . : domain_not_set.invalid
    Description . . . . . . . . . . . : NVIDIA nForce MCP Networking Controller
    Physical Address. . . . . . . . . : 00-0C-76-C3-1B-1F
    DHCP Enabled. . . . . . . . . . . : Yes
    Autoconfiguration Enabled . . . . : Yes
    IP Address. . . . . . . . . . . . : 192.168.1.64
    Subnet Mask . . . . . . . . . . . : 255.255.255.0
    Default Gateway . . . . . . . . . : 192.168.1.1
    DHCP Server . . . . . . . . . . . : 192.168.1.1
    DNS Servers . . . . . . . . . . . : 62.24.128.18
    62.24.128.17
    192.168.1.1
    Lease Obtained. . . . . . . . . . : 10 January 2007 22:18:52
    Lease Expires . . . . . . . . . . : 11 January 2007 22:18:52
     
  4. GeeTek

    GeeTek Guest

    What is the condition of the cat5 patch cable from the PC to the Router ? Are the ends good and solid and plugged in well ? Try a ping loop to the DNS server from the laptop and then from the PC. From a DOS prompt type
    c:> ping 62.24.127.18 -t
    which will show the return delay times and possible time-outs. Compare the results from the 2 computers. Wiggle the cables and stuff on the PC while the loop is running to see what may happen. If everything looks normal and consistent then dis-able any 3rd party software firewall unless you have open ports on your router.
     
  5. Davestar

    Davestar LI Guru Member

    Nope cable seems to be fine and is brand new, it is pinging okay, exactly the same as the wireless machine. I disabled the firewall on both PCs and still no difference.

    I've desperately tried to look for a difference between the two, do you think it could be some kind of conflict between Windows XP and Windows 2000? I notice the Win XP has extra items in the Network Connection Settings like QoS Packet Scheduler and AEGIS Protocol.

    I'm really stuck for ideas here? Hope someone can think of something, when I startup my Win 2000 PC it automatically pops up and connects to the LAN. Is there someway of resetting the NIC and any settings put on it? The only thing I can see to do is hit disable but then it needs enabled again, whereas before it never had any entry for LAN in the Dial Up Networking.
     
  6. GeeTek

    GeeTek Guest

    So it is the Windows 2000 machine with the regular NIC that is slow ? Has it ever been fast with that card ?
     
  7. Davestar

    Davestar LI Guru Member

    Yes. When I first set it up it was working normally i.e. fast.
     
  8. GeeTek

    GeeTek Guest

    Connect the fast computer to the LAN port and see if it goes slow also. If not, re-install / replace the NIC on the slow computer. Automatic software updates can cause that symptom as well if they are big and you are not aware of them going on. If the NIC is good, TCPOptimizer.exe can sometimes repair corruption in the TCP timings by over-writing with correct values.
     
  9. Esquire

    Esquire Mesquire Staff Member Member

    Connection-specific DNS Suffix . : domain_not_set.invalid

    This doesn't look like the default configuration response. Are you using the default DNS settings in your TCP/IP?

    [​IMG]
     

Share This Page