Re: Windows XP network problem...
- From: "Tony" <wittley3231@xxxxxxxxxxx>
- Date: Fri, 1 Jul 2005 11:28:37 -0400
The purpose of win 2000/2003 was to deviate away from having to rely on
netbios name resolution. Get rid of the netbios protocol, you do not need it
and if any thing will cause security concerns and excess broadcast traffic.
Look into setting up a DHCP server utilizing DDNS to resolve host names
across multiple subnets. This is the preferred way now, is more reliable and
faster. But, if you have pre-windows 2000 machines, then you're pretty much
stuck with WINS. If this is the case, consider upgrading.
"Adam Drayer" <spam@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:evq5ekcdFHA.3048@xxxxxxxxxxxxxxxxxxxxxxx
> I assume you are using subnet masks of 255.255.255.0 which puts the
> 192.168.0.0 and 192.168.1.0 networks on different subnets. Unfortuantely,
> browsing across subnets cannot be accomplished through broadcast name
> resolution because different subnets are not in the same broadcast domain.
> You'll need to do either one of two things...
>
> 1. Use WINS (for 2 machines, I wouldn't recommend this)
> 2. Use LMHOSTS
>
> You'll have to make a static entry in each LMHOSTS file. They can be
> located in %system32%\drivers\etc
>
> Here is a KB article that explains LMHOSTS better:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;314884
>
> Here is a small excerpt:
> Windows recognizes names instead of IP addresses for network requests, and
a
> name discovery process is used to correctly route network requests with
> TCP/IP. Because the name discovery process is generally not routed by an
IP
> router, the LMHOSTS file allows Windows-based computers to use TCP/IP to
> communicate across a subnet.
>
>
> In addition to this, you'll have to verify several other things need for
> network browsing. Both computers should have 'NetBIOS over TCP/IP'
enabled.
> They should also not have Windows Firewall or other 3rd party firewalls
> configured to block MS Networking(almost all do out of the box. You can
> disable them for testing, but please re-enable them when you are done).
You
> will need 'client for microsoft networking' installed and it will also
help
> to have them in the same workgroup
>
> If you have any more questions, just shoot!
>
> --
> Hope I've helped some!
> Adam Drayer
>
>
> "fungus" <umailMY@xxxxxxxxxxxxxxx> wrote in message
> news:qEDte.45688$dr.44660@xxxxxxxxxxxxxxx
> > I've got three machines here:
> >
> > Server/Router
> > -------------
> > This machine acts as a server, it connects to
> > the Internet via a cable modem. It also has
> > Ethernet and Wifi and does Internet connection
> > sharing.
> >
> > Modem IP = auto
> > Ethernet IP = 192.168.0.1
> > Wifi IP = 192.168.1.1
> >
> > Machine A
> > ---------
> > I've got a machine "A" which connects to the
> > server via Ethernet.
> >
> > A's IP = 192.168.0.2
> > A's Gateway = 192.168.0.1
> >
> > Machine B
> > ---------
> > I've got another machine "B" which connects
> > to the server via Wifi.
> >
> > B's IP = 192.168.1.2
> > B's Gateway = 192.168.1.1
> >
> >
> > The setup works. All machines have Internet
> > access, all machines can ping each other (I've
> > edited "hosts" to fill in the IP addresses).
> >
> > The only problem is that A can't see shared
> > files on B, and B can't see shared files on A.
> > I look in "My Network Places" and the machines
> > aren't there, they can only see the server.
> >
> > How can I get A and B to see each other's files?
> >
> >
> > --
> > <\___/>
> > / O O \
> > \_____/ FTB. For email, remove my socks.
> >
> > In science it often happens that scientists say, 'You know
> > that's a really good argument; my position is mistaken,'
> > and then they actually change their minds and you never
> > hear that old view from them again. They really do it.
> > It doesn't happen as often as it should, because scientists
> > are human and change is sometimes painful. But it happens
> > every day. I cannot recall the last time something like
> > that happened in politics or religion.
> >
> > - Carl Sagan, 1987 CSICOP keynote address
>
>
.
- Prev by Date: Problem with new XP system in a Win2K workgroup
- Next by Date: Re: Problem with new XP system in a Win2K workgroup
- Previous by thread: Problem with new XP system in a Win2K workgroup
- Next by thread: Re: Add static route
- Index(es):
Relevant Pages
|
Loading
