Computer Expert Needed!

[troutbert]

salmonoid wrote:
To actually try to be helpful to the OP, can you answer these questions:

1) Are you able to access other websites or is it just PAFF that does not work?

Hey now. THERE'S an idea!

But it's lacking in techy lingo. And hammers.

 

[pcray1231]

I'd add:

3. Do the same devices open paflyfish on other networks?

4. Is this new? i.e. WERE these devices able to access paflyfish on this network at sometime in the recent past?

 

[shortrod2]

salmonoid wrote:

shortrod2 wrote:
The signal to noise ratio on this thread is fatally low.
Command line utilities like ping and traceroute are often helpful to separate the wheat from the chaff.

Will they tell me if I am spoofing my IP?

No, those tools tell you if you reach www.flyfish.com thru your network.

Example of ping:

$ ping www.paflyfish.com
PING paflyfish.com (173.248.187.160): 56 data bytes
64 bytes from 173.248.187.160: icmp_seq=0 ttl=52 time=132.999 ms
64 bytes from 173.248.187.160: icmp_seq=1 ttl=52 time=148.414 ms
64 bytes from 173.248.187.160: icmp_seq=2 ttl=52 time=131.057 ms

It proves that I can talk to www.paflyfish.com



Example of traceroute:

traceroute to paflyfish.com (173.248.187.160), 64 hops max, 52 byte packets
1 99-999-999-9-static.local.acces.point.net (99.999.999.9) 1.291 ms 0.793 ms 0.725 ms
2 router.region.pa.pitt.comcast.net (99.999.999.999) 1.748 ms 1.602 ms 1.694 ms
3 69.139.168.25 (69.139.168.25) 10.443 ms
te-0-5-0-2-ar03.pittsburgh.pa.pitt.comcast.net (69.139.195.17) 10.426 ms
69.139.168.29 (69.139.168.29) 5.731 ms
4 he-4-5-0-0-cr01.ashburn.va.ibone.comcast.net (68.86.94.165) 10.611 ms
he-4-14-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.94.185) 17.063 ms 17.076 ms
5 23.30.207.94 (23.30.207.94) 32.573 ms 29.694 ms
ae12.edge1.newyork2.level3.net (4.68.127.1) 16.690 ms
6 vlan52.ebr2.newyork2.level3.net (4.69.138.254) 79.581 ms
vlan52.ebr2.washington12.level3.net (4.69.146.222) 48.862 ms 49.290 ms
7 ae-2-2.ebr1.chicago1.level3.net (4.69.132.65) 54.592 ms 54.659 ms
ae-6-6.ebr2.chicago2.level3.net (4.69.148.146) 48.213 ms
8 ae-1-100.ebr1.chicago2.level3.net (4.69.132.113) 56.098 ms
ae-6-6.ebr1.chicago2.level3.net (4.69.140.190) 75.948 ms 55.079 ms
9 ae-3-3.ebr2.denver1.level3.net (4.69.132.61) 48.414 ms 58.855 ms 53.973 ms
10 ae-2-52.edge3.denver1.level3.net (4.69.147.104) 61.272 ms 50.248 ms 54.064 ms
11 handy-netwo.edge3.denver1.level3.net (4.53.12.246) 126.794 ms 152.085 ms 88.411 ms
12 68.71.128.68 (68.71.128.68) 85.352 ms 126.677 ms 144.248 ms
13 ae0-10.dist2.denver2.wehostwebsites.com (68.71.128.145) 151.139 ms 151.156 ms 126.201 ms
14 173.248.187.160 (173.248.187.160) 108.396 ms 144.337 ms 95.164 ms

It shows all of the routers that I pass thru when talking to www.paflyfish.com.


If you have your modem attached to a router and can connect more than one device to the internet then you have a "spoofed" ip address. The router has to real ip address and every thing that connects thru it has a spoofed address.

On Windows the command line utility ipconfig will tell you your ip address.

Example:

$ ipconfig

Windows IP Configuration
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : localdomain
IP Address. . . . . . . . . . . . : 172.16.206.128
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.206.2

The 172.16.206.128 address is also a spoof on top of a spoof. It is from Windows running inside a virtual machine running on a Mac.

On a Mac or Linux machine the command is ifconfig.

Example with a bunch of noise removed:

$ ifconfig
en0: flags=8863 mtu 1500
ether c8:2a:14:2a:48:c3
inet6 fe80::ca2a:14ff:fe2a:48c3%en0 prefixlen 64 scopeid 0x4
inet 192.168.4.40 netmask 0xffffff00 broadcast 192.168.4.255
media: autoselect (1000baseT )
status: active

The relevant line is inet 192.168.4.40. This is a spoofed ip address. If your ip address starts with 192.168 it is spoofed.

Does this help?

 

[ponner1us]

Thanks guys, appreciate all of the suggestions. I have tried other web browsers, Google Chrome, Firefox, IE, it won't open in any of them. It has always occurred, not a new problem, I was hoping the new wifi modem would correct it, but it just will not open. I got a new Macbook Pro for work so I'm going to take my (old) work laptop home, set everything up and hope it works, then take a sledgehammer to the POS DELL that I have at home that has given me nothing but problems from the get go. If the new (old) laptop doesn't work, I will go through all of the above and hopefully get this issue fixed.

 

[SBecker]

You do realize you must record all smashing that occurs.

 

[troutbert]

salmonoid wrote:
To actually try to be helpful to the OP, can you answer these questions:

1) Are you able to access other websites or is it just PAFF that does not work?

Has this question been answered yet?

 

[salmonoid]

shortrod2 wrote:

Does this help?

I should have put the tags on my post about spoofing. I was adding some gentle ribbing to another post with that terminology. IP spoofing is the process whereby another user or device finds a mean to place a different IP address on a network, generally for nefarious purposes (i.e. to redirect or intercept others' communications). And if a user comes to the PAFF forum for technical help, they probably have no idea what an IP spoof is in the first place, nor would any home user who is not a hacker ever have reason to engage in such an activity. Network Address Translation (NAT) or IP masquerading does not carry the same connotation for me as IP spoofing; they're both technically doing the same thing but the intended purpose is different. And using a fictitious (or private) address doesn't necessarily mean you are using NAT. It simply means that whoever designed the network decided that using addresses that are not routable across the Internet was the way to go.

The fundamental question with troubleshooting any IT issue is to answer the question what changed? There's limited information from the OP, so a few more questions are needed to try and narrow the scope. And once the change area is identified, it may be in an area where the end-user has no control.

Potential change areas:
PAFF webhosting provider - web server (mis)configuration, network changes, DNS changes, content management system changes
ISP (backbone and local) - routing changes, proxy, DNS
Home network - router, individual device configuration, software (spyware?) installation
The latter is the only piece that an end-user can affect any reversal of change.
There could also be hardware or cable failures (changes) in any areas of the above.

What troutbert highlights, and which many technical people lose sight of is the fact that most people are not technically inclined. They don't know even what questions to ask, so they glaze over when they are asked questions in response that are laden with techno-speak or contain a bunch of technical jargon or acronyms. Being able to translate English to tech and vice-versa is an extremely useful skill.

For instance, it probably does little good to try and describe a possible cause as there being a BGP routing issue between two ASes. It's a whole lot more comprehensible to say that the road sign to PAFF pionts down that road over there, but the bridge is out, and you can't get there from here. For those that are curious, Border Gateway Protocol (BGP) is a routing protocol that advertises routes over the Internet. An AS is an Autonomous System - entities are assigned an AS and they advertise to the rest of the world via BGP the routes that they handle. Think of it as a way for the backbone Internet routers to become self-aware of how to reach an edge of the Internet - the routers play a sort of whisper-down-the-lane game to pass that info around. Sometimes, they get confused (through someone feeding a malicious BGP advertisement, or someone misconfiguring a BGP advertisement), and it's not possible to reach certain networks (and by extension, whatever resources are on those networks, like websites).

 

[pcray1231]

a way for the backbone Internet routers to become self-aware

Uh oh.

 

[JackM]

shortrod2 wrote:

Does this help?

I'll answer for him: no. Are you a Linux user?

 

[CLSports]

Reboot

 

[shortrod2]

JackM wrote:

shortrod2 wrote:

Does this help?

I'll answer for him: no. Are you a Linux user?

As a professional programmer for nearly 30 years I have been a "user" of many operating systems including Linux. Today my primary os both at home and work is Mac OS X.

As to not being helpful, suppose someone posted looking for and expert plumber saying that he had a backed up sink. Twenty guys post to use Drayno or Liquid Plumber. A plumber posts a description of how open the trap and clear it. Would the plumber's post be considered helpful?

In either case, if you are not willing to get your hands dirty, pay a professional.

 

[Number6]

While I can see smashing the Dell just on general principles, I don't think you'll find that that's the problem.
Describe your setup. Cable modem? Separate router?
I've seen this with a cable modem and linksys wireless router before. The solution was to go into the router settings, change the MAC address, and reboot everything.
You might want to give that a try.

 

[Chaz]

The relevant line is inet 192.168.4.40. This is a spoofed ip address. If your ip address starts with 192.168 it is spoofed.

Not sure what you mean by spoofed.
Not necessarily, if you are using a cable mdom to connect and or a wireless router, your IP will start with 192.168 unless you change it

 

[shortrod2]

Chaz wrote:
Not sure what you mean by spoofed.

I meant NAT or similar technology.

Chaz wrote:
Not necessarily, if you are using a cable mdom to connect and or a wireless router, your IP will start with 192.168 unless you change it

Chaz, I don't want to slam you too hard here, but you are out of your element.


Ip addresses that start with 192.168 are reserved for private networks. Routers on the internet can not forward packets to such an address.


The way this works for most home user accounts is when you connect to your ISP, you are granted a single ip address either static or more commonly dynamic through DHCP.


If you want to communicate with more than one device over the internet, you will need a ip sharing tech like NAT. Typically a wireless router that provides this layer is used. The user devices in your home (pc, cell phone, game console, tv, toaster) use ip addresses from the private range. The NAT layer keeps track of which request came from which client and proxies the request on the internet using the one and only authorized public ip address for your account. When the request comes back the NAT layer translates and forwards to the originating client.

 

[salmonoid]

And for all the offers of advice (right, wrong, useless, off-topic or otherwise), I still don't know if the OP has resolved his issue... Lots of arm chair IT professionals here ;-)

I am curious - of the respondents, who actually works in the IT field?

 

[gfen]

shortrod does, and asked qualified questions in two posts. i know this because i do, too. they weren't answered. not much to be done until they are.

shakey had this problem, too. he's posted since then. send him an PM and ask what he did. please sure you make a "PM sent!" poast so we know that a PM was sent; people on forums love that sort of thing.

 

[cryan1980]

I'm having this same issue on all my home devices. Only paflyfish.com.

My phone works fine at my brothers so I was able to read this thread and try to resolve when home

 

[cryan1980]

I just fixed my issue.


I needed to release and renew my external ip.

 

[Maurice]

cryan1980 wrote:
I just fixed my issue.


I needed to release and renew my external ip.

So how did u do that? Was it just a matter of unplugging and plugging in your modem?

 

[cryan1980]

No, Unplugging did not work when I tried

log into the router (I have verizon BTW)

"My network"

"network connections"
"broadband connection"
"settings"

"DHCP LEASE" and click release, then renew