Solved No internet on computer port after upgrade to 16

[NDGsystems]

Hi All, yesterday one of our hosted systems was automatically upgraded to 16.
Since, all the pass through ports on the grandstream 2140 stopped forwarding internet.
Phones are connected and work well, but all computer connected to the phones computer port do not have internet.
If we disconnect a computer and connect it directly to the network switch, all works well.

Any ideas?

 

[nub]

vlan id on the computer ports on the phones? thats all i can think of.

 

[NDGsystems]

Thank you, computers and phones were on the same vlan before the upgrade. I'm assuming nothing has changed.

 

[leejor]

A quick look at Grandstream's site, for that model, seems to indicate that it has a web GUI. You should be able to log into a set and check the options, in particular, the Bridge LAN port. That may also be available through an option on the sets display. Perhaps there was a re-provisioning pushed to the set that disabled it, although I'm not sure why that would happen.

 

[NDGsystems]

good idea, checking, i'll keep you posted.

 

[NDGsystems]

In advanced:


So this happens after update to 16
3CX support, please fix it. you cannot decide to disable this port!
This is one of the only phones with 1GB port which is very useful.

Leejor - Thank you very much for your help!

 

[NDGsystems]

Well, this still does not fix the issue. PC does not get any DHCP info from the Router when connected to the PC Port on the phone, and phone PC Port is set to Enabled.
Anyone from 3CX has an idea?

 

[Mark Phillips]

I found that by default the PC port on a Grandstream GXP1782 was disabled by default - I had to enable the PC port on the phone provisioning page, setting Vlan to 1 (default) and leaving priority at 0. From memory, this is independent of any voice vlan configuration.

 

[NDGsystems]

Thank you Mark, I'll try that and keep you updated.
BTW, this is in each phone through the web interface?
Is there a way to set this to all phones using 3CX?

 

[Mark Phillips]

Yes, this was set on the Phone Provisioning tab of the extension.
As far as I am aware, you'd have to set this per extension or I guess it would be possible to edit the provisioning template to make the change globally - but you then become responsible for managing a custom template.

 

[leejor]

If you enable the port, then re-boot (power off/on), does it then work, or, does it show disabled again? If it still shows enabled, and the set was also re-provisioned, then (it would seem) the provisioning file does not affect that option.

 

[NDGsystems]

I understand, this is problematic for large installs. I'll test and update here.

 

[Jayh]

This happened to all of my Grandstream phones that had a PC connecting thru them, The were able to pull a dhcp address but not able to acces the network. I was able to resolve the issue by logging into the Server and changing the phon extension under provisioning to enable "Enable VLAN for PC PORT " it was not necessary to set the vlan.

 

[Bronston Hansen]

Ugh.
+1

 

[YiannisH_3CX]

Please note that there was a change in the template regarding this which was requested by Grandstream for the new template and firmware. I am not sure why they requested this so i would recommend contacting Grandstream directly regarding this issue.

 

[joec]

+1 same thing happening with my grandstream 1630 phones. Tried changing VLan pc port and VLan wan settings, no luck

 

[craigreilly]

I had to do this back early v15.5 when Grandstream was supported again in order for the port to work.
I am still on v15.5 so not sure if this is the permanent fix.

 

[joec]

I never left 15.5 and just started having issues over the weekend. Maybe it's a firmware issue?

 

[joec]

I never left 15.5 and just started having issues over the weekend. Maybe it's a firmware issue?

Also I am running in lightsail using stun for my provision method

 

[joec]

On v16 this was the fix for me with grandstream 1630 phones
https://www.3cx.com/community/threads/grandstream-gxp21xx-pc-port-not-enabled-by-default.54203/