Odd AT&T gateway issue.

[Digital Micro]

I have a client that switched to AT&T and when setting everything up I ran across an odd issue. When I connect both computers and dvr they pull a internal ip of 192.16.1.xxx. When I connect the wireless printer it pulls an ip starting with 162 which is in a range of ip's under the IP Public Subnet. When I manually configure the printers network settings it only stayed online for a few minutes. I have connected the printer via wired connection to one pc and shared it so the other will print.

Anyone else have this happen with an AT&T gateway?

 

[nlinecomputers]

Sounds like you are blaming the gateway for a problem with the printer.

 

[Digital Micro]

Sounds like you are blaming the gateway for a problem with the printer.

Not really blaming. Could be a bad printer. Just didn't know if I was having a "duh" moment and overlooking the obvious.

This is only one of three business clients with AT&T. I had one a few weeks ago that was a new install. His was switching between an ipv4 and ipv6 static public ip. I called AT&T, they said it wasn't. As of right now it still is. When it's on ipv4 the dvr remote views, when it switches to ipv6 it won't.

 

[nlinecomputers]

Slap a real firewall gateway in place, instead of that crap AT&T sells.

 

[Markverhyden]

The roll out of IPV6 has already begun in earnest. So we will have to start figuring out what goes on. Was at a customer today and as part of their update we ordered a fixed IP. According to the Comcast rep they get 56 public V6's with one public V4. At any rate it sounds like something else is going on.

 

[YeOldeStonecat]

Those gateways have a couple of DHCP services....one for private subnet, one for public subnet.
Check the settings, see how it's configured..each DHCP is fully configurable. I always have it set to pass the public to our own router..and I go from there.
They're my least liked ISP gateways...can't stand them. So many different variations based on make/model..even down to the firmware version. Just when you think you have it figured out, they change it up on ya!

 

[Digital Micro]

Those gateways have a couple of DHCP services....one for private subnet, one for public subnet.
Check the settings, see how it's configured..each DHCP is fully configurable. I always have it set to pass the public to our own router..and I go from there.
They're my least liked ISP gateways...can't stand them. So many different variations based on make/model..even down to the firmware version. Just when you think you have it figured out, they change it up on ya!

I'm actually about to go back onsite. The ATT tech came to fix the second phone line and now nothing works, voice or data. He blamed old wiring and left. It's Cat6 and I ran it 8 months ago. Sad part is he could've rewired it in 5 minutes. the network closet is on the other side of the office wall .

He won't spend for a real firewall. I can't really blame him. he has a single pos behind the vendor firewall and an office pc for logging into a portal to check numbers. He sometimes uses his laptop in the lobby

 

[YeOldeStonecat]

He won't spend for a real firewall. I can't really blame him.

Don't need a full firewall..but even just a partially decent standarized hundred dollar router. Would have avoided a call like this....thus worth it. Unfortunately we have quite a few clients with those oddball NV units from ATT/Frontier..so I've wrestled with a lot of 'em.

 

[ComputerRepairTech]

I have a client that switched to AT&T and when setting everything up I ran across an odd issue. When I connect both computers and dvr they pull a internal ip of 192.16.1.xxx. When I connect the wireless printer it pulls an ip starting with 162 which is in a range of ip's under the IP Public Subnet. When I manually configure the printers network settings it only stayed online for a few minutes. I have connected the printer via wired connection to one pc and shared it so the other will print.

Anyone else have this happen with an AT&T gateway?

You checked in the ATT gateways settings? i dont remember the exact area. If client is paying extra for a static ip he can call ATT and ask to speak to the static ip address team im not sure if they are still around but i remember having some impossible to fix issue with a static ip and they had to do something i didn't have access to in order to fix it.

 

[Digital Micro]

UPDATE : When I got onsite a few minutes passed and a new ATT guy showed up. He said the router they put in has only been available a few weeks and not everyone knows how to configure it. He said he thought it was bad and replaced it with a new one (same model) and everything works like it should. The printer even pull a 192 this time.