Network issues

Discussion in 'Computer Support' started by westnilebassist@aol.com, Mar 20, 2007.

  1. Guest

    I have two computers on a small office network and the newest computer
    on the network can not read the original computer. Both desktops are
    dell computers and have not had any major technical changes on them. I
    use Verizon DSL with a 3COM Office Connect router with Windows XP
    SP2. This is not a minor issue such as a connection problem. I have
    had a computer tech in and his words were, "I think it might be a
    routing table." We still have not figured this out and I was wondering
    if there is any one who could help me!
    , Mar 20, 2007
    #1
    1. Advertising

  2. Mike Easter Guest

    wrote:
    > I have two computers on a small office network and the newest computer
    > on the network can not read the original computer. Both desktops are
    > dell computers and have not had any major technical changes on them. I
    > use Verizon DSL with a 3COM Office Connect router with Windows XP
    > SP2. This is not a minor issue such as a connection problem. I have
    > had a computer tech in and his words were, "I think it might be a
    > routing table." We still have not figured this out and I was wondering
    > if there is any one who could help me!


    Here is 3com's page of officeconnect routers
    http://www.3com.com/products/en_US/...chase&cat=152882&selcat=Routers&family=175073
    or http://snipurl.com/1dire

    You can find your product in there. I think they can all/each be
    configured with your browser. I'm sure the router came with a CD
    manual.

    I doubt if any special routing table was configured by default,
    typically the router has the default subnetmask. Did you pay the
    'computer tech' to come in and make remarks or was that what he said
    when he decided to not charge you because he didn't know about network
    troubleshooting?


    --
    Mike Easter
    Mike Easter, Mar 20, 2007
    #2
    1. Advertising

  3. why? Guest

    On 20 Mar 2007 11:01:23 -0700, wrote:

    >I have two computers on a small office network and the newest computer
    >on the network can not read the original computer. Both desktops are
    >dell computers and have not had any major technical changes on them. I


    You can either answer or just consider the questions. It's much easier
    to fix this sort of thing when actually in fromt of the kit.

    Or at least get the ISP settings, check the router settings, PC IP
    values and results of the ping test.

    So it was working before minor changes?

    You also didn't say what the problem really was, is it any of the PC to
    the ISP / email , internet or filesharing between the PCs?

    >use Verizon DSL with a 3COM Office Connect router with Windows XP


    The DSL box is the modem ISP part of the setup? This is connecting to
    the 3Com OC router. How about, the model of the router?

    Connect only 1 PC without the router, this should get the (if configured
    for DHCP) default ISP settings or do you have static IP addresses.

    If it's DHCP then use ipconfig/all from a CMD prompt shell and note down
    the IP address, gateway, subnet mask , any DNS servers.

    While still in the CMS shell,

    route print

    will show you the XP routing table, it's really simple :

    local PC and loop back addresses and a couple of entries for the ISP,
    i.e. how to get to network X via gateway A at IP address B.



    If both PC are connected to the router it may be it allocates the IP
    address settings. This may be an IP of something like 192.168.0.2 and
    0.3. The subnet mask may be 255.255.255.0 and the DNS is either the
    router 192.168.0.1 or it passes through the ISP settings to the PCs.

    At this point the router WAN port connected to the DSL box (no make /
    model given either) is your ISP settings, you should be able to confirm
    this via the webpage / settings of the router.

    >SP2. This is not a minor issue such as a connection problem. I have


    Ah but it usually is :), how do you know anyway? Guessing you already
    tried some tests but you didn't say.

    That's both PCs XP SP2?

    When the PCs are connected to the router, if you do the ipconfig/all for
    both PCs do the settings look okay i.e. the same except for the IP
    address.

    Can you ping the PCs from each other , ping the router?

    >had a computer tech in and his words were, "I think it might be a
    >routing table." We still have not figured this out and I was wondering


    Oh dear that one....

    >if there is any one who could help me!


    Me
    why?, Mar 20, 2007
    #3
  4. Guest

    On Mar 20, 1:29 pm, "Mike Easter" <> wrote:
    > wrote:
    > > I have two computers on a small office network and the newest computer
    > > on the network can not read the original computer. Both desktops are
    > > dell computers and have not had any major technical changes on them. I
    > > use Verizon DSL with a 3COM Office Connect router with Windows XP
    > > SP2. This is not a minor issue such as a connection problem. I have
    > > had a computer tech in and his words were, "I think it might be a
    > > routing table." We still have not figured this out and I was wondering
    > > if there is any one who could help me!

    >
    > Here is 3com's page of officeconnect routershttp://www.3com.com/products/en_US/prodlist.jsp?tab=cat&pathtype=purc...
    > or http://snipurl.com/1dire
    >
    > You can find your product in there. I think they can all/each be
    > configured with your browser. I'm sure the router came with a CD
    > manual.
    >
    > I doubt if any special routing table was configured by default,
    > typically the router has the default subnetmask. Did you pay the
    > 'computer tech' to come in and make remarks or was that what he said
    > when he decided to not charge you because he didn't know about network
    > troubleshooting?
    >
    > --
    > Mike Easter


    The tech was not being paid he is a friend of the family. As for the
    router having a manual/CD; it was given to us by the tech so it did
    not come with any of those.
    , Mar 20, 2007
    #4
  5. Mr. Arnold Guest

    wrote:
    > I have two computers on a small office network and the newest computer
    > on the network can not read the original computer. Both desktops are
    > dell computers and have not had any major technical changes on them. I
    > use Verizon DSL with a 3COM Office Connect router with Windows XP
    > SP2. This is not a minor issue such as a connection problem. I have
    > had a computer tech in and his words were, "I think it might be a
    > routing table." We still have not figured this out and I was wondering
    > if there is any one who could help me!
    >


    1) In some cases with XP and this is a computer that has never
    networked, use of a router and trying to share resources with other
    computers or see the computers on the LAN, sometimes, the protocols
    being used on the NIC(s) are flat-out not going to work for whatever
    reasons and you must change the protocols on the NIC to make things work.

    2) The router could be flaky. The firmware of the router must be
    re-initialized by doing a hard reset of the router, powering the router
    down waiting for a few seconds and powering the router back up.

    3) Sometimes, the firmware of the router has flat-out becomes sick and
    the router needs to be re-flashed/the firmware re-installed in order to
    straighten the router out.
    Mr. Arnold, Mar 20, 2007
    #5
  6. John Holmes Guest

    Mr. Arnold "contributed" in 24hoursupport.helpdesk:

    > wrote:
    >> I have two computers on a small office network and the newest computer
    >> on the network can not read the original computer. Both desktops are
    >> dell computers and have not had any major technical changes on them. I
    >> use Verizon DSL with a 3COM Office Connect router with Windows XP
    >> SP2. This is not a minor issue such as a connection problem. I have
    >> had a computer tech in and his words were, "I think it might be a
    >> routing table." We still have not figured this out and I was wondering
    >> if there is any one who could help me!
    >>

    >
    > 1) In some cases with XP and this is a computer that has never
    > networked, use of a router and trying to share resources with other
    > computers or see the computers on the LAN, sometimes, the protocols
    > being used on the NIC(s) are flat-out not going to work for whatever
    > reasons and you must change the protocols on the NIC to make things

    work.


    BWAHAHAHAHAHAHAHAHAHAAAAA!!!

    >
    > 2) The router could be flaky. The firmware of the router must be
    > re-initialized by doing a hard reset of the router, powering the router
    > down waiting for a few seconds and powering the router back up.


    BWAHAHAHAHAHAHAHAHAHAAAAA!!!

    >
    > 3) Sometimes, the firmware of the router has flat-out becomes sick and
    > the router needs to be re-flashed/the firmware re-installed in order to
    > straighten the router out.
    >


    BWAHAHAHAHAHAHAHAHAHAAAAA!!!

    <aside> You fucking idiot.

    --
    Your mother was a handsome cauliflower who opened an animal sanctuary in
    graveyards.
    John Holmes, Mar 20, 2007
    #6
  7. Shel-hed Guest

    On Tue, 20 Mar 2007 19:32:54 GMT, "Mr. Arnold" <"Mr. Arnold"@Arnold.COM> wrote:

    >>

    >
    >1) In some cases with XP and this is a computer that has never
    >networked, snip
    >2) The router could be flaky. snip
    >3) Sometimes, the firmware of the router has flat-out becomes sick snip


    And I'll add-
    4) And sometimes the manufacturer just outright lied and said that you can
    network "up to" n computers, but failed to mention that you have to unplug one
    for the other to work.

    Creative sound cards are famous for lies like this.
    Search google groops with the model number.
    Shel-hed, Mar 20, 2007
    #7
  8. Mr. Arnold Guest

    Shel-hed wrote:
    > On Tue, 20 Mar 2007 19:32:54 GMT, "Mr. Arnold" <"Mr. Arnold"@Arnold.COM> wrote:
    >
    >
    >>1) In some cases with XP and this is a computer that has never
    >>networked, snip
    >>2) The router could be flaky. snip
    >>3) Sometimes, the firmware of the router has flat-out becomes sick snip

    >
    >
    > And I'll add-
    > 4) And sometimes the manufacturer just outright lied and said that you can
    > network "up to" n computers, but failed to mention that you have to unplug one
    > for the other to work.
    >
    > Creative sound cards are famous for lies like this.
    > Search google groops with the model number.
    >


    Also, they don't tell you that the protocols being used on the NIC's
    which in some cases for a Windows XP set-up right out of the box install
    will not work when trying to network machines via a router.

    I have seen the posts too many times by users working with XP that they
    couldn't get the machines to network, but seemed to have done the setup
    of the O/S(s) properly, while using a router.

    A friend of mine faced that problem with a Linksys router and XP pro
    machines. He couldn't get the machines to network with the out of the
    box install of the protocols for XP on the NIC(s).

    I told him to change the protocols. If you can't force something to work
    in it's current state, you have to try another approach. He changed the
    protocols and was able to network the machines with the router in play.

    I had that problem on a wire/wireless router where the wire machine
    would not network with the wireless machine for Win 2k machines with
    their out of the box protocols on the NIC(s). I changed the protocols on
    the NIC(s) and was able to network the machines.
    Mr. Arnold, Mar 20, 2007
    #8
  9. Maximum Dog7 Guest

    John Whore in need of a toilet wrote:

    <snipped>

    >
    > BWAHAHAHAHAHAHAHAHAHAAAAA!!!
    > BWAHAHAHAHAHAHAHAHAHAAAAA!!!
    > BWAHAHAHAHAHAHAHAHAHAAAAA!!!


    <You do know when you fart like this, you should run to the toilet and
    take a shit, else you'll shit on yourself.>

    <If you don't know this, then you don't know to wipe too.>
    Maximum Dog7, Mar 20, 2007
    #9
  10. why? Guest

    On Tue, 20 Mar 2007 23:15:58 GMT, Mr. Arnold wrote:

    >Shel-hed wrote:
    >> On Tue, 20 Mar 2007 19:32:54 GMT, "Mr. Arnold" <"Mr. Arnold"@Arnold.COM> wrote:
    >>
    >>
    >>>1) In some cases with XP and this is a computer that has never
    >>>networked, snip
    >>>2) The router could be flaky. snip
    >>>3) Sometimes, the firmware of the router has flat-out becomes sick snip

    >>
    >>
    >> And I'll add-
    >> 4) And sometimes the manufacturer just outright lied and said that you can
    >> network "up to" n computers, but failed to mention that you have to unplug one
    >> for the other to work.
    >>
    >> Creative sound cards are famous for lies like this.
    >> Search google groops with the model number.
    >>

    >
    >Also, they don't tell you that the protocols being used on the NIC's
    >which in some cases for a Windows XP set-up right out of the box install
    >will not work when trying to network machines via a router.


    What like TCP/IP by default?

    >I have seen the posts too many times by users working with XP that they
    >couldn't get the machines to network, but seemed to have done the setup
    >of the O/S(s) properly, while using a router.
    >
    >A friend of mine faced that problem with a Linksys router and XP pro
    >machines. He couldn't get the machines to network with the out of the
    >box install of the protocols for XP on the NIC(s).


    What protocols, changed from what to which?

    <snip>

    Me
    why?, Mar 21, 2007
    #10
  11. Mr. Arnold Guest

    why? wrote:
    > On Tue, 20 Mar 2007 23:15:58 GMT, Mr. Arnold wrote:
    >
    >
    >>Shel-hed wrote:
    >>
    >>>On Tue, 20 Mar 2007 19:32:54 GMT, "Mr. Arnold" <"Mr. Arnold"@Arnold.COM> wrote:
    >>>
    >>>
    >>>
    >>>>1) In some cases with XP and this is a computer that has never
    >>>>networked, snip
    >>>>2) The router could be flaky. snip
    >>>>3) Sometimes, the firmware of the router has flat-out becomes sick snip
    >>>
    >>>
    >>>And I'll add-
    >>>4) And sometimes the manufacturer just outright lied and said that you can
    >>>network "up to" n computers, but failed to mention that you have to unplug one
    >>>for the other to work.
    >>>
    >>>Creative sound cards are famous for lies like this.
    >>>Search google groops with the model number.
    >>>

    >>
    >>Also, they don't tell you that the protocols being used on the NIC's
    >>which in some cases for a Windows XP set-up right out of the box install
    >>will not work when trying to network machines via a router.

    >
    >
    > What like TCP/IP by default?


    Of course TCP/IP has to stay. But for whatever reason, there seems to be
    an issue with XP and networking with a router sometimes.
    >
    >
    >>I have seen the posts too many times by users working with XP that they
    >>couldn't get the machines to network, but seemed to have done the setup
    >>of the O/S(s) properly, while using a router.
    >>
    >>A friend of mine faced that problem with a Linksys router and XP pro
    >>machines. He couldn't get the machines to network with the out of the
    >>box install of the protocols for XP on the NIC(s).

    >
    >
    > What protocols, changed from what to which?



    I told him to use NWlink IPX/SPX on the NIC(s). It worked for him. It
    worked for me as well when I couldn't get Win 2K machines to network
    with wire and wireless machines.

    In the case of the Win 2K machines, Netbeui had to be removed off of the
    NIC as installing MS NWlink with Netbeui, the TCP Stack was hosed when
    that happened and had to be reset.

    One can't force it to work if it don't work and another path has to be
    taken. Yes, I have heard that NWlink is an old protocol and shouldn't be
    used, although I really never was shown solid proof as to why.

    Anyway, it's there on the O/S. I and others that I have mentioned it to
    that were having issues that tried MS NWlink took the path of least
    resistance, got things to network and moved on.

    http://www.practicallynetworked.com/sharing/xp/network_protocols.htm
    Mr. Arnold, Mar 21, 2007
    #11
  12. why? Guest

    On Wed, 21 Mar 2007 18:02:07 GMT, Mr. Arnold wrote:

    >why? wrote:
    >> On Tue, 20 Mar 2007 23:15:58 GMT, Mr. Arnold wrote:
    >>
    >>
    >>>Shel-hed wrote:
    >>>
    >>>>On Tue, 20 Mar 2007 19:32:54 GMT, "Mr. Arnold" <"Mr. Arnold"@Arnold.COM> wrote:
    >>>>
    >>>>
    >>>>
    >>>>>1) In some cases with XP and this is a computer that has never
    >>>>>networked, snip
    >>>>>2) The router could be flaky. snip
    >>>>>3) Sometimes, the firmware of the router has flat-out becomes sick snip


    <snip>

    >>>Also, they don't tell you that the protocols being used on the NIC's
    >>>which in some cases for a Windows XP set-up right out of the box install
    >>>will not work when trying to network machines via a router.

    >>
    >>
    >> What like TCP/IP by default?

    >
    >Of course TCP/IP has to stay. But for whatever reason, there seems to be
    >an issue with XP and networking with a router sometimes.
    >>
    >>
    >>>I have seen the posts too many times by users working with XP that they
    >>>couldn't get the machines to network, but seemed to have done the setup
    >>>of the O/S(s) properly, while using a router.
    >>>
    >>>A friend of mine faced that problem with a Linksys router and XP pro
    >>>machines. He couldn't get the machines to network with the out of the
    >>>box install of the protocols for XP on the NIC(s).

    >>
    >>
    >> What protocols, changed from what to which?

    >
    >
    >I told him to use NWlink IPX/SPX on the NIC(s). It worked for him. It
    >worked for me as well when I couldn't get Win 2K machines to network
    >with wire and wireless machines.


    Yea, fine. Haven't used that for 5 or 6 years, TCP/IP always works in
    any combination I have.

    So it's router upgrade time for Vista then? I haven't even looked if the
    old protocols are hidden away somewhere on the DVD.

    <snip>

    >One can't force it to work if it don't work and another path has to be
    >taken. Yes, I have heard that NWlink is an old protocol and shouldn't be
    >used, although I really never was shown solid proof as to why.


    Depends on how you look at it, you can set TCP/IP on 1 PC for internet
    access, and NWlink for local sharing without internet access.

    Maybe with Vista you can do this, 1 PC runs IPv4 and 6 the others only
    run IPv6 to share file/print without internet?

    <snip>

    Thanks

    Me
    why?, Mar 21, 2007
    #12
  13. Mr. Arnold Guest

    why? wrote:

    <snipped>

    > So it's router upgrade time for Vista then? I haven't even looked if the
    > old protocols are hidden away somewhere on the DVD.
    >
    >
    > Maybe with Vista you can do this, 1 PC runs IPv4 and 6 the others only
    > run IPv6 to share file/print without internet?
    >


    I guess I'll find out soon as I think I'll becoming of the old
    Contractor's road of travel around the US. I'll be able to pull my stuff
    out of storage, set up my network of MS and Linux machines again and
    continue to learn.

    Vista is in my plans.
    Mr. Arnold, Mar 21, 2007
    #13
    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. =?iso-8859-1?Q?Frisbee=AE?=

    SNMP Issues in Cisco Routers; Vulnerability Issues in TCP

    =?iso-8859-1?Q?Frisbee=AE?=, Apr 21, 2004, in forum: MCSE
    Replies:
    0
    Views:
    790
    =?iso-8859-1?Q?Frisbee=AE?=
    Apr 21, 2004
  2. pcbutts1
    Replies:
    0
    Views:
    584
    pcbutts1
    Jul 6, 2005
  3. pcbutts1
    Replies:
    0
    Views:
    767
    pcbutts1
    Jul 6, 2005
  4. Howie
    Replies:
    0
    Views:
    555
    Howie
    Jul 6, 2005
  5. GJ
    Replies:
    11
    Views:
    661
Loading...

Share This Page