Printable View
Hello, can anyone help me. I have WinXp Pro as the host computer, and want to enable internet connection sharing for my client Win2000 computer. I have rogers high speed internet. Can anyone help me configure this? I have everything set up, its just the IP part - do I set the client to obtain ip's automaticlly?, Also where do I enable ICS, on the local area network, or on my internet connection?
Thanks.
DUDE
Just go get a router and save yourself the headache(s) of ICS......
Kind of too late for that.
Any ideas? I had it working with two Win2k machines, but WinXp and Win2k don't want to cooperate.
Its a protocol problem...You need to install NetBeui on the XP box......
And Dude its NEVER too late to get a router :D
Here's how to configure ICS:
On the XP System:
1. Go to Network Connections
2. Right click your Internet connection (not the internal lan)
3. Go to the Advanced tab
4. Select "Allow other network users to connect to the internet through this system"
5. Click apply
This will not only enabled ICS, but it will configure your internal network card to IP: 192.168.0.1
On the Windows 2000 System:
1. Go to Network Connections
2. Right click your Internal LAN connection
3. Double click "TCP/IP"
4. Give the client system the IP: 192.168.0.2
5. Change the subnet to 255.255.255.0
6. Change the default gateway and primary DNS to 192.168.0.1
7. Click Apply/OK.
If you try change the IP from that level... LSASS will fail, and ICS will not function correctly. LSASS relies on the IP: 192.168.0.1 to act as a DNS gateway and router.
If you ever need to change your DNS, always change it on the client system! If you unsure if the setup is working...
On the Host System:
1. Go to start > Run
2. Type 'cmd' (without the quotes)
3. then type 'ping 192.168.0.2' (again, without quotes)
4. Press enter
If you see request time out... then you either have a firewall configured to disallow ICMP requests.. or it's just not working. If it pings... you're almost finished.
On the Guest System:
1. Go to start > Run
2. Type 'cmd' (without the quotes)
3. then type 'ping 192.168.0.1' (again, without quotes)
4. Press enter
If you see request time out... then again... you either have a firewall blocking it or the card is not enabled. If it pings the server... great! Repeat the above process but try 'ping 194.168.4.100' (without quotes)... this will try to ping the NTL's root DNS server. If it pings, but you are unable to get on the net... then it's just DNS you need to sort out. If it doesn't ping out to the net, then your server isn't acting as a router. Check cables, firewall and bandwidth settings on the NIC.
Never use the DHCP (Automatically assign IP) feature by the way! It's virtually useless anyway, and IPv6 won't help matters either! :)
Hope this helps... or have I just wasted 3 mins! :D :D ;)
Oh... Netbeui is a non-routable protocol, so trying to share anything outside the subnet is useless anyway.
You'de do better forwarding or masquerading the ports from the server to the host.. and dealing with security from just one system.
If you have to install Netbeui, please make sure you unbind 137,138 and 139 file and printer sharing... or you'll be vulnerable to nooby hackers.
Or install a firewall like Sygate or Mcafee. Steer clear of Norton if you can possibly help it.
Switching off file and printer sharing and installing the firewall is a better solution :p If there isn't a protocol there... it can't respond!
TCP Port: All TCP ports require a handshake from a service before anything can connect.
UDP Port: All UDP ports can be opened without the need for a running service to grant/deny access. These are usually classed as the more dangerous port.
Block both TCP 137 & 139... and you'll be pretty safe.
Arghh, Now I installed Xp on both computers. Things should be easy now right? No, it still refuses to work. Both the host and client computers can send packets, but not recieve them. Can this be more of a hardware problem?
VisionIT, I tried to ping 192.168.0.1 on the host and it works, but on the client it doesn't. I don't have any firewalls.
Are you using a standard network cable between the two systems?
Yes, I don't know why its not working. It used to work fine when I had both computers running Win2k Pro.Quote:
Originally posted by VisionIT
Are you using a standard network cable between the two systems?
Thats why then! :p
There are two main types of network cable...
1. 568A - 568A
2. 568A - 568B
You need type 2 or what is called a 'cross over cable'. If you try to use a standard CAT5e cable (like you are doing) the network card won't terminate... and after a few milliseconds the card will fail.
You'll probably find the network card light is red, showing an error.
Get back to me if you still can't sort it, and i'll remote connect and sort it out if you wish.
:wave:
Quote:
Originally posted by VisionIT
Thats why then! :p
There are two main types of network cable...
1. 568A - 568A
2. 568A - 568B
You need type 2 or what is called a 'cross over cable'. If you try to use a standard CAT5e cable (like you are doing) the network card won't terminate... and after a few milliseconds the card will fail.
You'll probably find the network card light is red, showing an error.
Get back to me if you still can't sort it, and i'll remote connect and sort it out if you wish.
:wave:
No no, its a standard cable, but its corssed over:bigyello: I did it as an experiment. It works I know that for sure because the networked worked perfect when I had Win2k OSs.
A little more info:
On the Host computer, I ran ipconfig, for the Local Area Connection:
DNS Suffix is blank
IP address 192.168.0.1
Subnet mask: 255.255.255.0
Deafult Gateway: Blank
on the Client comp:
DNS Suffic is blank
Autoconfig IP address 169.254.226.249
Subnet Mask: 255.255.0.0
Gateway: 192.168.0.1
Maybe there is something wrong here?
The client system should read:
IP: 192.168.0.2
Subnet: 255.255.255.0
Default Gateway: 192.168.0.1
DNS: 192.168.0.1
DO NOT USE DHCP!
If you follow my initial post... it'll work fine!
It doesn't matter what OS you have installed! If you don't configure both the server and the host... you'll never get anywhere :rolleyes: :p
I fallowed your post. I have a few questions.
on the HOST computer, Under the Internet connection, I have set Obtain Ip autmatically and obtain DNS automatically.
Then on the same HOST computer, under the LAN, I have set ip 192.168.0.1 and subnet 255.255.255.0
Is that correct?
Thanks
"On the Host System:
1. Go to start > Run
2. Type 'cmd' (without the quotes)
3. then type 'ping 192.168.0.2' (again, without quotes)
4. Press enter
If you see request time out... then you either have a firewall configured to disallow ICMP requests.. or it's just not working. If it pings... you're almost finished.
On the Guest System:
1. Go to start > Run
2. Type 'cmd' (without the quotes)
3. then type 'ping 192.168.0.1' (again, without quotes)
4. Press enter"
As of now, both these PING tests fail(timeout)
You MUST be doing something wrong m8!
You DO NOT enter 192.168.0.1 on the server... the ICS feature does that for you.
Host System:
Internet Connection: Set to DHCP
Lan Connection: Will be auto-configured when you enable ICS.
Guest System:
Lan Connection: Set IP to 192.168.0.2
Then try again.
If you are still unable to fix it... please PM me with the IP address of the internet connection.. and i'll remote connect. If these cards work, and the cabling works... there's absolutely nothing that would stop it from working.
Woohhoo, alright, its working. It was a matter of setting the connection speed for the network. It was set to 100Mbs, but that was apperantly too much, so I set it tot 10Mbs Full Duplex and it works
Thanks a lot for the help