Boss: It's not a DNS issue its with the Processor
Me:Okay I'll spend more time trying to figure it out with the processor

An hour later:
Me: Boss, i dont think it's on the processor..
Boss: it has to be, nothing else changed.

2 hours later:
Me: Hey i fixed it was a DNS issue. Somehow it got changed to Dynamic DNS. Set static to Google's DNS after talking to the guy who set up the domain, he gave me the go ahead to get them fixed and he'll go on site and fix everything next week.
Boss: I dont understand that.. but glad it's fixed.

I've been saying DNS issue since I got the call handed to me this morning after everyone else touched it. . . ridiculous.

@EddieJennings said in What Are You Doing Right Now:

@WrCombs said in What Are You Doing Right Now:

@EddieJennings said in What Are You Doing Right Now:

@Dashrender said in What Are You Doing Right Now:

@scottalanmiller said in What Are You Doing Right Now:

We love talking to ours. But maybe that's because we use a good one.

Who do you use?

Creditcardadillo

Never heard of em .

They have a web hosting division named Hostadillo

ah you got me.
LOL thanks for humor

@EddieJennings said in What Are You Doing Right Now:

@Dashrender said in What Are You Doing Right Now:

@scottalanmiller said in What Are You Doing Right Now:

We love talking to ours. But maybe that's because we use a good one.

Who do you use?

Creditcardadillo

Never heard of em .

@WrCombs said in What Are You Doing Right Now:

@scottalanmiller said in What Are You Doing Right Now:

@WrCombs said in What Are You Doing Right Now:

On the phone with Credit Card Processors today.. Yay...

We love talking to ours. But maybe that's because we use a good one.

Bahahahaha maybe!
Just love being put on hold for 30 -45 minutes to try what they suggested, then call back. and get put on hold again.

Processor: We don't see anything from the site since Monday 8/3/2020 at 20:00 hours.
Me: then why am I being told it's your problem ?
Processor : good question..

@scottalanmiller said in What Are You Doing Right Now:

@WrCombs said in What Are You Doing Right Now:

On the phone with Credit Card Processors today.. Yay...

We love talking to ours. But maybe that's because we use a good one.

Bahahahaha maybe!
Just love being put on hold for 30 -45 minutes to try what they suggested, then call back. and get put on hold again.

On the phone with Credit Card Processors today.. Yay...

Great

@scottalanmiller said in Collision Domain - In POS:

@WrCombs said in Collision Domain - In POS:

@scottalanmiller said in Collision Domain - In POS:

@WrCombs said in Collision Domain - In POS:

@Dashrender said in Collision Domain - In POS:

@Romo said in Collision Domain - In POS:

@WrCombs Everything in the same network is being switched no matter if its wireless or wired. In order to route, you need to move the packets to a different network.

To expand upon this, just because the router is involved, doesn't mean the packets are being routed. As you describe it the SSID is put onto the same network as the server and terminals, so there is no routing happening.

I'm Guessing I just dont understand here; The access point is on a different port of the firewall, wouldn't that make it on a different network?

Not on its own, no. A port is just a physical attachment device. The ports can be routed between, or switches, or in theory hubbed (no one does this.) A Ubiquiti EdgeRouter for example you can choose to make ports switched or routed as needed.

99% of firewalls/routers use switching between their ports, but that's because 99.9% of firewalls are consumer.

Thanks for explaining that

This is TOTALLY a bullshit thing, but almost always is true.

If the ports are spread far apart physically, they are almost always routed. If they are close together, they are almost always switched. It's a visual clue that most manufacturers follow.

Ahhh Okay makes a little more sense.. haha

@scottalanmiller said in Collision Domain - In POS:

@WrCombs said in Collision Domain - In POS:

@Dashrender said in Collision Domain - In POS:

@Romo said in Collision Domain - In POS:

@WrCombs Everything in the same network is being switched no matter if its wireless or wired. In order to route, you need to move the packets to a different network.

To expand upon this, just because the router is involved, doesn't mean the packets are being routed. As you describe it the SSID is put onto the same network as the server and terminals, so there is no routing happening.

I'm Guessing I just dont understand here; The access point is on a different port of the firewall, wouldn't that make it on a different network?

Not on its own, no. A port is just a physical attachment device. The ports can be routed between, or switches, or in theory hubbed (no one does this.) A Ubiquiti EdgeRouter for example you can choose to make ports switched or routed as needed.

99% of firewalls/routers use switching between their ports, but that's because 99.9% of firewalls are consumer.

Thanks for explaining that