WIN2K and WINXP P2P Prob.

  • Thread starter Thread starter MBE Box and Mop Boy
  • Start date Start date
M

MBE Box and Mop Boy

Cannot map drive in WIN2K to an WINXP server on P2P, but
can by IP address. Changed WIN2K terminals, have had this
problem times before and other terminals seem to fix it,
other people on this site seem to have the same issue.
MOst of the KB articles point to domain-related problems,
most of things do not exist in retaurant POS-terminal
systems.

If someone has a solid answer for these problems I would
sure like to know it. One of the kids who just joined our
shop had told me the same problem he had at his old job;
it always "fixed" itself by the next day. The next day is
NOT going to cut it when this P2P product for restaurants
is becoming our new cash-cow. It needs to be resolved M$,
I see many references to it in the www. The workstations
do not connect, they connect, ping, and map drives by IP
address, the Network Neighborhood has only the workstation
in it, and brwosing the network only produces the lone
workstation. Great networkability!

You know M$, you may have a 95% now, but crap like this
will shrink it overtime. We sure do not have these issues
with our *NIX products.
 
MBE Box and Mop Boy said:
You know M$, you may have a 95% now, but crap like this
will shrink it overtime. We sure do not have these issues
with our *NIX products.
Click to expand...

I guess you'll have to hire competent people to install this stuff
properly,...or better yet,...just replace the equipment with that wonderful
and faultless *NIX products.

Sorry,..I guess I'm not watching how I post,..again.
 
1. Its been running for more than thirty days, its a
sudden thing.
2. One hundred *NIX sites running NT with NO workstation,
server, computer browser services and no issues; pretty
good I think.
3. If you aint got a fix don't post. It is an annoying
error that shows up at or on Murphy's clock. The customer
doesn't care, but they do see "Windows" as the problem,
they DO have a Mac sitting in their office and made the
original remark that it never has these problems.
4. The NetBIOS name, I am assuming, does not network out,
however IP addresses work fine, it is however ONLY from
that specfic NetBIOS name. The software application is
VERY specific about its licensing and its naming
conventions. There are five other stations that are
connecting just fine.

:p

MBE Box and Mop Boy
-----Original Message-----
"MBE Box and Mop Boy"
Click to expand...
in message news:[email protected]...
You know M$, you may have a 95% now, but crap like this
will shrink it overtime. We sure do not have these issues
with our *NIX products.
Click to expand...

I guess you'll have to hire competent people to install this stuff
properly,...or better yet,...just replace the equipment with that wonderful
and faultless *NIX products.

Sorry,..I guess I'm not watching how I post,..again.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


.
Click to expand...
 
Ok,...I decided to calm down and lighten up a bit.

In a Workgroup model you have to have identical accounts on all machines and
the accounts have to have identical passwords. The Workgroup name must also
match across all machines. You also have to actually have something Shared
and actually have permissions on it, you can not map a drive to something
that isn't there.
I see many references to it in the www. The workstations
do not connect, they connect, ping, and map drives by IP
address, the Network Neighborhood has only the workstation
in it, and brwosing the network only produces the lone
workstation. Great networkability!
Click to expand...

If you saw so many references to it on the WWW then you should have fixed it
yourself by now or at least have more of an idea of what is going on, or you
could have given more useful information to help solve the problem instead
of just a mindless rant.
 
Browsing is not and was never intended to be the preferred way to map a
drive in a peer to peer environment.

If you frequently restart machines, use dynamic IP addressing, and
frequently create temporary drive mappings, browsing is likely to be
problematic. If you have a lot of machines, you will flood the network with
unnecessary election, and IP discovery traffic. As a result, the master
browser may change frequently and the browse list will often be out of date
or inconsistent. The conventional way to map drives in a peer to peer
environment is to use static IPs and lmhosts files configured to load at
start-up. That way your name resolution is always accurate and you can map
drives using \\servername\sharename.

There may be valid business reasons why you do not want to use a
conventional approach, but those reasons may suggest other possibilities.
You need to tell us a lot more about your network, what you are trying to
do, and why.

If browsing is critical to your business, you may be able to resolve many
issues by configuring one machine as a master browser which is always
running, and configuring the other machines not to maintain a browse list.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP


If your business requires that you frequently create tempoary drive mappings
 
Back
Top