DSL with WinXP Home and Win2K

Hello all!

I have just purchased DSL service in my area. I have two computers, one runs WinXP Home and the other Uses Win2k.
Both computers are AMD K-7 1.2 GHz with ONE NIC card each, and plenty of USB ports for each (I know, what the heck do USB ports have to do with anything, well read on).

I also bought a Belkin 4-port DSL/Cable Router to share the connection with the two computers. My promblems are:

1. It slows the connection WAY down (sub 56k).

2. I can't "see" the other computer from either machine.
-both connect to the same workgroup.
-but we can play LAN games.

~btw~

the DSL modem is a speedstream 5160 not sure about that model number. But it lets me connect via USB or Ethernet.
I get a great connection either way if I am connected directly to the modem.


Thanks for whatever help you guys can give.

 

Bummer. Sounds like you have good equipment and no way it should be that slow.

This is really two totally different issues (internet/lan speed and file sharing between the two PCs) so I'll deal with them seperately.

Only possible reasons I can think of for your internet connections to be that bad thru the router/switch are hardware related and happen between the PC and the switch part of the Belkin. Unlikely to be related to the router piece unless the firmware is seriously messed up.

a) Marginal network cable.
- Are they home made or store bought? If home made, maybe too much untwisted wire to the connector causing lots of crosstalk and static. If store bought, highly unlikely that both are bad so try only hooking one PC to the router/switch and see about internet access then. If bad, try the other cable. Broadband is so slow that a cable might easily work fine directly to the modem but cause bad problems when run thru the switch.

b) Bad switch (part of the router) and there is so much chatter and garbage generated by the port(s) that normal traffic is seriously slowed. If you've tried changing ports, the remaining diagnostics are a little tricky. Possible but not real simple. If no other answers appear, post back and I'll give some ideas for trapping traffic details.

c) Problems with the NIC and the switch port negotiating an operating speed. For this, try setting both NICs to 10Mbs half-duplex. If that helps, keep changing to faster connections - i.e., to 10Mbs full-duplex then 100Mbs half and finally 100Mbs full. Avoid the auto setting. Not sure about your specific switch but if the ports can have their speed set, try matching the switch port speed/duplexing to that of the NIC.

LAN issues

In order for a peer-peer setup to work properly with NT systems involved, you will need to be logging on to both PCs and will need both a username and a password. Put both user accounts with password (must be exact and case is important) into the Users section on each PC. Basically NT demands to know Who is trying to connect before deciding to allow it or not. 9X wasn't that way.

Avoid "network neighborhood" or "computers near me" or any of that. Map to the share on the other PC that contains the stuff you want to see & use. Works lots better and especially on a peer setup. Domains do pretty well with the nethood thing but it is still slower and adds overhead for no good reason except for a share you only very rarely want to connect to.

~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

If none of the above helps out and you do need to post back for more help (as opposed to posting that your problems are solved) please post the results of the following:

Assuming two PCs with IP addresses / names of
192.168.0.2 PC1
192.168.0.3 PC2

start~run~cmd and then (you will be sending the results to some small text files and will not see any on-screen results)

First from PC1
ipconfig /all > c:\PC1-cfg.txt
ping -a 192.168.0.3 > c:\ping-PC2.txt

and then from PC2
ipconfig /all > c:\PC2-cfg.txt
ping -a 192.168.0.2 > c:\ping-PC1.txt

 

Newt,

Good news and bad...

The Good first.

File, print, computer sharing works now. Didn't know about logging on.

Now the Bad.

Switched all the cables, and ports around...Still slow through the router. BTW all the cables were store bought but I tried switching them out anyway.

Here is the info. you wanted.

first the pings:

******************************************
Pinging 192.168.0.2 with 32 bytes of data:

Request timed out.
Reply from 162.40.216.1: Destination host unreachable.
Request timed out.
Request timed out.

Ping statistics for 192.168.0.2:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),

Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

************

Pinging 192.168.0.1 with 32 bytes of data:

Request timed out.
Reply from 162.40.216.1: Destination host unreachable.
Request timed out.
Reply from 162.40.216.1: Destination host unreachable.

Ping statistics for 192.168.0.1:

Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms

******************************************

Now the Ipconfigs

PC1:
Windows IP Configuration

Host Name . . . . . . . . . . . . : stephen
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : -d
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC

Physical Address. . . . . . . . . : 00-D0-09-C4-9D-98
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.2.22
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.1

Lease Obtained. . . . . . . . . . : Thursday, October 10, 2002 8:20:53 PM

Lease Expires . . . . . . . . . . : Monday, January 18, 2038 11:14:07 PM

*********************

Windows 2000 IP Configuration



Host Name . . . . . . . . . . . . : josh
Primary DNS Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : -d

Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : -d
Description . . . . . . . . . . . : HP Ethernet with LAN remote power adapter
Physical Address. . . . . . . . . : 00-60-B0-5D-F4-CD

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

IP Address. . . . . . . . . . . . : 192.168.2.36

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.2.1

DHCP Server . . . . . . . . . . . : 192.168.2.1

DNS Servers . . . . . . . . . . . : 192.168.2.1
Lease Obtained. . . . . . . . . . : Friday, October 11, 2002 8:56:23 AM

Lease Expires . . . . . . . . . . : Monday, January 18, 2038 10:14:07 PM



Thanks for checking it out Newt.

 

I wonder why they are grabbing IPs so high?
Something really flakey going on.

 

router IP

those Ip addies are from the router...it maybe that the router has been configured to use higher IP settings...

i have found that for 2 comps to talk at least w/W2K that NetBIOS over TCP/IP needs to be used...at least thats the way my 2 comps are doing it....

neomatsu