help.. ghost in gateway and dns server???

[Guest]

This is very weird and i've never seen anything like this.

Configuration:

4 computers xp pro
1 computer xp home

tcp/ip network with ip's 192.168.0.1/24 - 0.5/24

4 computers are running firewalls.

0.1 xp firewall
0.2 - 0.4 norton firewall
0.5 no firewall

All computers have internet access trough 192.168.0.1 (internet server)

the computers 0.2 - 0.5 can see each other in my network places, but not the
0.1 computer.
the computer 0.1 can see itself in my network places, but no other computer.

the weirdest thing is that all of the 0.2 -0.5 computers have a gateway and
dns server of 192.168.1.1!!! and not as you would think 192.168.0.1. Still
they can connect to the internet. If I change it to 192.168.0.1 they cannot
acces the internet and/or see the 0.1 computer (ping, pingpath, tracert I've
tried).

Then ofcourse they can share files among each other, but not with the 0.1
computer.

I know this has something to do with the gateway and dns setting, but i am
totally confused here...

I do not know how to configure this network with a proper adressing range
and dns, gateway ip. Does someone have an option here??

 

[Steve Winograd [MVP]]

"Niels Broertjes, MCSA, Net+, A+" <Niels Broertjes, MCSA, Net+,

This is very weird and i've never seen anything like this.

Configuration:

4 computers xp pro
1 computer xp home

tcp/ip network with ip's 192.168.0.1/24 - 0.5/24

4 computers are running firewalls.

0.1 xp firewall
0.2 - 0.4 norton firewall
0.5 no firewall

All computers have internet access trough 192.168.0.1 (internet server)

the computers 0.2 - 0.5 can see each other in my network places, but not the
0.1 computer.
the computer 0.1 can see itself in my network places, but no other computer.

the weirdest thing is that all of the 0.2 -0.5 computers have a gateway and
dns server of 192.168.1.1!!! and not as you would think 192.168.0.1. Still
they can connect to the internet. If I change it to 192.168.0.1 they cannot
acces the internet and/or see the 0.1 computer (ping, pingpath, tracert I've
tried).

Then ofcourse they can share files among each other, but not with the 0.1
computer.

I know this has something to do with the gateway and dns setting, but i am
totally confused here...

I do not know how to configure this network with a proper adressing range
and dns, gateway ip. Does someone have an option here??

Many home broadband routers, especially from Linksys, have a default
LAN IP address of 192.168.1.1.

Is there a broadband router in your network setup? If so, why are you
using one of the computers as an Internet server? A cable modem or
DSL modem with an Ethernet connection can connect directly to the
router for Internet sharing.

However, a typical router can't share a dial-up connection or a USB
connection to a cable modem or DSL modem. In that case, you need to
use one of the computers as an Internet server and to use the router
as a network switch only:

1. Connect all of the computers to the router's LAN ports.
2. Don't connect anything to the router's WAN (Internet) port.
3. Disable the router's built-in DHCP server.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Eric Niewoehner]

To add to this discussion, clarification on specific network setup would
be helpful. But from what I read, one thing is apparent -- workgroup
PC's don't find each other using TCP/IP necessarily. They utilize an
older protocol called NetBIOS. If you use DNS, you will need to set up
a DNS server on your network, which none of the workstations you
described below can provide. So you are stuck with NetBIOS.

 

[Steve Winograd [MVP]]

To add to this discussion, clarification on specific network setup would
be helpful. But from what I read, one thing is apparent -- workgroup
PC's don't find each other using TCP/IP necessarily. They utilize an
older protocol called NetBIOS. If you use DNS, you will need to set up
a DNS server on your network, which none of the workstations you
described below can provide. So you are stuck with NetBIOS.

Yes, workgroups require NetBIOS for network browsing. A domain with a
computer running Windows 2000 Server or Windows Server 2003 can use
DNS for network browsing.

NetBIOS is an API (application programming interface) that runs over
one of the transport protocols: TCP/IP, IPX/SPX, or NetBEUI.

The NetBIOS specification was created by Sytec for IBM in 1983, so
it's newer than TCP/IP, which was developed in the 1970's.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Guest]

Problem solved... It was indeed a router that was the problem.

The people who owned the router, said it was a hub. Because of the fact it
was way in the back of a large closet, I didn't look at it. The man had heard
from the store were he bought the router, that he should put his "main
computer" with ICS into the WAN port... and that port had a adress off
192.168.1.1

thanks to you all