Router--Router--Internet setup not working....

Discussion in 'Computer Support' started by BigAl.NZ@gmail.com, Sep 16, 2007.

  1. Guest

    Hi Folks,

    Hoping that someone here could please help.

    I am trying to help a friend setup a home network. They connect to the
    internet via a Belkin ADSL Modem which has a single ethernet port at
    the back. I suppose you could call it a Single port router.

    They got given a D-Link 4 port router with wifi (DI-524 from memory),
    and this now sits between the PC (WinXP SP2) and the the Belkin ADSL
    modem. They also have a laptop which connects via the wifi (Vista).

    The internet appears to work intermittently, it will go for varying
    lengths of time before you start to receive page cannot be displayed.

    I have done the most basic of diagnosing when the connection went
    down:

    1. Could ping the D-Link on 192.168.0.1
    2. Could ping the Belkin on 10.1.1.1
    3. Could not ping a website, using the dns name or the IP (so it would
    appear not to be a DNS issuse)
    4. IPCONFIG showed the PC having a IP assigned

    Pictorially, the wired PC setup looks like:

    <PC>----<D-Link router/wifi>----<Belkin>----<Internet>

    I think (will have to confirm this) that when the internet stops
    working, I can plug the Belkin directly into the PC and it will work
    again, so it appears to be some sort of issue between the Belkin and
    the D-Link?

    What other testing can I do?

    Thanks in advance,

    -Al
    , Sep 16, 2007
    #1
    1. Advertising

  2. R. McCarty Guest

    You need to login to the ADSL modem and set it's operational mode
    to "Bridging". Then use the Router to select PPPOE and provide the
    master account Username/Password of your ISP to login. As it stands
    now you're using a double NAT (Network Address Translation) setup.

    <> wrote in message
    news:...
    > Hi Folks,
    >
    > Hoping that someone here could please help.
    >
    > I am trying to help a friend setup a home network. They connect to the
    > internet via a Belkin ADSL Modem which has a single ethernet port at
    > the back. I suppose you could call it a Single port router.
    >
    > They got given a D-Link 4 port router with wifi (DI-524 from memory),
    > and this now sits between the PC (WinXP SP2) and the the Belkin ADSL
    > modem. They also have a laptop which connects via the wifi (Vista).
    >
    > The internet appears to work intermittently, it will go for varying
    > lengths of time before you start to receive page cannot be displayed.
    >
    > I have done the most basic of diagnosing when the connection went
    > down:
    >
    > 1. Could ping the D-Link on 192.168.0.1
    > 2. Could ping the Belkin on 10.1.1.1
    > 3. Could not ping a website, using the dns name or the IP (so it would
    > appear not to be a DNS issuse)
    > 4. IPCONFIG showed the PC having a IP assigned
    >
    > Pictorially, the wired PC setup looks like:
    >
    > <PC>----<D-Link router/wifi>----<Belkin>----<Internet>
    >
    > I think (will have to confirm this) that when the internet stops
    > working, I can plug the Belkin directly into the PC and it will work
    > again, so it appears to be some sort of issue between the Belkin and
    > the D-Link?
    >
    > What other testing can I do?
    >
    > Thanks in advance,
    >
    > -Al
    >
    R. McCarty, Sep 16, 2007
    #2
    1. Advertising

  3. why? Guest

    On Sun, 16 Sep 2007 13:02:32 -0700, wrote:

    x-post cut to 24HSHD from

    comp.protocols.tcp-ip,alt.internet.wireless,24hoursupport.helpdesk,microsoft.public.windowsxp.general

    This is not a comp.protocols.tcp-ip issue, that ng is for the
    discussion of TCP/IP protocol if you browsed the ng you would know that.
    TCP/IP is working anyway.

    Not really a wireless issue either, you can't get connected with the
    modem and router, leave wireless out of it for now.

    Nor XP, either, and nothing fits 24hsd just fine.

    >Hi Folks,
    >
    >Hoping that someone here could please help.
    >
    >I am trying to help a friend setup a home network. They connect to the
    >internet via a Belkin ADSL Modem which has a single ethernet port at
    >the back. I suppose you could call it a Single port router.


    How so, assuming it's a router?

    It's possible to have an ADSL modem connected to a router or both built
    in to 1 box. You didn't specify the model.

    >They got given a D-Link 4 port router with wifi (DI-524 from memory),


    Okay that's a router.

    So you don't have this setup then

    Belkin modem (single port router) connected to the DI-524 router?

    Spot the 2 router issue.

    >and this now sits between the PC (WinXP SP2) and the the Belkin ADSL
    >modem. They also have a laptop which connects via the wifi (Vista).


    Test setup Belkin ADSL modem + 1 PC only.

    >The internet appears to work intermittently, it will go for varying


    What part of it?

    When it's working do a few traceroutes, to a couple of the IP devices
    like web or ftp or mail server.


    >lengths of time before you start to receive page cannot be displayed.


    When you get a vrowser issue, repeat the same test and compare.

    The internet is faulty or the web browser which may or may not use a
    proxy server that's used?

    What about mail , usenet, ftp?

    >I have done the most basic of diagnosing when the connection went
    >down:


    No, most basic is minimum kit ADSL modem + 1PC.

    >1. Could ping the D-Link on 192.168.0.1
    >2. Could ping the Belkin on 10.1.1.1


    Assuming 10.1.1.1 is the ISP side of the Belkin, and 192.168.0.1 is the
    inside IP of the D-Link.

    Traceroute to the next hop, i.e. the ISP 1st device not someting on the
    internet, since it's broken.


    >3. Could not ping a website, using the dns name or the IP (so it would
    >appear not to be a DNS issuse)


    Unless it's pointing to a server that can't be reached.

    >4. IPCONFIG showed the PC having a IP assigned


    Why forget to mention the PC IP? It will be 192.168.0.2 possibly.

    The rest of

    ipconfig /all

    output affects step 3.

    The DNS server in ipconfig /all on the PC where it isn't working may be
    in the 10 or 192.168 range, this may be a clue it's being assigned okay.

    It will tell you which device the query to isn't responding, just in
    case.

    >Pictorially, the wired PC setup looks like:
    >
    ><PC>----<D-Link router/wifi>----<Belkin>----<Internet>
    >
    >I think (will have to confirm this) that when the internet stops
    >working, I can plug the Belkin directly into the PC and it will work


    Connect to the belkin settings page and note all the ISP settings.

    >again, so it appears to be some sort of issue between the Belkin and


    So you waited until the end to mention this :)

    >the D-Link?
    >
    >What other testing can I do?
    >
    >Thanks in advance,


    Checking it's not 2 routers.

    Recording the settings when it's working and compare to those when it's
    not working.

    Me
    why?, Sep 16, 2007
    #3
  4. Elmo Guest

    wrote:
    > Hi Folks,
    >
    > Hoping that someone here could please help.
    >
    > I am trying to help a friend setup a home network. They connect to the
    > internet via a Belkin ADSL Modem which has a single ethernet port at
    > the back. I suppose you could call it a Single port router.
    >
    > They got given a D-Link 4 port router with wifi (DI-524 from memory),
    > and this now sits between the PC (WinXP SP2) and the the Belkin ADSL
    > modem. They also have a laptop which connects via the wifi (Vista).
    >
    > The internet appears to work intermittently, it will go for varying
    > lengths of time before you start to receive page cannot be displayed.
    >
    > I have done the most basic of diagnosing when the connection went
    > down:
    >
    > 1. Could ping the D-Link on 192.168.0.1
    > 2. Could ping the Belkin on 10.1.1.1
    > 3. Could not ping a website, using the dns name or the IP (so it would
    > appear not to be a DNS issuse)
    > 4. IPCONFIG showed the PC having a IP assigned
    >
    > Pictorially, the wired PC setup looks like:
    >
    > <PC>----<D-Link router/wifi>----<Belkin>----<Internet>
    >
    > I think (will have to confirm this) that when the internet stops
    > working, I can plug the Belkin directly into the PC and it will work
    > again, so it appears to be some sort of issue between the Belkin and
    > the D-Link?
    >
    > What other testing can I do?
    >
    > Thanks in advance,
    >
    > -Al


    Open Device Manager, open the properties on your ethernet card, click
    the Power tab, and deselect "Allow the computer to turn off this device
    to save power". If it's a USB port rather than an ethernet or NIC, make
    the same change to all the USB ports.

    --
    Joe =o)
    Elmo, Sep 17, 2007
    #4
  5. Guest

    R. McCarty wrote:
    > You need to login to the ADSL modem and set it's operational mode
    > to "Bridging". Then use the Router to select PPPOE and provide the
    > master account Username/Password of your ISP to login. As it stands
    > now you're using a double NAT (Network Address Translation) setup.


    We use PPPoATM in NZ - does that matter?
    , Sep 17, 2007
    #5
  6. Guest

    Okay,

    I have a lot more information.

    1. The Belkin is a F5D5730au
    2. When I was with the two computers this afternoon, it was not
    working on either computer, so I unplugged the Belkin from the Dlink
    and connected straight to the PC - it then worked on the PC.
    3. After reconnecting the PC --> Dlink --> Belkin both computers had
    internet access....
    4. Some screen (sorry about the res) at :
    BELKIN
    http://img241.imageshack.us/img241/8255/belkinpg1sl8.jpg
    http://img101.imageshack.us/img101/6769/belkinpg21wq3.jpg
    http://img205.imageshack.us/img205/864/belkinpg22ax2.jpg
    http://img241.imageshack.us/img241/784/belkinpg31ib7.jpg
    http://img241.imageshack.us/my.php?image=belkinpg41tz6.jpg
    http://img205.imageshack.us/my.php?image=belkinpg51dj7.jpg

    D-Link
    http://img101.imageshack.us/my.php?image=dlinkpg1ss6.jpg
    http://img241.imageshack.us/my.php?image=dlinkdhcplanns2.jpg


    Logs from D-Link below - hope this helps?


    *********** Printout of D-Link System Logs ****************
    -------------------------------------------------
    System Logs
    -------------------------------------------------
    Fri Sep 14 17:59:50 2007 Associated: 00-19-7E-98-62-E1 st=0
    Fri Sep 14 17:59:54 2007 DOD:triggered internally
    Fri Sep 14 17:59:54 2007 DHCP:discover(zeeman)
    Fri Sep 14 17:59:54 2007 DHCP:eek:ffer(10.1.1.1)
    Fri Sep 14 17:59:54 2007 DHCP:request(10.1.1.2)
    Fri Sep 14 17:59:54 2007
    DHCP:ack(DOL=4294967295,T1=2147483647,T2=3758096384)
    Fri Sep 14 18:17:13 2007 Connection is broken
    Fri Sep 14 18:17:13 2007 DHCP:release
    Fri Sep 14 18:17:15 2007 DOD:192.168.0.187 query DNS for
    teredo.ipv6.microsoft.com
    Fri Sep 14 18:17:15 2007 DHCP:discover(zeeman)
    Fri Sep 14 18:17:19 2007 DHCP:discover(zeeman)
    Fri Sep 14 18:17:27 2007 DHCP:discover(zeeman)
    Fri Sep 14 18:17:43 2007 DHCP:discover(zeeman)
    Fri Sep 14 18:20:38 2007 DOD:192.168.0.187 query DNS for
    dns.msftncsi.com
    Fri Sep 14 18:20:38 2007 DHCP:discover(zeeman)
    Fri Sep 14 18:20:42 2007 DHCP:discover(zeeman)
    Fri Sep 14 18:20:44 2007 DHCP:eek:ffer(10.1.1.1)
    Fri Sep 14 18:20:44 2007 DHCP:request(10.1.1.2)
    Fri Sep 14 18:20:46 2007
    DHCP:ack(DOL=4294967295,T1=2147483647,T2=3758096384)
    Fri Sep 14 18:20:53 2007 Syn time: Fri Sep 14 18:20:57 2007
    Fri Sep 14 18:36:08 2007 Disassociated: 00-19-7E-98-62-E1
    Fri Sep 14 22:36:19 2007 Associated: 00-19-7E-98-62-E1 st=0
    Fri Sep 14 22:38:41 2007 Disassociated: 00-19-7E-98-62-E1
    Sat Sep 15 09:51:13 2007 Associated: 00-19-7E-98-62-E1 st=0
    Sat Sep 15 10:27:32 2007 Disassociated: 00-19-7E-98-62-E1
    Sun Sep 16 19:15:30 2007 Associated: 00-19-7E-98-62-E1 st=0
    Sun Sep 16 23:01:09 2007 Disassociated: 00-19-7E-98-62-E1
    Mon Sep 17 17:20:01 2007 Associated: 00-19-7E-98-62-E1 st=0
    Mon Sep 17 17:24:29 2007 Connection is broken
    Mon Sep 17 17:24:29 2007 DHCP:release
    Mon Sep 17 17:24:46 2007 DOD:192.168.0.187 query DNS for
    teredo.ipv6.microsoft.com
    Mon Sep 17 17:24:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:24:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:24:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:25:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:25:46 2007 DOD:triggered internally
    Mon Sep 17 17:25:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:25:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:25:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:26:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:26:46 2007 DOD:triggered internally
    Mon Sep 17 17:26:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:26:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:26:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:27:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:27:46 2007 DOD:triggered internally
    Mon Sep 17 17:27:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:27:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:27:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:28:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:28:46 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:28:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:28:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:28:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:29:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:29:46 2007 DOD:triggered internally
    Mon Sep 17 17:29:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:29:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:29:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:30:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:30:46 2007 DOD:triggered internally
    Mon Sep 17 17:30:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:30:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:30:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:31:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:31:46 2007 DOD:triggered internally
    Mon Sep 17 17:31:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:31:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:31:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:32:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:32:46 2007 DOD:triggered internally
    Mon Sep 17 17:32:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:32:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:32:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:33:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:33:46 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:33:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:33:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:33:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:34:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:34:46 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:34:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:34:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:34:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:35:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:35:46 2007 DOD:triggered internally
    Mon Sep 17 17:35:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:35:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:35:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:36:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:36:46 2007 DOD:triggered internally
    Mon Sep 17 17:36:46 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:36:50 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:36:58 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:37:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:41:13 2007 DOD:192.168.0.187 query DNS for www.symantec.com
    Mon Sep 17 17:41:13 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:41:17 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:41:25 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:41:41 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:42:14 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:42:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:42:18 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:42:26 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:42:42 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:43:14 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:43:14 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:43:18 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:43:26 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:43:42 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:44:15 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:44:15 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:44:19 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:44:27 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:44:43 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:45:15 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:45:15 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:45:19 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:45:27 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:45:43 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:46:15 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:46:15 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:46:19 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:46:27 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:46:43 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:47:15 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:47:15 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:47:19 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:47:27 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:47:43 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:48:15 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:48:15 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:48:19 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:48:27 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:48:43 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:49:15 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:49:15 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:49:19 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:49:27 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:49:43 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:50:15 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:50:15 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:50:19 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:50:27 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:50:43 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:51:15 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:51:15 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:51:19 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:51:27 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:51:43 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:52:15 2007 DOD:192.168.0.187 query DNS for wpad
    Mon Sep 17 17:52:15 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:52:19 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:52:27 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:52:43 2007 DHCP:discover(zeeman)
    Mon Sep 17 17:53:00 2007 Disassociated: 00-19-7E-98-62-E1
    Mon Sep 17 18:06:45 2007 DOD:192.168.0.146 query DNS for www.microsoft.com
    Mon Sep 17 18:06:45 2007 DHCP:discover(zeeman)
    Mon Sep 17 18:06:45 2007 DHCP:eek:ffer(10.1.1.1)
    Mon Sep 17 18:06:45 2007 DHCP:request(10.1.1.2)
    Mon Sep 17 18:06:45 2007
    DHCP:ack(DOL=4294967295,T1=2147483647,T2=3758096384)
    Mon Sep 17 18:06:46 2007 Syn time: Mon Sep 17 18:06:46 2007
    Mon Sep 17 18:07:00 2007 Associated: 00-19-7E-98-62-E1 st=0
    , Sep 17, 2007
    #6
  7. Guest

    Oh and autoreconnect on the WAN page of the Dlink was disabled, so I
    enabled it.

    -Al
    , Sep 17, 2007
    #7
  8. Guest

    On Sep 17, 7:32 pm, wrote:
    > Oh and autoreconnect on the WAN page of the Dlink was disabled, so I
    > enabled it.
    >
    > -Al


    The internet connection was lost again tonight.

    I tried a tracert and got a reply from 192.168.0.1 and 10.1.1.1 but
    nothing after that....

    -Al
    , Sep 18, 2007
    #8
  9. Peter Pan Guest

    wrote:
    > On Sep 17, 7:32 pm, wrote:
    >> Oh and autoreconnect on the WAN page of the Dlink was disabled, so I
    >> enabled it.
    >>
    >> -Al

    >
    > The internet connection was lost again tonight.
    >
    > I tried a tracert and got a reply from 192.168.0.1 and 10.1.1.1 but
    > nothing after that....
    >
    > -Al


    Just out of curiosity, what happens if you unplug/replug the wap (not the
    cable/dsl modem)? I used to have that at my old house (something wierd about
    the power), and got one of those lamp timers to turn it off/backon at odd
    hours of the day
    Peter Pan, Sep 19, 2007
    #9
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. =?Utf-8?B?RHJhZ29ueA==?=

    wifi not working on new hp, or not working after live update

    =?Utf-8?B?RHJhZ29ueA==?=, Oct 2, 2005, in forum: Wireless Networking
    Replies:
    1
    Views:
    914
    =?Utf-8?B?RHJhZ29ueA==?=
    Oct 2, 2005
  2. MICHAEL SMITH

    Internet Browser (Internet Explorer) Not Working

    MICHAEL SMITH, Apr 21, 2006, in forum: Computer Support
    Replies:
    12
    Views:
    638
    neville
    Apr 22, 2006
  3. Paul Welch

    AOL working, Internet Explorer not working

    Paul Welch, Aug 12, 2006, in forum: Computer Support
    Replies:
    3
    Views:
    3,755
    Thoronwen
    Aug 13, 2006
  4. STAN1ZX

    Wired ethernet not working after wireless setup

    STAN1ZX, Sep 25, 2007, in forum: Wireless Networking
    Replies:
    4
    Views:
    672
    Phillip Windell
    Sep 26, 2007
  5. pcprince1987

    security setup wizaed not working please help

    pcprince1987, Sep 2, 2008, in forum: General Computer Support
    Replies:
    0
    Views:
    755
    pcprince1987
    Sep 2, 2008
Loading...

Share This Page