«

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!

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/p...&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

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

On Mar 20, 1:29 pm, "Mike Easter" <M...@ster.invalid> wrote:
> westnilebass...@aol.com 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.

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 "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 ****ing idiot.

--
Your mother was a handsome cauliflower who opened an animal sanctuary in
graveyards.

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 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.

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 ****, else you'll **** on yourself.>

<If you don't know this, then you don't know to wipe too.>

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