Any computer whizzes understand this?

[RedRock]

I play as a regular, when I have time, on a COD:UO server with the [40]nOverVets clan, and one of their server admins posted this message asking for ISP/DHCP help, and I don't even understand what he's asking, but it looks like the pinging tests that Lamron had us do a while back, so I thought maybe someone here (?Lam, ?DS, ?Mar) would know what the guy is asking and what the problem is. I think he's talking about his own home pc, too, not the game server. Any clues, guys? It's from [40]BigNasty, and he's a nice guy, sort of like Mar in how he likes to backshoot and backstab me in the game!

I apparently have a DHCP server app that is not working, or perhaps shouldn't even be on the computer...I have no clue how to remove it / fix it.

Check It:

[00000001] Realtek RTL8139/810x Family Fast Ethernet NIC (FAILED)
Caption = [00000001] Realtek RTL8139/810x Family Fast Ethernet NIC
DatabasePath = %SystemRoot%\System32\drivers\etc
DefaultIPGateway = 192.168.1.1(Same Subnet) (PASSED)
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=0
Reply from 192.168.1.1: bytes=32 time<1ms TTL=0
Reply from 192.168.1.1: bytes=32 time<1ms TTL=0
Reply from 192.168.1.1: bytes=32 time<1ms TTL=0
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
DefaultTTL = 64
Description = Realtek RTL8169/8110 Family Gigabit Ethernet NIC - Packet Scheduler Miniport
DHCPEnabled = TRUE
DHCPLeaseExpires = 10:45:12 PM 4/17/2009
DHCPLeaseObtained = 9:45:12 PM 4/17/2009
DHCPServer = 192.168.0.1 (FAILED)
Pinging 192.168.0.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)

[Major_A]

the 192.168.1.1 looks like a router address.
the DHCPServer = 192.168.0.1 (FAILED) is probly his modem
his nic may have started to fail or dsl/cable modem may be failing or his ISP may have been having issues/ cutting out.

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) If this is the modem address, which is most likely a dsl modem it's probly dropping isp connection/starting to fail/cruddy weather or isp issue of some type

hard to say what it could be for sure without knowing more, but those would be the areas to start at as far as I can tell.

oh, maybe updated drivers for his NIC possibly?

[RedRock]

Oct 31, 2009 11:38:40 GMT -5 Major_A said:

the 192.168.1.1 looks like a router address.
the DHCPServer = 192.168.0.1 (FAILED) is probly his modem
his nic may have started to fail or dsl/cable modem may be failing or his ISP may have been having issues/ cutting out.

Ping statistics for 192.168.0.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss) If this is the modem address, which is most likely a dsl modem it's probly dropping isp connection/starting to fail/cruddy weather or isp issue of some type

hard to say what it could be for sure without knowing more, but those would be the areas to start at as far as I can tell.

oh, maybe updated drivers for his NIC possibly?

Thanks, Major, I'll pass that on.

[Death's Shadow]

looks like he needs to install or update his nic drivers.

Or he has a port blocked in firewall on his pc and or router.


that would be my guess anyway with out knowing more or having my hands on it.

[RedRock]

Thanks, guys, I passed on your comments/thoughts, and here's the update, slightly altered by me for posting here:

Thanks, Red. Your buddies were purty dern close ta perfecto--it was the modem/router. Turns out that after 2 1/2 months of dealing with this issue (and the turds at Charter Cable), I finally figured out last night that when I was upgraded to a higher speed service, the jack hole that did the install of the new wireless router/modem failed to call in the change to the tech dept...so I have been running a wrong MAC address for this entire time. This has produced the poor performance as well as the DHCP issues. The Internet could not properly identify my static IPs, etc., so it simply dropped the connection which resulted in hideous packet loss.

I called the tech dept, and they howled...not even knowing how I had any connectivity whatsoever...they were shocked. So we got it all fixed up, and the DHCP issues have been properly corrected.

Unfortunately, I am still unsatisfied due to the fact that I am unable to introduce the Cable tech, that blew the assignment to begin with, to my new S&P 40.

[Major_A]

HAHA introduce, LOL

glad he got it fixed, but he should get his faster service cheaper for a few months since he wasn't getting what he was paying for, or offer them an introduction.

If that would have happened to me, I would have been seriously urinated off, so to speak. I understand his frustration