Author Topic: 192.168.0.1 internet shared connection not working for subnet?  (Read 19577 times)

0 Members and 1 Guest are viewing this topic.

Offline nat1

  • Jr. Member
  • **
  • Posts: 46
I loved my 4 version and got 5 after 3 year. I had nothing but problems getting my shared internet connection to work -- and yes, it is still not working.

Any suggestion  ???

No tech support from avast (I tried that with a ticket some days ago.)  :-X They must be working on getting the bugs out...

Also no info in any of the help files....
« Last Edit: April 13, 2010, 06:20:16 PM by nat1 »

Offline Cahya Legawa

  • Sr. Member
  • ****
  • Posts: 386
  • Oh, here we are again.
    • My Log
Re: did I just pay $$$ for a beta?
« Reply #1 on: April 01, 2010, 03:49:26 PM »
nat1,

There were some people who has a similar problems like you, please check another part of the forum. I don't know what exactly going on, since my avast 5 works fine by any networks (dial-up, LAN, Wifi all fine).

The forum here: http://forum.avast.com/index.php?topic=57844.0;topicseen may give some clues for you.

Regards,
Cahya.
Avast Ultimate (Bundle). Windows 10, Android, iOS.

Offline nat1

  • Jr. Member
  • **
  • Posts: 46
Re: did I just pay $$$ for a beta?
« Reply #2 on: April 01, 2010, 05:30:54 PM »
No, this did not help. It is true that I installed avast 5 internet sec. over avast 5 free. Avast 5 internet sec prompted me to first uninstall avast 5 free - which I did, and after that installed avast 5 internet sec. over it.

Also, my modem works fine. If I disable the firewall see the internet - but this cant be the answer  :-\
« Last Edit: April 04, 2010, 05:20:27 PM by nat1 »

Offline Cahya Legawa

  • Sr. Member
  • ****
  • Posts: 386
  • Oh, here we are again.
    • My Log
Re: did I just pay $$$ for a beta?
« Reply #3 on: April 02, 2010, 02:32:08 AM »
Hi nat1,

Did you uninstall avast using control panel or avast uninstaller: http://www.avast.com/uninstall-utility
Avast Ultimate (Bundle). Windows 10, Android, iOS.

Offline nat1

  • Jr. Member
  • **
  • Posts: 46
Re: did I just pay $$$ for a beta?
« Reply #4 on: April 04, 2010, 05:17:25 PM »
Yes - did the uninstall and reinstall, but I still can not see the internet.

My problem is: I can ping my server internally just fine, which has the shared internet connection; so 192.168.0.3 is seeing 192.168.0.1 (my server with the internet connection) but 192.168.0.3 has no access to the internet (google.com)  :-\

I must mention here that I am hosting my own website and DNS server, but that should not make a difference.

I have been trying different settings, but nothing is working. ANY help would be very much appreciated as tech support is taking for ever to get back to me. :(
« Last Edit: April 04, 2010, 05:23:10 PM by nat1 »

Offline Cahya Legawa

  • Sr. Member
  • ****
  • Posts: 386
  • Oh, here we are again.
    • My Log
Re: 192.168.0.1 shared connection not working in subnet?
« Reply #5 on: April 05, 2010, 02:53:01 AM »
nat1,

I'm sorry, this would be outside my expertise. Lets wait other forum members give their opinion.
Avast Ultimate (Bundle). Windows 10, Android, iOS.

Offline mkis

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1620
Re: 192.168.0.1 shared connection not working in subnet?
« Reply #6 on: April 05, 2010, 05:02:35 AM »
yes the problem appears with the connection - is inside NAT, is that correct?

I'm not sure about 0 in yr address - 192.168.0.1 - is this indicate no internet connection?

For now - have you tried netstat command, and also NSLOOKUP - run the ? after command for switch options
Avast7 Free, MBAM (on demand), MVPS Hosts

Intel DG41TY, Windows 7 Ultimate, IE9, Google Chrome, 4 GB ram, Secunia PSI, ccleaner, Foxit Reader, Faststone Image viewer, MWSnap.

Offline nat1

  • Jr. Member
  • **
  • Posts: 46
Re: 192.168.0.1 shared connection not working in subnet?
« Reply #7 on: April 05, 2010, 05:38:41 PM »
The 0 in 192.168.0.1 has nothing to do with it. Turing off the firewall in avast 5 and turning on the firewall in Win XP x64/2003 makes it works just fine. (This is standard. How to share an internet connection on LAN: http://hubpages.com/hub/How-to-share-an-internet-connection-on-LAN)

I REALLY NEED TO GET THIS TO WORK IN THE NEXT COUPLE DAYS.

===============================
Avast Firewall is ON
===============================

NSLOOKUP on system Server 192.168.0.1 is giving me:
Default Server:  dnsr1.sbcglobal.net
Address:  68.94.156.1

netstat on  Server 192.168.0.1
Active Connections
  Proto  Local Address          Foreign Address        State
  TCP    myserver:1029           myserver:3306           ESTABLISHED
  TCP    myserver:1030           myserver:3306           CLOSE_WAIT
  TCP    myserver:1032           myserver:3306           CLOSE_WAIT
  TCP    myserver:1033           myserver:3306           ESTABLISHED
  TCP    myserver:1060           myserver:1061           ESTABLISHED
  TCP    myserver:1061           myserver:1060           ESTABLISHED
  TCP    myserver:1062           myserver:1063           ESTABLISHED
  TCP    myserver:1063           myserver:1062           ESTABLISHED
  TCP    myserver:1867           myserver:53053          ESTABLISHED
  TCP    myserver:1868           myserver:53053          ESTABLISHED
  TCP    myserver:2095           myserver:3306           ESTABLISHED
  TCP    myserver:3306           myserver:1029           ESTABLISHED
  TCP    myserver:3306           myserver:1033           ESTABLISHED
  TCP    myserver:3306           myserver:2095           ESTABLISHED
  TCP    myserver:53053          myserver:1867           ESTABLISHED
  TCP    myserver:53053          myserver:1868           ESTABLISHED
  TCP    myserver:netbios-ssn    subnet3:1057              ESTABLISHED
  TCP    myserver:ms-wbt-server  subnet3:1054              ESTABLISHED

---------------------------------
NSLOOKUP on 192.168.0.3 is giving me:
Default Server: myserver.myworkgroup.net
Address: 192.168.0.1

netstat on 192.168.0.3
Active Connections
  Proto  Local Address          Foreign Address        State
  TCP    sutnet3:1800              localhost:27015        ESTABLISHED
  TCP    sutnet3:1802              localhost:5354         ESTABLISHED
  TCP    sutnet3:1803              localhost:5354         ESTABLISHED
  TCP    sutnet3:1804              localhost:5354         ESTABLISHED
  TCP    sutnet3:1805              localhost:5354         ESTABLISHED
  TCP    sutnet3:4411              localhost:4412         ESTABLISHED
  TCP    sutnet3:4412              localhost:4411         ESTABLISHED
  TCP    sutnet3:4413              localhost:4414         ESTABLISHED
  TCP    sutnet3:4414              localhost:4413         ESTABLISHED
  TCP    sutnet3:4467              localhost:4468         ESTABLISHED
  TCP    sutnet3:4468              localhost:4467         ESTABLISHED
  TCP    sutnet3:4470              localhost:4471         ESTABLISHED
  TCP    sutnet3:4471              localhost:4470         ESTABLISHED
  TCP    sutnet3:5152              localhost:1448         CLOSE_WAIT
  TCP    sutnet3:5354              localhost:1802         ESTABLISHED
  TCP    sutnet3:5354              localhost:1803         ESTABLISHED
  TCP    sutnet3:5354              localhost:1804         ESTABLISHED
  TCP    sutnet3:5354              localhost:1805         ESTABLISHED
  TCP    sutnet3:27015             localhost:1800         ESTABLISHED
  TCP    sutnet3:1054              myserver.myworkgroup.net:3389  ESTABLISHED
  TCP    sutnet3:1057              myserver.myworkgroup.net:netbios-ssn  ESTABLISHED
« Last Edit: April 05, 2010, 06:49:57 PM by nat1 »

Offline nat1

  • Jr. Member
  • **
  • Posts: 46
Re: 192.168.0.1 shared connection not working in subnet?
« Reply #8 on: April 05, 2010, 06:05:34 PM »
Disabling Firewall in avast 5 and enabling it in Win will add five more line to the netstat output in system 192.168.0.3 (NOTE: this is when it works, and I can establish internet connection from my subnet - turning avast Firewall on is not letting me see the internet from my subnet)

===============================
Avast Firewall is OFF (Win Firewall is ON and it works)
===============================

subnet3 - new lines only
Active Connections
  Proto  Local Address          Foreign Address        State
  TCP    sutnet3:1108              localhost:12080        ESTABLISHED
  TCP    sutnet3:12080             localhost:1108         ESTABLISHED
  TCP    sutnet3:kpop              lax04s01-in-f104.1e100.net:http  ESTABLISHED
  TCP    sutnet3:1110              px-in-f139.1e100.net:https  ESTABLISHED
  TCP    sutnet3:1057              myserver.mshome.net:netbios-ssn  ESTABLISHED

server
Proto  Local Address          Foreign Address        State
  TCP    myserver:2602           s15333091.mailshell.net:http  TIME_WAIT
  TCP    myserver:2603           s15313536.mailshell.net:http  TIME_WAIT
  TCP    myserver:2610           s15282716.mailshell.net:http  TIME_WAIT
  TCP    myserver:1029           myserver:3306           ESTABLISHED
  TCP    myserver:1030           myserver:3306           CLOSE_WAIT
  TCP    myserver:1032           myserver:3306           CLOSE_WAIT
  TCP    myserver:1033           myserver:3306           ESTABLISHED
  TCP    myserver:1060           myserver:1061           ESTABLISHED
  TCP    myserver:1061           myserver:1060           ESTABLISHED
  TCP    myserver:1062           myserver:1063           ESTABLISHED
  TCP    myserver:1063           myserver:1062           ESTABLISHED
  TCP    myserver:1867           myserver:53053          ESTABLISHED
  TCP    myserver:1868           myserver:53053          ESTABLISHED
  TCP    myserver:2095           myserver:3306           ESTABLISHED
  TCP    myserver:3306           myserver:1029           ESTABLISHED
  TCP    myserver:3306           myserver:1033           ESTABLISHED
  TCP    myserver:3306           myserver:2095           ESTABLISHED
  TCP    myserver:53053          myserver:1867           ESTABLISHED
  TCP    myserver:53053          myserver:1868           ESTABLISHED
  TCP    myserver:pop3           sutnet3:1274              TIME_WAIT
  TCP    myserver:pop3           sutnet3:1278              TIME_WAIT
  TCP    myserver:pop3           sutnet3:1282              TIME_WAIT
  TCP    myserver:pop3           sutnet3:1290              TIME_WAIT
  TCP    myserver:pop3           sutnet3:1293              TIME_WAIT
  TCP    myserver:pop3           sutnet3:1294              TIME_WAIT
  TCP    myserver:ms-wbt-server  sutnet3:1054              ESTABLISHED

One would think that clicking the "Internet Connection Sharing mode" inside the Firewall Policies would add these 4 lines  ???

Do I need to manually add these lines as Packet Rules? And if so how?
« Last Edit: April 05, 2010, 07:00:58 PM by nat1 »

Offline mkis

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1620
Re: 192.168.0.1 shared connection not working in subnet?
« Reply #9 on: April 05, 2010, 07:20:57 PM »
hxxp://hubpages.com/hub/How-to-share-an-internet-connection-on-LAN

The link you gave is blocked by hostsfile  - 127.0.0.1  hubpages.com
I'm not sure why

Also win XP 64/2003 - not sure about this, but if workaround works and you are inside a firewall?

What about others you are sharing with? same problem?
Avast7 Free, MBAM (on demand), MVPS Hosts

Intel DG41TY, Windows 7 Ultimate, IE9, Google Chrome, 4 GB ram, Secunia PSI, ccleaner, Foxit Reader, Faststone Image viewer, MWSnap.

Offline nat1

  • Jr. Member
  • **
  • Posts: 46
Re: 192.168.0.1 shared connection not working in subnet?
« Reply #10 on: April 05, 2010, 07:53:40 PM »
the link is working for me (removed cookies and it is still working)

What about others you are sharing with? same problem?
same problem
« Last Edit: April 05, 2010, 07:56:37 PM by nat1 »

Offline mkis

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1620
Re: 192.168.0.1 shared connection not working in subnet?
« Reply #11 on: April 05, 2010, 08:13:12 PM »
Here is a basic article anyway

http://compnetworking.about.com/od/routers/g/192_168_0_1_def.htm

Quote
The IP address 192.168.0.1 is the default for certain home broadband routers, principally various D-Link and Netgear models. This address is set by the manufacturer at the factory, but you can change it at any time using the network router's administrative console.
Avast7 Free, MBAM (on demand), MVPS Hosts

Intel DG41TY, Windows 7 Ultimate, IE9, Google Chrome, 4 GB ram, Secunia PSI, ccleaner, Foxit Reader, Faststone Image viewer, MWSnap.

Offline nat1

  • Jr. Member
  • **
  • Posts: 46
Re: 192.168.0.1 shared connection not working in subnet?
« Reply #12 on: April 06, 2010, 05:20:35 PM »
Hi mkis

Thanks, I know how to set it up (read the post all the way through) - what I don't know is how to make it work in Avast 5.

Avast 5 Firewall is disabling my internal network setup!

HELP !!!    Please...



Offline mkis

  • Avast Evangelist
  • Super Poster
  • ***
  • Posts: 1620
Re: HELP!!! - 192.168.0.1 shared connection not working in subnet?
« Reply #13 on: April 06, 2010, 06:13:22 PM »
I only posted that article because yr link is being blocked by my hostsfile - 127.0.0.1  hubpages.com
- plus maybe some clues for you in the article anyway - try reading it all the way through

Unfortunately I am not there in front of yr computer(s)
- but firewall disabling an internal network is something I have not experienced anyway

Also windows XP 64 + firewall - if workaround works and you are inside a firewall? Surely that good enough for the interim
I have an XP64 computer here but unfortunately is not supported by my wireless modem - just one of those things  ???

You did turn yr Windows firewall off? And yr avast firewall is recognising the internet connection (router)?
Really, provide as much of the procedure that you followed when you set up yr avast module and registered through yr product key.
Avast7 Free, MBAM (on demand), MVPS Hosts

Intel DG41TY, Windows 7 Ultimate, IE9, Google Chrome, 4 GB ram, Secunia PSI, ccleaner, Foxit Reader, Faststone Image viewer, MWSnap.

Offline nat1

  • Jr. Member
  • **
  • Posts: 46
Re: HELP!!! - 192.168.0.1 shared connection not working in subnet?
« Reply #14 on: April 06, 2010, 08:19:23 PM »
I just got this from Avast tech-support:

Quote
"This ticket was now assigned to our second-level technical support department. They will try to simulate the problem and find the solution. If they need some special information, they will contact you again.

Please keep in mind that the process may take some time (one week approximately, usually less), so please be patient."


To mkis's question:
Quote
And yr avast firewall is recognizing the internet connection (router)?

I am not too sure how avast would see this router. It is not an external box or so. I am using two connections - one for my internet and one for my subnet that goes to a hub from which I have many computers hocked up to.