Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works
Photo

possible ethernet problem


  • Please log in to reply

#16
ZpoonZ

ZpoonZ

    Member

  • Topic Starter
  • Member
  • PipPip
  • 31 posts
C:\Documents and Settings\User>ipconfig /release

Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Autoconfiguration IP Address. . . : 169.254.247.203
Subnet Mask . . . . . . . . . . . : 255.255.0.0
IP Address. . . . . . . . . . . . : fe80::20c:76ff:fe73:b0a8%4
Default Gateway . . . . . . . . . :

PPP adapter Alcatel Speedtouch Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 84.12.155.99
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 84.12.155.99

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
Default Gateway . . . . . . . . . :

Tunnel adapter 6to4 Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 2002:540c:9b63::540c:9b63
Default Gateway . . . . . . . . . : 2001:16d8:2:80:0:1:6150:46

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:169.254.247.203%2
Default Gateway . . . . . . . . . :

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:84.12.155.99%2
Default Gateway . . . . . . . . . :

C:\Documents and Settings\User>ipconfig /renew

Windows IP Configuration

An error occurred while renewing interface Local Area Connection : unable to contact your DHCP server. Request has timed out.

  • 0

Advertisements


#17
ZpoonZ

ZpoonZ

    Member

  • Topic Starter
  • Member
  • PipPip
  • 31 posts
i've tried most of the stuff on this guide: link

still no joy though.
:whistling:
  • 0

#18
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
hmm....the router is seeing the desktop when it's plugged into it...what's the dealio? i wonder if the usb modem is conflicting with the NIC....try plugging into the router with the desktop...and unplug the modem...then do the ipconfig /release /renew stuff...
  • 0

#19
ZpoonZ

ZpoonZ

    Member

  • Topic Starter
  • Member
  • PipPip
  • 31 posts
OK, LOTS of progress! nearly there now!
:whistling:

so far:
installed SP2
rebooted

installed the network fix suggested on that page
made the registry change
rebooted

change network adapter connection type to auto-negotiation/full duplex 10BaseT/full duplex 100BaseT (i've changed it back to auto-negotiation now)

and: "Reset your TCP/IP stack by downloading and running WinsockXPFix.exe a Visual Basic program designed to fix corrupted TCP/IP issues, host file problems and a variety of other connectivity issues."

FINALLY i've gotten it semi working!

OK, so now it assigns IP address no problem. on the router config screen (still accessed from the laptop) i can now see both computers, with their respctive names, rather than 'unknown-' and my MAC address.

i can't access the router config screen from the desktop still, but it's not timing out any more, it just sits there!

on the laptop, from the command line i can ping the desktop but i get packet loss. anything from 0% to 100%
same on the desktop, i can ping the laptop, but i get random amounts of packet loss. from 0% to 100%.

here's the new IPCONFIG /ALL results from my desktop:

C:\Documents and Settings\User>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : ZPOONZ-DESK
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : config

PPP adapter Alcatel Speedtouch Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 84.12.27.184
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 84.12.27.184
DNS Servers . . . . . . . . . . . : 213.208.106.212
213.208.106.213

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : config
Description . . . . . . . . . . . : VIA Rhine II Fast Ethernet Adapter
Physical Address. . . . . . . . . : xx-xx-xx-xx-xx-xx
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.65
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : ?
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DNS Servers . . . . . . . . . . . : 192.168.1.254
?
?
?
Lease Obtained. . . . . . . . . . : 14 June 2006 22:47:55
Lease Expires . . . . . . . . . . : 15 June 2006 22:47:55

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : FF-FF-FF-FF-FF-FF-FF-FF
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : ?
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Disabled


i know it's almost a different problem now, but i'm convinced that it's related.

:blink:

here are 5 ping results:

C:\Documents and Settings\User>ping 192.168.1.64

Pinging 192.168.1.64 with 32 bytes of data:

Request timed out.
Reply from 192.168.1.64: bytes=32 time=268ms TTL=128
Reply from 192.168.1.64: bytes=32 time=1ms TTL=128
Reply from 192.168.1.64: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.1.64:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 268ms, Average = 90ms

C:\Documents and Settings\User>ping 192.168.1.64

Pinging 192.168.1.64 with 32 bytes of data:

Reply from 192.168.1.64: bytes=32 time=1ms TTL=128
Reply from 192.168.1.64: bytes=32 time=1ms TTL=128
Request timed out.
Request timed out.

Ping statistics for 192.168.1.64:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

C:\Documents and Settings\User>ping 192.168.1.64

Pinging 192.168.1.64 with 32 bytes of data:

Reply from 192.168.1.64: bytes=32 time=1ms TTL=128
Request timed out.
Reply from 192.168.1.64: bytes=32 time=1ms TTL=128
Request timed out.

Ping statistics for 192.168.1.64:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

C:\Documents and Settings\User>ping 192.168.1.64

Pinging 192.168.1.64 with 32 bytes of data:

Request timed out.
Request timed out.
Reply from 192.168.1.64: bytes=32 time=1ms TTL=128
Reply from 192.168.1.64: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.1.64:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

C:\Documents and Settings\User>ping 192.168.1.64

Edited by ZpoonZ, 14 June 2006 - 04:06 PM.

  • 0

#20
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
from the desktop do a tracert on the laptop (from the laptop do a tracert on the desktop)

to do a tracert do
start > run > cmd > tracert <ip address of other computer>

and post the results
  • 0

#21
ZpoonZ

ZpoonZ

    Member

  • Topic Starter
  • Member
  • PipPip
  • 31 posts
:whistling:

it's back to not being able to acquire a network address now.

by the way, my new ISP is up and running now. so i can only connect from my laptop via the new modem/router.
i really need to get this working! i'm stumped.
:blink:
  • 0

#22
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
...i was thinking that the modem was screwing up the connection...being that you were trying to connect with the modem AND the router...COMPLETELY uninstall that modem...and remove any of it's corresponding network connections in your network neighborhood

edit: did i just say network neighborhood....how old is that?!?!...jeebus "network connections" under the properties of "my network places"
  • 0

#23
ZpoonZ

ZpoonZ

    Member

  • Topic Starter
  • Member
  • PipPip
  • 31 posts
ok, after trying a load of times it finally got an IP address.
here are two route traces to the router itself:

C:\Documents and Settings\User>tracert 192.168.1.254

Tracing route to dsldevice.config [192.168.1.254]
over a maximum of 30 hops:

1 * * * Request timed out.
2 <1 ms * * dsldevice.config [192.168.1.254]
3 * <1 ms * dsldevice.config [192.168.1.254]
4 <1 ms * * dsldevice.config [192.168.1.254]
5 <1 ms <1 ms * dsldevice.config [192.168.1.254]
6 <1 ms * * dsldevice.config [192.168.1.254]
7 <1 ms * * dsldevice.config [192.168.1.254]
8 * * <1 ms dsldevice.config [192.168.1.254]

Trace complete.

C:\Documents and Settings\User>tracert 192.168.1.254

Tracing route to dsldevice.config [192.168.1.254]
over a maximum of 30 hops:

1 1 ms * * dsldevice.config [192.168.1.254]
2 <1 ms * * dsldevice.config [192.168.1.254]
3 * <1 ms <1 ms dsldevice.config [192.168.1.254]

Trace complete.

  • 0

#24
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
what did you type to do that trace? the ip of the other computer or the ip of the router?
  • 0

#25
ZpoonZ

ZpoonZ

    Member

  • Topic Starter
  • Member
  • PipPip
  • 31 posts
the ip of the router.
  • 0

Advertisements


#26
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
do the same tracert from each computer...but put the other computer's ip address in (ie from the laptop do tracert <ip of desktop>) of course...do this with both machines connected to said router
  • 0

#27
ZpoonZ

ZpoonZ

    Member

  • Topic Starter
  • Member
  • PipPip
  • 31 posts
please note that the IPs are reversed today! (i.e. laptop IP is now x.x.x.65, and desktop is now x.x.x.64)

from the laptop:
C:\Documents and Settings\ZpoonZ>tracert 192.168.1.254

Tracing route to dsldevice.config [192.168.1.254]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms dsldevice.config [192.168.1.254]

Trace complete.

C:\Documents and Settings\ZpoonZ>tracert 192.168.1.64

Tracing route to ZPOONZ-DESK.config [192.168.1.64]
over a maximum of 30 hops:

1 1 ms * * ZPOONZ-DESK.config [192.168.1.64]
2 1 ms 1 ms * ZPOONZ-DESK.config [192.168.1.64]
3 * * * Request timed out.
4 1 ms * 1 ms ZPOONZ-DESK.config [192.168.1.64]

Trace complete.


from the desktop:
C:\Documents and Settings\User>tracert 192.168.1.254

Tracing route to dsldevice.config [192.168.1.254]
over a maximum of 30 hops:

1 * <1 ms <1 ms dsldevice.config [192.168.1.254]

Trace complete.

C:\Documents and Settings\User>tracert 192.168.1.65

Tracing route to ZPOONZ-LAP.config [192.168.1.65]
over a maximum of 30 hops:

1 1 ms 1 ms 3 ms ZPOONZ-LAP.config [192.168.1.65]

Trace complete.

  • 0

#28
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
can the two ping each other?

also now that the desktop has an ip..can it connect to the internet?
  • 0

#29
ZpoonZ

ZpoonZ

    Member

  • Topic Starter
  • Member
  • PipPip
  • 31 posts
same thing as yesterday. anything between 0 and 100% loss.
i just tried pinging each other and got 75% loss (219ms) from the desktop to the lap, and 50% loss (1ms) from the laptop to the desk.

still can't connect to internet from desk.
when i tried to connect to routed config, the title came up in the very top of the window of my browser (on the bit above the menu bar) but it just sits there and doesn't go any further. it doesn't say 'cannot connect' it just sits there forever.
  • 0

#30
dsenette

dsenette

    Je suis Napoléon!

  • Administrator
  • 26,019 posts
  • MVP
Please try WinsockFix. Once run, reboot and test your connection.

If that fails, please goto Start, Run, type CMD, press 'OK', then type the following commands:
  • netsh winsock reset catalog
  • netsh int ip reset reset.log
Reboot and test.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP