false IP reading

[hypronix]

Hmm so you already resetted the modem... supposedly by unplugging it [if not try that].

If the ISP sees your proper IP [although you shouldn't get new IPs on cable in most parts that I know] then the only thing I can htink about is connection hijack, so I would do a traceroute ASAP and see what awkward IPs that gives you.

Alternatively you could try downloading something like Knoppix LiveCD and see how that works [ifconfig would give you your IP] and in case you get the proper one then I assume something's wrong with Win. Run an AV program, Google for that HJT output... If however you get the same ip then either your ISP cache is at fault or... something else that I didn't think of.

I would also ping the IP you should have and the one you do have and see how that works, eventually try and traceroute those aswell... see to whom the IP belongs to [if it's not your ISP] and if the problem persists send them an e-mail.

Keep us posted...

[Simple Simon]

by nihil

I am over in the UK so things may be a bit different, With my dial-up 56.6 and DSL connections I get a new IP every time I log out and back on. With cable the address tends to be static, perhaps there is some delay before the change is implemented by your ISP............or their records are updated, hence the suggestion of traceroute and whois.

Your cable IP address probably has a longer lease time on the DHCP than the dial up lease time. This would make sense if you consider the duration of connections, i.e. dial up short and cable long ("always on"). You may have noticed that occasionally it changes, but not very often.

The DHCP lease time for the PC's where I work are set to 21 days. So if they do not connect to the DHCP server in 21 days, then the very next time they connect they may obtain a new IP address, but only if the one previously leased to them has been re-allocated to a different PC.

Wow - long sentence. Does that make sense?

If not click here. Or click there anyway! lol

[hypronix]

Originally posted here by Simple Simon
Your cable IP address probably has a longer lease time on the DHCP than the dial up lease time. This would make sense if you consider the duration of connections, i.e. dial up short and cable long ("always on"). You may have noticed that occasionally it changes, but not very often.

The way I understood it is that the ISP sees he's been given a different IP address then what he is able to see for himself. In that case it's not a DHCP lease time IMO.

[Simple Simon]

I was referrring to nihil's situation not isle_of_infamy's. I didnt't make that very clear did I?

When I read what I typed, it seems a bit garbled! lol

Did I get it totally wrong?

[Tiger Shark]

Ok.... Let's go back to basics.... You are saying a lot about the IP's being different..... I want you to post them please. But before you do that I need you to think a bit.

If both the IP's start with the same two octals, (ie: 67.65), then place x's for the numbers in the first two octals so 67.65.125.34 would become xx.xx.125.34.... OK?

If the first two octals are 192.168. or 10.x or 172.1 through 172.16 then post them in full.

Then make sure that you show the subnet mask for both the IP's.

Without knowing the IP's, or at least a close approximation of them we are all really "shooting in the dark".....

[ShagDevil]

isle_of_infamy,
I've never really experienced this type of problem so I can offer only limited advice.
Are there any boxes checked under:
Internet Properties-->Connections-->(Highlight your default connetion) and click on the Settings tab-->Proxy Server
(OR)
Internet Properties-->Connections-->LAN settings-->Proxy Server

I know it sounds pretty simple and somewhat stupid but, I'm just starting with the basics.
Also, there's this quick little website test you can run to see if it detects any Proxy Servers in use:
http://www.proxyinfo.co.uk/check.php

[isle_of_infamy]

ok for i guess my ip was my ip afterall but for some reason my cable company didn't know what my ip was. how stupid is that ?

[Shugart]

did you ever try ping'ing or doing a tracert on both IPs? I would think that if you did have an IP problem, ie spoofed, etc. that you wouldn't be able to get on the net because your request would be lost aand if you tried pinging it should come up as"request lost" because of that. I have seen similar things done in trojan programs that do DrDos attacks. They work by spoofing the IP address of the target and then send a flood of ping request to a router and thus the router sends it back to target IP and makes it a very clever, but very hard to trace attack.

Shugart-

[nihil]

ok for i guess my ip was my ip afterall but for some reason my cable company didn't know what my ip was. how stupid is that ?

Well, with the usual reservations about being in different countries

1. Because cable companies do not change your IP very frequently, they may not update their records that frequently either? And I am willing to bet that customer services/tech support are at the bottom of the information foodchain.

2. I have known it that when an ISP has had problems they have temporarily "rented" bandwidth from apparent rivals.............antitrust? ho ho ho

Grab yourself that tool I suggested and do a bit of investigating.

Cheers

[rapier57]

In any case, the confusion may be that likely there is a significant latency between the assignment of the IP at the client side, and the update of the DNS records on the support side. So, the query run by the support person probably picked up whatever was in DNS cache at the time.