Please help for lan network

  • Thread starter Thread starter CM
  • Start date Start date
C

CM

Hi there:
This system has two PCs both installed with Windows 2000 server.
The configuration is (both servers are in the same workgroup):

Internet -> cable ->Modem-> [NC1->ServerA ->NC2(192.168.0.1)] ->
Hub ->[NC3-> ServerB]


How to set ServerB connect to internet through ServerA?

I now set NC3 using TCP/IP, automatically obtain IP, gate way 192.168.0.1,
NetBEUI.

Now these two server can communicate using NetBEUI, but ServerB cannot
connect to Internet.

What's wrong? Anyone can help?

Thanks!

CM
 
If there is no dhcp server server b should recieve an
automatic private ip address. (starts with 169). it would
actually be easier if you got a cheap router or
configured routing and remote access and dhcp on server a.
 
I've pinged 127.0.0.1 on ServerB, it's okay, but ping 192.168.0.1, no
response.
ServerB can communicate with ServerA using NetBEUI.
Strange thing is if run ipconfig on ServerB, the result is as following:

connective specific DNS suffix: --------
autoconfiguration IP: 169.254.249.117
subnet mask: 255.255.0.0
default gateway: 192.168.0.1

Where come the autoconfiguration IP: 169.254.249.117 ?

The problem is only ServerB cannot access internet via ServerA.

anyone can help?
thanks!
CM
 
I've pinged 127.0.0.1 on ServerB, it's okay, but ping 192.168.0.1, no
response.
ServerB can communicate with ServerA using NetBEUI.
Strange thing is if run ipconfig on ServerB, the result is as following:

connective specific DNS suffix: --------
autoconfiguration IP: 169.254.249.117
subnet mask: 255.255.0.0
default gateway: 192.168.0.1

Where come the autoconfiguration IP: 169.254.249.117 ?

The problem is only ServerB cannot access internet via ServerA.

anyone can help?
Click to expand...

1) Remove NetBEUI on all your systems. You don't need it.

2) Your ServerB is set to retrieve an autoassigned IP address only
you don't have a DHCP server so it pulls an autoassigned number.
Which isn't in your logical network scheme so it can't connect.

3) Assign server B an IP address of 192.168.0.2, Netmask
255.255.255.0, Gateway 192.168.0.1.

4) Learn TCP/IP networking. There are whole courses and books on it,
and it's not a simple task, but you'll need it in the future and this
situation you're in is *very* basic TCP/IP addressing.

Jeff
CM said:
Hi there:
This system has two PCs both installed with Windows 2000 server.
The configuration is (both servers are in the same workgroup):

Internet -> cable ->Modem-> [NC1->ServerA ->NC2(192.168.0.1)] ->
Hub ->[NC3-> ServerB]


How to set ServerB connect to internet through ServerA?

I now set NC3 using TCP/IP, automatically obtain IP, gate way 192.168.0.1,
NetBEUI.

Now these two server can communicate using NetBEUI, but ServerB cannot
connect to Internet.

What's wrong? Anyone can help?

Thanks!

CM
Click to expand...
Click to expand...
 
You make sure NAT is setup before any surfing can be done
Also make sure ServerB is in the same subnet as ServerA.
I usually recommend a linksys router to make real easy.

internet--->modemcable--->linksys--->Servers

HTH
 
Thanks for the reply!
However, it did not work either. But fortunately, after I switched back
using dynamic obtain IP and set gateway to 192.168.0.1 on serverB, it
connects to Internet. I really cannot understand MS Windows.
Anywhere, the success is because of you, thank you again!
CM


Jeff Cochran said:
I've pinged 127.0.0.1 on ServerB, it's okay, but ping 192.168.0.1, no
response.
ServerB can communicate with ServerA using NetBEUI.
Strange thing is if run ipconfig on ServerB, the result is as following:

connective specific DNS suffix: --------
autoconfiguration IP: 169.254.249.117
subnet mask: 255.255.0.0
default gateway: 192.168.0.1

Where come the autoconfiguration IP: 169.254.249.117 ?

The problem is only ServerB cannot access internet via ServerA.

anyone can help?
Click to expand...

1) Remove NetBEUI on all your systems. You don't need it.

2) Your ServerB is set to retrieve an autoassigned IP address only
you don't have a DHCP server so it pulls an autoassigned number.
Which isn't in your logical network scheme so it can't connect.

3) Assign server B an IP address of 192.168.0.2, Netmask
255.255.255.0, Gateway 192.168.0.1.

4) Learn TCP/IP networking. There are whole courses and books on it,
and it's not a simple task, but you'll need it in the future and this
situation you're in is *very* basic TCP/IP addressing.

Jeff
CM said:
Hi there:
This system has two PCs both installed with Windows 2000 server.
The configuration is (both servers are in the same workgroup):

Internet -> cable ->Modem-> [NC1->ServerA ->NC2(192.168.0.1)] ->
Hub ->[NC3-> ServerB]


How to set ServerB connect to internet through ServerA?

I now set NC3 using TCP/IP, automatically obtain IP, gate way 192.168.0.1,
NetBEUI.

Now these two server can communicate using NetBEUI, but ServerB cannot
connect to Internet.

What's wrong? Anyone can help?

Thanks!

CM
Click to expand...
Click to expand...
Click to expand...
 
Back
Top