Syntax for a Private IP Address

  • Thread starter Thread starter Nathan Sokalski
  • Start date Start date
N

Nathan Sokalski

My computer is on a home network connected to the Internet through DSL.
Therefore, my computer has a private IP address rather than a public IP
address. Because I use Windows XP Professional's IIS to test my web site, I
need to know what to type in the URL to access these pages from another
computer. If I had a public IP address, I would simply enter something in
the form http://x.x.x.x/, but I do not know the syntax for entering a
private IP address. Any help would be greatly appreciated. Thanks.
 
What makes you think you have a private IP? Usually dsl is a public ip like
any isp. If your network is hooked to a router/firewall and you have the
router set to use dhcp and issue ip addresses then you would have a private
one on the computer, but the wan ip of the router would be public. If this
is your setup, you'd try to connect to the router wan ip address and then
have the router setup correctly to allow access to your website, most likely
opening port 80 or 8080 and telling it which ip the site is hosted on. If
you have no router then you'd connect to the public ip address you get from
your isp(and firewalls would have to be configured corectly). Post back with
some more details about your setup.
 
if you can go to a command prompt go to start/run and type cmd

in the command prompt type ipconfig -all this will state your ip address
 
If you mean from another computer within your home network, you'd use the
same format, http://xxx.xxx.xxx.xxx. You can find out what IP address you
have by going to a command prompt and typing ipconfig. Alternatively, you
can use the netbois name of the computer (name you gave the computer when
you installed it, ipconfig /all will show that) then you just use
http://computername

If you want to test it from your own machine, you can just use
http://localhost.

If you're trying to test it from outside you home network, you'd have to
have your internet router set to forward port 80 to your computer and hope
that your ISP allows incoming port 80 connections.

--
Posted 'as is'. If there are any spelling and/or grammar mistakes, they
were a direct result of my fingers and brain not being synchronized or my
lack of caffeine.

Mike Brearley
 
I seem to have lost some of of my previous message


If your Ip address is in th range of

10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

Then you have a private IP address otherwise it is a routable address.
If its a routable address type the IP address in the browser otherwise you
will need to find out what that IP address is of your router to your DSL
conection
 
I am not using a router. My network contains only 2 computers, which are
connected using a crossover cable. One of the computers is connected to the
DSL, and therefore has 2 network cards in it (1 to connect to the DSL, 1 for
the crossover cable) When I typed ipconfig -all at a command prompt, I
recieved the following:

C:\>ipconfig -all

Windows IP Configuration

Host Name . . . . . . . . . . . . : NJS
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection
Physical Address. . . . . . . . . : 00-07-E9-57-21-65
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.132
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::207:e9ff:fe57:2165%4
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Lease Obtained. . . . . . . . . . : Tuesday, May 25, 2004 1:31:28 PM
Lease Expires . . . . . . . . . . : Tuesday, June 01, 2004 1:31:28
PM

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling
Pseudo-Interface
Physical Address. . . . . . . . . : 80-00-39-97-BB-5C-C1-6D
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . :
3ffe:831f:4004:1952:8000:3997:bb5c:c16d
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%5
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . : mshome.net
Description . . . . . . . . . . . : Automatic Tunneling
Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-00-84
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.132%2
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\>

If there is a setting on one (or both) of the 2 computers that can be
changed that will give me a public IP address, I would like to know what it
is. I appreciate your help. Thanks.
 
The computer/network card that is connected to the dsl will have the public
ip address. In the machine with two nics try this to get your public ip
address(btw - if you have dsl you have to have a public address, that's how
it works).

My network places, view network connection, right click your dsl/internet
connectiod, status, support tab.(also the details button on the support
tab).

This should give you the public ip of that nic and the dsl connection.
 
Nathan Sokalski said in news:u$%[email protected]:
I am not using a router. My network contains only 2 computers, which
are connected using a crossover cable. One of the computers is
connected to the DSL, and therefore has 2 network cards in it (1 to
connect to the DSL, 1 for the crossover cable) When I typed ipconfig
-all at a command prompt, I recieved the following:

So on which host is your web server running? On the gateway host (with
the 2 NICs)? Or on the wholly intranet host connected using the
cross-over CAT5 cable?

If it is on your gateway host then use the public IP address assigned to
it by your ISP (since you'll have DHCP enabled on that host to get an IP
address).

If it is on your wholly intranet host then you'll somehow have to
redirect HTTP requests from your gateway host to your intranet host.
Use a router to define a virtual server which is port 80 on your
intranet host (but you'll need to connect that host to the router unless
there is some way to define a route or redirect through your gateway
host for port 80, which could be done if you run a software firewall on
it). Or use a DNS server to resolve a hostname to the intranet host's
IP address (i.e., you have to provide your own IP name resolution to
point at whatever internal hosts you want identified).
 
Try using http://NJS as I see that you have the following line showing from
ipconfig:

Host Name . . . . . . . . . . . . : NJS

--
Posted 'as is'. If there are any spelling and/or grammar mistakes, they
were a direct result of my fingers and brain not being synchronized or my
lack of caffeine.

Mike Brearley
 
I believe that would work when connecting from another computer on the
network, but I don't think it would work when connecting from other places
on the Internet. Would it?
 
My web server is running on the wholly intranet host. I read what you
suggested doing for this case, but I seemed to have a little trouble
understanding exactly what I need to do to accomplish this, especially since
there is no router involved in my network, just a crossover cable going
straight from one computer to the other. Thanks.
 
No, it wouldn't.

Go to http://www.dslreports.com/whois?java=1

If your DSL connection allows incoming port 80 connections, then using the
IP address given by the above page will show your web page.

--
Posted 'as is'. If there are any spelling and/or grammar mistakes, they
were a direct result of my fingers and brain not being synchronized or my
lack of caffeine.

Mike Brearley
 
If your going to host your own website, then you should get a
router/firewall or the possibility of you getting hacked could be high. A
webserver really needs to be configured right or it could be
hacked/exploited. I suggest you get a router/firewall and then do some
research on the net to see how to set it up and secure it.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top