Sharing internet connection.

[~uNIx~]

No use
Done exactly as suggested by SuperCzar...still no luck (
The ICS is working and i can connect to net on PC I but the PC II still refuses.
The ip address given by Sify is 10.13.202.114 and i have assigneed 10.13.0.1 to NIC II on PC I.

what is your netmask on PC 1 for NIC II?

what is you netmask on PC 1 for NIC I?

What is your IP/Netmask on PC 2 for NIC I?

 

[Deus Ex Machina]

what is your netmask on PC 1 for NIC II?

what is you netmask on PC 1 for NIC I?

What is your IP/Netmask on PC 2 for NIC I?

PC I NIC II >> 10.13.0.1/255.255.255.0
PC I NIC I >> 10.13.202.114/255.255.255.0
PC II (asigned autoamtically) >> 169.254.198.89/255.255.0.0

 

[~uNIx~]

PC I NIC I >> 10.13.202.114/255.255.255.0
PC II (asigned autoamtically) >> 169.254.198.89/255.255.0.0

now how can u expect to ping PC I from PC II with that IP address/mask for PC II :S In order to ping PC I from PC II give static IP to PC II

Assuming your Pc I NIC II is connected to PC II NIC I

IP: 10.13.0.2
Mask: 255.255.255.0

If you are going to use ICS then also refer:

http://www.annoyances.org/exec/show/ics_98

 

[Deus Ex Machina]

now how can u expect to ping PC I from PC II with that IP address/mask for PC II :S In order to ping PC I from PC II give static IP to PC II

Assuming your Pc I NIC II is connected to PC II NIC I

But i was told to choose Automatic IP address assignment.
Will giving a static solve the problem?

 

[~uNIx~]

But i was told to choose Automatic IP address assignment.
Will giving a static solve the problem?

yes ICS it is automatic option shuld be selected. read my above post again

 

[Deus Ex Machina]

Nothing works.
Read the whole goddamn tutorial. But still...
I'm quiting the whole idea for sometime. Will try later. Thanx for ur help guys

 

[superczar]

Quote:
Originally Posted by superczar
is 123.123.x.x a recognized private ip address....i would suggest usin a 192.168.x.x ip configuration
secondly u make me laugh by your book knowledge. i do all practical and not just follow what i read

Unix, Kiddo...This is not a matter of bookish knowledge....
For lack of a better analogy, here is a porr yet close one:
The books say drive on the left side of the road in India...Now if the road on the right is vacant, would you drive on the right (like so many truck drivers on the Chennai Bangalore highway do :-D )
After all driving on the vacant right lane will let a practical man cover the distance in much less time? Would you ?

Similarly, 123.123.x.x etc are IP addresses assigned to uniques PCs on the web....for home/internal networks, W3C recommends 192.168.x.x, 169.254, 10.13, range IPs so as to avoid any possibility of conflicts and all DNS servers know to interpret any 192.168 etc addresses as they are meant to be , i.e Private IP LAN addresses....Just do a whois.sc to understand this better.....

Remember :no knowledge is better than half baked

Now back to Thunderbolt's issue....
Windows' DHCP server can handle only 192.168 range private IPs and not 10.13.x.x that u r using
Just assign 192.168.0.1 to ur 2nd NIC on the primary PC and set the 2nd PCs NIC to obtain IP automatically....

Also, have u made sure u r using a crossover cable and not a normal cable

 

[~uNIx~]

Similarly, 123.123.x.x etc are IP addresses assigned to uniques PCs on the web....for home/internal networks, W3C recommends 192.168.x.x, 169.254, 10.13, range IPs so as to avoid any possibility of conflicts and all DNS servers know to interpret any 192.168 etc addresses as they are meant to be , i.e Private IP LAN addresses....Just do a whois.sc to understand this better.....

thank you for the explanation it was all new to me wow..i don't understand all this sigh :rofl: i don't need to read something again or do a whois that i know since years thank you. it was u the same guy who don't know the difference between Bits and Bytes and give lame reasons of type mistake. look u are funny good
next you will say that i should not use any other port for ftp other than 21 just bcoz iana.org says so lol :rofl:

do you mean to say that if i assign 123.123.123.x/255.255.255.248 for my internal LAN and share internet connection via proxy server it will conflict. dude thats funny bcoz i use it @ home LAN for many months without any issues.

dude the broadband setup is similar to this and so is mine:

@thunderbolt i have a tutroail coming up for u on proxy server

 

[~uNIx~]

@thunderbolt

tutorial: http://techenclave.com/forums/showthread.php?goto=newpost&t=1767

 

[superczar]

it's sad whn people bicker...
1- Go read the post on Bits & Bytes closely so that u can realize it's a typo
2- I've been using 1 192.168.x.x config at my home for months...DOes that mean it's necessasirily right or wrong?
I had a hardtime setting up my home network, because of certain conflicts, so I speak frm practical experience and not theory .....Long story, posted the qstns on TA and managed to set it up part thru trial & error & majorly thru the help extended by other members.....

So some lessons from a senior (have a strong feeling though i may be wrong ....agewise, academically and experiencewise)
- Keep an open mind clear of prejudices
- Be willingto listen to others and their POV..many a times, others woudl be wrong, but you'd emerge enriched nevertheless

 

[Count_Down]

I am also using 192.168.0.x config for my home network for many years and no problems so far. I have a DLINK router which also (by default, DHCP) assigns IP in that range. The router is connected to internet using static IP.
Outside my home network, when I need to connect my laptop to another PC using a crossover cable, I manually put IPs of that range in both the PCs, make sure that they have the same workgroup, user permission etc and they network quite easily.

Just wondering what are the disadvantages of IPs of this range?

 

[Count_Down]

PC I NIC II >> 10.13.0.1/255.255.255.0
PC I NIC I >> 10.13.202.114/255.255.255.0
PC II (asigned autoamtically) >> 169.254.198.89/255.255.0.0

I think for networking to work properly, you need to give PC1 NIC II and PC II same subnet mask and IPs of the same range.

Just try:

PC I NIC II >> 192.168.0.1/255.255.255.0 and
PC II >> 192.168.0.2/255.255.255.0

 

[~uNIx~]

it's sad whn people bicker...
1- Go read the post on Bits & Bytes closely so that u can realize it's a typo

ya thats a lame reason lol

2- I've been using 1 192.168.x.x config at my home for months...DOes that mean it's necessasirily right or wrong?
I had a hardtime setting up my home network, because of certain conflicts, so I speak frm practical experience and not theory .....Long story, posted the qstns on TA and managed to set it up part thru trial & error & majorly thru the help extended by other members.....

it is u who questioned my network settings i.e 123.123.123.x telling me that i should use 192.168.0.x to avoid conflicts joke . So next time when u don't know something in depth you don't comment or give lame suggestions to atleast my replies before doing a proper research.

 

[~uNIx~]

I think for networking to work properly, you need to give PC1 NIC II and PC II same subnet mask and IPs of the same range.

Just try:

PC I NIC II >> 192.168.0.1/255.255.255.0 and
PC II >> 192.168.0.2/255.255.255.0

good basic understanding thats what i told him before

Now a little advance question

Now tell me is this correct? Can PC I ping PC II if I use this IP/Mask settings

PC I NIC II >> 192.168.0.1/255.255.255.252 and
PC II >> 192.168.0.2/255.255.255.252

What about this? Can PC I ping PC II if I use this IP/Mask settings
PC I NIC II >> 192.168.0.1/255.255.255.252 and
PC II >> 192.168.0.5/255.255.255.252

 

[Count_Down]

good basic understanding thats what i told him before

Now a little advance question

Now tell me is this correct? Can PC I ping PC II if I use this IP/Mask settings

PC I NIC II >> 192.168.0.1/255.255.255.252 and
PC II >> 192.168.0.2/255.255.255.252

What about this? Can PC I ping PC II if I use this IP/Mask settings
PC I NIC II >> 192.168.0.1/255.255.255.252 and
PC II >> 192.168.0.5/255.255.255.252

192.168.0.X/255.255.255.0 setup works for me. Haven't tried other subnet masks as never felt any reason to change that setting. You seems to be an expert. Would love to know your take on this.

 

[~uNIx~]

192.168.0.X/255.255.255.0 setup works for me. Haven't tried other subnet masks as never felt any reason to change that setting. You seems to be an expert. Would love to know your take on this.

no friend you should try different things if you want to learn. Nothing goes wrong. Just experiment with the netmasks i posted above. after that you can always revert back to original settings.

In first case:
PC I NIC II >> 192.168.0.1/255.255.255.252 and
PC II >> 192.168.0.2/255.255.255.252

Yes PC I can ping PC II. In the above network only two hosts can be connected.

In second case:
PC I NIC II >> 192.168.0.1/255.255.255.252 and
PC II >> 192.168.0.5/255.255.255.252

No PC I cannot ping PC II

Bcoz they are different:
Subnet ID: 192.168.0.0 Boradcast: 192.168.0.3 Mask: 255.255.255.252
Max Hosts: 192.168.0.1 and 192.168.0.2

Subnet ID: 192.168.0.4 Boadcast: 192.168.0.7 Mask: 255.255.255.252
Hosts: 192.168.0.5 and 192.168.0.6

How to calculate? => IPv4

Mask: 255.255.255.255
Binary: 11111111 11111111 11111111 11111111 = 32 bits

~~~
Mask: 255.255.255.0
Binary: 11111111 11111111 11111111 00000000 = 24 bits

In above the last 8 bits (0) are not covered. Therefore we get 2^8 = 256 addresses. So 256 - 256 = 0
So,
Network ID: 192.168.0.0 cannot be assigned to hosts
Hosts IP Range: 192.168.0.1 - 192.168.0.254 can be assigned to hosts
Broadcast: 192.168.0.255 cannot be assigned to hosts

~~~~
Mask: 255.255.255.252
Binary: 11111111 11111111 11111111 11111100 = 30 bits

In above the last 2 bits (0) are not covered. Therefore we get 2^2 = 4 addresses. So 256 - 4 = 252

So,
1) 192.168.0.0 is the network ID so cannot assigned to hosts
2) 192.168.0.1 IP can be assigned to host
3) 192.168.0.2 IP can be assigned to host
4) 192.168.0.3 Boradcast IP so cannot assigned to hosts

One more example:
Mask: 255.255.255.248
Binary: 11111111 11111111 11111111 11111000 = 29 bits

In above the last 3 bits (0) are not covered. Therefore we get 2^3 = 8 addresses. So 256 - 8 = 248

So,
192.168.0.0 is the network ID so cannot assigned to hosts
Range: 192.168.0.1 - 192.168.0.6 IP's can be assigned to host
192.168.0.7 Boradcast IP so cannot assigned to hosts

~~~
192.168.0.0/255.255.255.0 == CIDR(Classless Interdomain routing) format 192.168.0.0/24
192.168.0.0/255.255.255.252 == CIDR format 192.168.0.0/30
192.168.0.0/255.255.255.248 == CIDR format 192.168.0.0/29

Hope you got it

You may download this tool to understand different possible subnets:

http://www.radmin.com/download/ipcalc11.exe

 

[superczar]

pls to refer:
For all your MS bashing, i supopose u too would admit that they if they post some info on their site, it's not without merit:
source: http://www.microsoft.com/resources/...ll/reskit/en-us/prjj_ipa_sfww.asp /privip.htm

Types of IP Addresses
In order to communicate on a private network or the Internet, each computer on a TCP/IP network must be identified by a unique 32-bit IP address. Public IP addresses and authorized private IP addresses on the Internet are assigned and managed by the Internet Assigned Numbers Authority (IANA). It is also possible, although not always advisable, to assign an unauthorized private address (that is, an address of your own choosing.)

Public IP Addresses
In order for a computer to be visible on the Internet, it must be reachable through a public IP address. The IANA assigns ranges of public IP addresses to organizations that can then assign IP addresses within those ranges to individual computers. This prevents multiple computers from having the same IP address.

The public IP address for your Windows XP Professional– based computer can either be assigned through a Dynamic Host Configuration Protocol (DHCP) server available in your enterprise network, configured manually, or provided by an Internet service provider (ISP) through a dial-up connection.

Authorized Private IP Addresses
The IANA has reserved a certain number of IP addresses that are never used on the global Internet. These private IP addresses are used for networks that do not want to directly connect to the Internet, but nevertheless require IP connectivity. For example, a user wanting to connect multiple Windows XP Professional– based computers in a home network can use the Automatic Private IP Addressing (APIPA) feature to allow each computer to automatically assign itself a private IP address. The user does not need to configure an IP address for each computer, nor is a DHCP server needed. For more information about APIPA, see "Types of IP Address Assignment" later in this chapter.

Computers on a network using authorized private IP addressing can connect to the Internet through the use of another computer with either proxy or network address translator (NAT) capabilities. Windows XP Professional includes the Internet Connection Sharing (ICS) feature that provides NAT services to clients in a private network. For more information about Internet Connection Sharing, see "Connecting Remote Offices" in this book.

Unauthorized Private IP Addresses
It is possible, when there is an absolute certainty that your network will never access the Internet, to assign to a node a 32-bit unauthorized private IP address of your choosing. Keep in mind that if any Internet connectivity is ever established with any node on your network, these unauthorized private IP addresses could generate significant problems that would require you to immediately change the IP address of every node that you had assigned in this manner

Uh..BTW, I had asked you to read the comment on the b & B closely before u make any comments on that.....So it's either u r pigheaded, or you don't understand the language we use to communicate here...
Anyway, my last post on this thread...this is turning kinda slimy :no:

 

[~uNIx~]

Anyway, my last post on this thread...this is turning kinda slimy :no:

ah finally no more arguments w ith lamers good take care. it was fun reading silly stuff. wow lamers giving me links show me something new dud that i don't know

bubye

 

[nipunladha]

Hi guys, I need help from you guys... you seem to be the experts in the topic and i seem to be at the right place for help...
I have two computers at home each with one LAN card... I even have a hub... I have a sify broadband connection which i would like to share on both the comps... I want it configured in a way that at any point of time i should be able to use either one of the computers or both the computers together... i dont want to set up a server and domain by which one computer would be dependant on the other... by reading your previous discussions it seems like i will have to go in for a router... if that is the only way out how much do you think i will get a router for... thanks a ton... hope you guys reply soon
Nipun