Tech Support Forum banner
Status
Not open for further replies.
1 - 9 of 9 Posts

· Registered
Joined
·
4 Posts
Discussion Starter · #1 ·
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\user>IPCONFIG /ALL
Windows IP Configuration
Host Name . . . . . . . . . . . . : Parris
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : carolina.rr.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : carolina.rr.com
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-11-0A-A3-7E-40
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 174.110.173.242
Subnet Mask . . . . . . . . . . . : 255.255.224.0
Default Gateway . . . . . . . . . : 174.110.160.1
DHCP Server . . . . . . . . . . . : 10.221.0.1
DNS Servers . . . . . . . . . . . : 209.18.47.61
209.18.47.62
Lease Obtained. . . . . . . . . . : Wednesday, January 04, 2012 11:19:10
AM
Lease Expires . . . . . . . . . . : Wednesday, January 04, 2012 8:46:55
PM
C:\Documents and Settings\user>
C:\Documents and Settings\user>ping 174.110.173.242
Pinging 174.110.173.242 with 32 bytes of data:
Reply from 174.110.173.242: bytes=32 time<1ms TTL=128
Reply from 174.110.173.242: bytes=32 time<1ms TTL=128
Reply from 174.110.173.242: bytes=32 time<1ms TTL=128
Reply from 174.110.173.242: bytes=32 time<1ms TTL=128
Ping statistics for 174.110.173.242:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Documents and Settings\user>ping 174.110.160.1
Pinging 174.110.160.1 with 32 bytes of data:
Reply from 174.110.160.1: bytes=32 time=6ms TTL=255
Reply from 174.110.160.1: bytes=32 time=15ms TTL=255
Reply from 174.110.160.1: bytes=32 time=5ms TTL=255
Reply from 174.110.160.1: bytes=32 time=5ms TTL=255
Ping statistics for 174.110.160.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 5ms, Maximum = 15ms, Average = 7ms
C:\Documents and Settings\user>ping 216.109.112.135
Pinging 216.109.112.135 with 32 bytes of data:
Reply from 216.109.112.135: bytes=32 time=28ms TTL=245
Reply from 216.109.112.135: bytes=32 time=33ms TTL=245
Reply from 216.109.112.135: bytes=32 time=41ms TTL=245
Reply from 216.109.112.135: bytes=32 time=33ms TTL=245
Ping statistics for 216.109.112.135:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 41ms, Average = 33ms
C:\Documents and Settings\user>ping yahoo.com
Pinging yahoo.com [72.30.2.43] with 32 bytes of data:
Reply from 72.30.2.43: bytes=32 time=86ms TTL=54
Reply from 72.30.2.43: bytes=32 time=86ms TTL=54
Reply from 72.30.2.43: bytes=32 time=85ms TTL=54
Reply from 72.30.2.43: bytes=32 time=87ms TTL=54
Ping statistics for 72.30.2.43:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 85ms, Maximum = 87ms, Average = 86ms
C:\Documents and Settings\user>
 

· Registered
Joined
·
548 Posts
IP Address. . . . . . . . . . . . : 174.110.173.242
Subnet Mask . . . . . . . . . . . : 255.255.224.0
Default Gateway . . . . . . . . . : 174.110.160.1
DHCP Server . . . . . . . . . . . : 10.221.0.1
It looks like your network is setup incorrectly. By the looks of it, do you have a router connected to your modem?
 

· Registered
Joined
·
2 Posts
Well, Seems to me like you have connectivity to the internet via both ICMP and DNS. But if you can't browse internet you need to check your HTTP connectivity as well. Try running the below command in CMD.

C:\ telnet 98.137.149.56 80

You may replace the above IP addredd with any IP address of a working website. This should make your CMD screen blank if you do have HTTP connectivity. If you don't, you should get an error message after you entered the command. Try this and tell us..
 

· TSF Emeritus
Joined
·
16,407 Posts
Um not quite. All pings are successful including a ping to yahoo.com which means dns resolved the name to a ip address successfully.

Things get a little crazy on a large isp network which is why you see dhcp server in a totally differnet subnet. This would be due to dhcp helper/relay agent on a router which forwards the dhcp request/ack thru the router which normally would not do so.

Since the subnet mask 255.255.254.0 gives a range of ips 174.110.160.0 - 174.110.191.255 you can see that both the ip address and gateway are within the proper range.

pzo1970 specifically what is your issue?

Its clear you don't have a router protecting you which means you are vulnerable to port trojans/hackers. Has this worked previously for you?
 

· Registered
Joined
·
4 Posts
Discussion Starter · #5 ·
Thank you guys for the help.

Yes, the workstation is usually connected to a router, but during this troubleshooting session I have hooked it directly to the cable modem.

I run process that requires my modem to release and renew its IP leases but is continually times out in the process.

I am able to connect to the internet, but im unable to manully renew my ips at this point.

I have tried everything I can think of, lspfix, winsock fix to be more precise.

I noticed the dhcp was not running on the proper port. It was running on a port that had been opened with about 15 other processes running on that particular portPort 980. (tryed to recreate the report but to no avail)

Im attempting not to be forced to wipe harddirve and start fresh. This is infact the only issue with workstation and Im sure that this board can help me get it done..

Thanks..

Attached is a screenshot of my systems event viewer with the error, and a log file from the dhcp server
 

Attachments

· Registered
Joined
·
4 Posts
Discussion Starter · #6 ·
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\user>netstat -b
Active Connections
Proto Local Address Foreign Address State PID
TCP Parris:1039 localhost:1041 ESTABLISHED 3200
[java.exe]
TCP Parris:1041 localhost:1039 ESTABLISHED 3200
[java.exe]
TCP Parris:31000 localhost:32000 ESTABLISHED 3200
[java.exe]
TCP Parris:32000 localhost:31000 ESTABLISHED 2376
[wrapper.exe]
TCP Parris:1628 asterisk.app11.logmeinrescue-enterprise.com:http
s ESTABLISHED 1480
[LogMeIn.exe]

C:\Documents and Settings\user>netstat -an
Active Connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2002 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3260 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3261 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8019 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8088 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1037 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1039 127.0.0.1:1041 ESTABLISHED
TCP 127.0.0.1:1041 127.0.0.1:1039 ESTABLISHED
TCP 127.0.0.1:31000 127.0.0.1:32000 ESTABLISHED
TCP 127.0.0.1:32000 0.0.0.0:0 LISTENING
TCP 127.0.0.1:32000 127.0.0.1:31000 ESTABLISHED
TCP 174.110.173.242:139 0.0.0.0:0 LISTENING
TCP 174.110.173.242:1628 64.94.18.142:443 ESTABLISHED
TCP 174.110.173.242:5001 0.0.0.0:0 LISTENING
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1900 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1900 *:*
UDP 127.0.0.1:2001 *:*
UDP 127.0.0.1:2027 *:*
UDP 127.0.0.1:2060 *:*
UDP 174.110.173.242:123 *:*
UDP 174.110.173.242:137 *:*
UDP 174.110.173.242:138 *:*
UDP 174.110.173.242:1900 *:*
C:\Documents and Settings\user>netstat
Active Connections
Proto Local Address Foreign Address State
TCP Parris:1039 localhost:1041 ESTABLISHED
TCP Parris:1041 localhost:1039 ESTABLISHED
TCP Parris:31000 localhost:32000 ESTABLISHED
TCP Parris:32000 localhost:31000 ESTABLISHED
TCP Parris:1628 asterisk.app11.logmeinrescue-enterprise.com:http
s ESTABLISHED
TCP Parris:2118 yx-in-f105.1e100.net:http ESTABLISHED
TCP Parris:2119 rdc-024-025-026-153.southeast.rr.com:http ESTAB
LISHED
TCP Parris:2120 rdc-024-025-026-153.southeast.rr.com:http ESTAB
LISHED
TCP Parris:2121 rdc-024-025-026-153.southeast.rr.com:http ESTAB
LISHED
TCP Parris:2123 rdc-024-025-026-153.southeast.rr.com:http ESTAB
LISHED
TCP Parris:2124 rdc-024-025-026-153.southeast.rr.com:http ESTAB
LISHED
TCP Parris:2125 rdc-024-025-026-153.southeast.rr.com:http ESTAB
LISHED
TCP Parris:2126 yw-in-f154.1e100.net:http ESTABLISHED
TCP Parris:2127 rdc-024-025-026-144.southeast.rr.com:http ESTAB
LISHED
TCP Parris:2128 ec2-107-22-174-17.compute-1.amazonaws.com:http
ESTABLISHED
TCP Parris:2129 yx-in-f154.1e100.net:http ESTABLISHED
TCP Parris:2130 yx-in-f148.1e100.net:http ESTABLISHED
TCP Parris:2131 24.143.206.91:http ESTABLISHED
TCP Parris:2132 rdc-024-025-026-147.southeast.rr.com:http ESTAB
LISHED
TCP Parris:2133 24.143.206.58:http ESTABLISHED
TCP Parris:2135 rdc-024-025-026-153.southeast.rr.com:http ESTAB
LISHED
TCP Parris:2136 gx-in-f155.1e100.net:http ESTABLISHED
TCP Parris:2137 rdc-024-025-026-153.southeast.rr.com:http ESTAB
LISHED
TCP Parris:2138 ec2-50-16-215-15.compute-1.amazonaws.com:http E
STABLISHED
TCP Parris:2139 24.143.206.49:http ESTABLISHED
TCP Parris:2141 208.71.125.1:http TIME_WAIT
TCP Parris:2143 ec2-107-21-12-188.compute-1.amazonaws.com:http
ESTABLISHED
TCP Parris:2144 174.137.34.100:http ESTABLISHED
TCP Parris:2145 174.137.34.100:http ESTABLISHED
TCP Parris:2146 rdc-024-025-026-153.southeast.rr.com:http ESTAB
LISHED
TCP Parris:2151 lb2pfilter.xiti.com:http TIME_WAIT
TCP Parris:2152 yw-in-f113.1e100.net:http ESTABLISHED
TCP Parris:2153 yw-in-f113.1e100.net:http ESTABLISHED
TCP Parris:2155 ec2-50-16-215-15.compute-1.amazonaws.com:http E
STABLISHED
TCP Parris:2157 ec2-107-20-149-6.compute-1.amazonaws.com:http E
STABLISHED
TCP Parris:2158 ec2-107-20-149-6.compute-1.amazonaws.com:http E
STABLISHED
TCP Parris:2159 204.246.169.194:http ESTABLISHED
TCP Parris:2160 rdc-024-025-026-153.southeast.rr.com:http ESTAB
LISHED
TCP Parris:2161 ec2-50-17-253-115.compute-1.amazonaws.com:http
ESTABLISHED
TCP Parris:2165 204.246.169.194:http ESTABLISHED
TCP Parris:2166 204.246.169.194:http ESTABLISHED
TCP Parris:2170 ec2-184-73-189-176.compute-1.amazonaws.com:http
ESTABLISHED
TCP Parris:2171 gy-in-f155.1e100.net:http ESTABLISHED
TCP Parris:2172 yw-in-f156.1e100.net:http ESTABLISHED
TCP Parris:2178 24.143.206.115:http ESTABLISHED
TCP Parris:2179 24.143.206.115:http ESTABLISHED
TCP Parris:2180 24.143.206.115:http ESTABLISHED
TCP Parris:2182 24.143.206.115:http ESTABLISHED
TCP Parris:2184 24.143.206.58:http ESTABLISHED
TCP Parris:2185 ec2-50-17-192-49.compute-1.amazonaws.com:http E
STABLISHED
TCP Parris:2186 24.143.206.58:http ESTABLISHED
TCP Parris:2193 208.71.125.131:http ESTABLISHED
TCP Parris:2197 208.71.125.52:http ESTABLISHED
TCP Parris:2200 tacoda-atwola-prod-adcom-dtc.evip.aol.com:http
ESTABLISHED
TCP Parris:2202 69.80.196.159:http ESTABLISHED
TCP Parris:2206 ar-cs-adcom-dtc.evip.aol.com:http ESTABLISHED
TCP Parris:2208 s3-1-w.amazonaws.com:http ESTABLISHED
TCP Parris:2209 67.214.159.90:http ESTABLISHED
TCP Parris:2210 75.98.35.14:http ESTABLISHED
TCP Parris:2212 208.71.125.18:http ESTABLISHED
TCP Parris:2213 208.71.125.28:http ESTABLISHED
TCP Parris:2218 75.98.35.15:http ESTABLISHED
TCP Parris:2219 24.143.206.83:http ESTABLISHED
TCP Parris:2220 24.143.206.83:http ESTABLISHED
TCP Parris:2221 yx-in-f148.1e100.net:http ESTABLISHED
TCP Parris:2222 xml.harrahs.com:http ESTABLISHED
TCP Parris:2223 lb2pfilter.xiti.com:http TIME_WAIT
TCP Parris:2227 cdce.acs006.internap.com:http ESTABLISHED
TCP Parris:2234 mpr2.ngd.vip.bf1.yahoo.com:http CLOSE_WAIT
TCP Parris:2237 a.tribalfusion.com:http ESTABLISHED
TCP Parris:2241 mpr2.ngd.vip.bf1.yahoo.com:http CLOSE_WAIT
TCP Parris:2242 157.55.117.17:http ESTABLISHED
TCP Parris:2248 24.143.206.83:http ESTABLISHED
C:\Documents and Settings\user>netstat -r
Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 11 0a a3 7e 40 ...... Broadcom NetXtreme Gigabit Ethernet - Packet Sch
eduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 174.110.160.1 174.110.173.242 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
174.110.160.0 255.255.224.0 174.110.173.242 174.110.173.242 20
174.110.173.242 255.255.255.255 127.0.0.1 127.0.0.1 20
174.110.255.255 255.255.255.255 174.110.173.242 174.110.173.242 20
224.0.0.0 240.0.0.0 174.110.173.242 174.110.173.242 20
255.255.255.255 255.255.255.255 174.110.173.242 174.110.173.242 1
Default Gateway: 174.110.160.1
===========================================================================
Persistent Routes:
None
 

· TSF Emeritus
Joined
·
16,407 Posts
"I run process that requires my modem to release and renew its IP leases but is continually times out in the process.
I am able to connect to the internet, but im unable to manully renew my ips at this point. "

You don't have a problem. If your isp is doing ip reservations you will get the same ip every time. I would never consider formatting over a dhcp error. If it isn't broke don't fix it.
 

· Registered
Joined
·
4 Posts
Discussion Starter · #8 · (Edited)
My intent here is to take the tcip/ip, dhcp protocals back to thier virgin states.

I appreciate your opinion, but my isp DOES NOT have ip reservation. That was the reason I chose my particular ISP. I plugged another workstation to the modem and Im having no issues at all. Ip rotates the way that it should rotate.

Can you give me any insight from the log files above into what I need to check to get all networking components back to its virgin state in Windows XP Pro SP3?

Thank You
 

· TSF Emeritus
Joined
·
16,407 Posts
simple test
put the mac address of the pc nic that rotates correctly on the pc nic that doesn't
if the ip changes then you know for sure for whatever reason the isp has mapped your mac address.
you do this in the configure/advanced section of the nic properties under "network address" or "locally administered address"

You may wish to consider a repair install of the OS before you format and do a clean install.

BTW there is nothing in the dhcp protocol that can request a specific ip. simply doesn't work that way. The requestor can only get what the supplier sends. If this was not the case then you would be not getting internet due to a ip conflict at the isp level. After all someone else would have that ip, right?
 
1 - 9 of 9 Posts
Status
Not open for further replies.
Top