How can I view the Private Networks that I am connected to?

[font=tahoma]I would like know how to view the Private Networks that I am connected to.


I can view mine by clicking Firewall, Common Tasks, My Network Zones.

I think drragostea asked for other option =) Not just to look at existing Network Zones, but “highlight” Zones, wich he is connected to at this moment. If so - there is no such opportunity. May be it is a good wish, so try to post it in “CIS - Wishlist- Firewall (or GUI)”

exproff, so you’re saying that I should post this in another forum?

I’m confused. When I first started my modem after a reformat (long ago) Comodo prompted me that a new Private Network was detected.

I want to know how I can view that.

I’ve done what buttoni said, but it doesn’t really fill the spot.

[font=tahoma]Don’t want this thread to get lost. :THNK

Hi, drragostea

I don’t think what you are asking for exists.

You computer will only be on one network at a time.
When you reset your modem you lost your internet connection.
When it restarted, the modem and PC renegotiated your IP address.
The firewall saw No Network Connection,
Then New Network Connection.
(which can be a good thing to know. Windows by default is a Networking Wh*re (rhymes with Oar))

If you want to see your current IP address go to start>run type in cmd then at the command prompt
type ipconfig

Hope this helps

[font=tahoma]Bad Frogger, I couldn’t agree better, but I can’t get anything better than Windows T.T. Linux is unfamiliar to me hehe.

Well, I think you may be right. I only reason I brought this up is because there were two Private Network prompts during the past 6 months. One when I first started my modem after a reformat and two when it was out of nowhere.

Well I have one off-topic question. Why does my IP in “ipconfig” (I’m assuming that it is my Internal) different from the one in the web (Dynamic)? Wait… Er. I know a random IP is distributed to me from a “pool”, but why the difference (one in cmd and one in the web).

If you have one in ipconfig and a different one from the web.
That would indicate you are behind a router.

The internal IP should start with either 192.168.. or 10.0..
These are from reserved address ranges for private networks.
Communication to/from these addresses can’t get past a router without NAT (network address translation).

You aren’t connected by wireless are you? This adds a few more wrinkles regarding leaving one network and joining another.

Bottom line… Behind a router having a private and a public IP address is normal.
If you don’t have a router and have two addresses, something is very abnormal and requires investigation.


[font=tahoma]I’m using a router, so there’s nothing wrong. Yes, the Internal IP starts with 192.168.
So who uses NAT basically? I do not have Wireless Internet.

Your router,… allmost all routers use NAT, all are capable I believe.
It is part of routing (directing) the flow of packets (info) between networks.

Probably the simplest way to get it would be to think that if you got a group
of computers and connected them to your router.
They would be all networked and with their own individual Private IP Addresses,
they could communicate with each other no problem.
The router knows where to send every packet.
(each packet has a header like you would address an envelope)
To: Who, Where From: Who,Where
For the computer It would be
To: Port, Protocol, IP Address From: Port, Protocol, IP Address
Your router keeps a table, It knows the IP Address of each device
on each connection. (it gave them out).

So say your PC1 at sends a packet to your PC3 at
PC1 doesn’t know where PC3 is connected, all it knows is that to get anything
anywhere outside of itself it has to go to the router. (no device is aware of any
device beyond it’s gateway or next hop so to speak.)
The router gets the packet from PC1 sees that it’s for looks at the
routing table, says I know to chuck that packet at connection of PC3.

PC3 will deal with the packet depending on software firewall, listening applications,
and what not.
If it responds the exact same procedure repeats (including levels of awareness)
in the other direction. This is straight up routing, directing the flow of traffic within
a network.

Now imagine there are hundreds of millions of computers, and probably billions of other
networked devices all told. And they all need an address, but the IPv4 protocol only allows
for say 4 billion total available address spaces.
Then you take away from that huge swaths of address ranges that are reserved for various
purposes ie scientific research, military, government, the private ranges, etc.
OOOps we’re out out of addresses and we just barely started to build a world wide network.

So the true brilliance of the Internet was to multiply the available address space by the nth
degree by not having a network of interconnected machines, but a network of interconnected
networks. Each small network (networks are defined by routers, got a router = got a network)
is connected upstream to another network and becomes a part of a larger group of globally
interconnected networks. Internet.

So imagine the clusterf*ck when there are tens or hundreds of millions of devices using the same addresses on private networks.
My computer at say has no idea in the universe where your
computer with the same address is or isn’t located. The private addresses become irrelevant
beyond a router (outside of your private network).

NAT in action - My PC and your PC are actively communicating back and forth, we already have established a connection say through file sharing or a game whatever.
A packet leaves my machine, with packet header addressed to your Public IP Address, using
whatever protocol, aimed at whatever port.
From (return address) says, use whatever protocol, and I will await your response
on whatever port.
My router reads the packet header and knows that your Public IP isn’t on my network so it
would chuck the packet at it’s default gateway upstream into the greater bigness or to the
network connection of my ISP’s router that defines the sub network my Public IP belongs to.
BUT WAIT The return address won’t fly, that Private IP can’t go past a router either direction.

So finally NAT to the rescue it re writes the packet header so the return address is my Public IP and therefore routable address. And makes note in the routing table that a request from on connection PC3 was sent to your Public IP. And so any packets in response
ie containing your Public IP in the from field. Shall have their header info re written accordingly
and chucked at the PC3 connection. This happens constantly at both ends of almost all

Holy ■■■■ I’m gonna have to past this one on my page.

PS. Even with NAT and subnetting, we are still running out of Public IPv4 Address spaces.
So they have developed IPv6 with a much larger string of numbers which will provide
for billions and billions of times more available Public IP Addresses.

Clear as mud ?

O.O It sure is. Clear as water. But I’m gonna need to re-read it again 100x to fully understand it.
I’ll try to summarize it the best I can.

So communication from one computer cannot go to another computer without a router?
Routers allow you to connect to the Internet and gives you an IP address. Router=you have a network.

So routers “translate” data that is understandable by other computers?

Overall networking is complex.

And as evidenced by my previous post, hard to explain.

A slow re read (especially since I type so slow) should help along with this.

“So communication from one computer cannot go to another computer without a router?”
No, two computers can communicate seamlessly as long as they have IP Addresses from
the same group of addresses. ie. they belong to the same network.
You could connect two PC’s by cable with no router, manually set their IP addresses
to say and and share (communicate) no problems.
In this type of scenario, adding a router just simplifies everything by automatically setting up
the IP’s and keeping track of which packets go to which connections. And by allowing for
more than just 2 PC’s to be connected in the same way as a switch or hub.

“So routers “translate” data that is understandable by other computers?”
The only translating that happens is translating from Private IP addresses (non routable)
on outgoing (leaving your private network) packets to Public IP addresses (routable) so that
packets can go out on the public networks and be passed along from network to network
(router to router) till they get to where you sent them.
The replies are sent back to your Public IP address which is really your routers external address.
Then your router translates the public address back to the private address of whichever of the PC’s on your network that sent the request using the NAT table the router stores.

To try to be more precise and simplify more,
NAT translates (maps) multiple private IP addresses to One public IP address. - outgoing
NAT translates (maps) a single public IP address back to multiple private IP addresses. - incoming.

Better ?

Result: Clear as mud.

:■■■■ Thanks Frogger. You were a great help. I’m going to bookmark this thread.

Best regards,