Account authentication errors... with Windows

#1

Hi folks,
I've got a peculiar problem. I have a client that uses FM9 on a PC
network, with FM9 Server hosting files. Most machines are running
Windows XP. I'm a Windows know-nothing. One machine on the network
has started refusing to log in over the FM network. I get 'account &
password don't exist' errors for every account I try, including
admin. Only on that one machine. It can see the server files (using
"Open Remote"), so the connection is there, but the authentication is
getting screwed up somehow.

One thought I have is that the particular port(s) used by FM to
authenticate are not working, but the client machine doesn't have a
firewall enabled. Is there something else Windows-specific that could
be happening?

Anyone with an idea is a candidate for sainthood. Hope the recent
spam in this group hasn't driven everyone away...

TIA,
Lanse Stover

#2

In article
<97f22031-5dd2-4536-bcca-19a8a12d4349 (AT) u10g2000yqk (DOT) googlegroups.com>,
pastover <pastover (AT) gmail (DOT) com> wrote:

Quote:

Hi folks,
I've got a peculiar problem. I have a client that uses FM9 on a PC
network, with FM9 Server hosting files. Most machines are running
Windows XP. I'm a Windows know-nothing. One machine on the network
has started refusing to log in over the FM network. I get 'account &
password don't exist' errors for every account I try, including
admin. Only on that one machine. It can see the server files (using
"Open Remote"), so the connection is there, but the authentication is
getting screwed up somehow.

One thought I have is that the particular port(s) used by FM to
authenticate are not working, but the client machine doesn't have a
firewall enabled. Is there something else Windows-specific that could
be happening?

Anyone with an idea is a candidate for sainthood. Hope the recent
spam in this group hasn't driven everyone away...

TIA,
Lanse Stover

The first thing to check when passwords aren't working is that the
CapsLock key is not on.

You might also want to try typing in Microsoft Word (or whatever) to make
sure the computer is using the correct language settings for the keyboard
- you might well be typing "abc" but getting Japanese or something. This
will also show up problems with keys that may be stuck.

Helpful Harry

)

#3

On Oct 18, 8:13*pm, your.n... (AT) isp (DOT) com (Your Name) wrote:

Quote:

In article
97f22031-5dd2-4536-bcca-19a8a12d4... (AT) u10g2000yqk (DOT) googlegroups.com>,

pastover <pasto... (AT) gmail (DOT) com> wrote:
Hi folks,
I've got a peculiar problem. *I have a client that uses FM9 on a PC
network, with FM9 Server hosting files. *Most machines are running
Windows XP. *I'm a Windows know-nothing. *One machine on the network
has started refusing to log in over the FM network. *I get 'account &
password don't exist' errors for every account I try, including
admin. *Only on that one machine. *It can see the server files (using
"Open Remote"), so the connection is there, but the authentication is
getting screwed up somehow.

One thought I have is that the particular port(s) used by FM to
authenticate are not working, but the client machine doesn't have a
firewall enabled. *Is there something else Windows-specific that could
be happening?

Anyone with an idea is a candidate for sainthood. *Hope the recent
spam in this group hasn't driven everyone away...

TIA,
Lanse Stover

The first thing to check when passwords aren't working is that the
CapsLock key is not on.

You might also want to try typing in Microsoft Word (or whatever) to make
sure the computer is using the correct language settings for the keyboard
- you might well be typing "abc" but getting Japanese or something. This
will also show up problems with keys that may be stuck.

Helpful Harry *

)

Thanks for the reply, Harry. I'm afraid that neither of those are the
problem. The machine in question is used constantly/simultaneously
for other tasks, and the connection error has been happening for
weeks. The user has to move to another machine in the next room to
log into Filemaker, with her username/password the same.

I just was looking at the ports used by FM (http://sixfriedrice.com/wp/
filemaker-firewall/), and I'm reluctantly admitting that this is
probably not the problem either. It seems that 5003 and 5353 are the
only ports needed, and in any event, since the client can see the
hosted file in Open Remote, the only possible error would be if 5003
were somehow being blocked. But as I say, the client's firewall is
not even enabled.

I guess I was hoping that there might be a Windows-specific error
caused by some network-settings glitch. Or a virus?

still hoping for a saint...

- Lanse

#4

pastover <pastover (AT) gmail (DOT) com> wrote:

Quote:

I'm afraid that neither of those are the
problem. The machine in question is used constantly/simultaneously
for other tasks, and the connection error has been happening for
weeks. The user has to move to another machine in the next room to
log into Filemaker, with her username/password the same.

I'd try typing the password into a text editor anyway. I recently spent
a horrible hour trying to get back into the files I'm building until I
found out the keyboard wouldn't respond to a key when I was typing
quickly.

In order to narrow things further down, enable the guest account on of
those hosted files and try then.
--
http://clk.ch

#5

"Christoph Kaufmann" <clk (AT) tele2 (DOT) ch> wrote

Quote:

pastover <pastover (AT) gmail (DOT) com> wrote:

I'm afraid that neither of those are the
problem. The machine in question is used constantly/simultaneously
for other tasks, and the connection error has been happening for
weeks. The user has to move to another machine in the next room to
log into Filemaker, with her username/password the same.

I'd try typing the password into a text editor anyway. I recently spent
a horrible hour trying to get back into the files I'm building until I
found out the keyboard wouldn't respond to a key when I was typing
quickly.

In order to narrow things further down, enable the guest account on of
those hosted files and try then.

That's definietly worth a try. Unfortunately "network issues" can be very
difficult to find the source of.

It could of course be a corrupt verision of FileMaker (or even the operating
system), in which case a complete re-install of either / both MIGHT fix it
.... but first I would try bypassing the newtork putting a copy of the
databases onto the "naughty" computer itself and see if you can open them up
as single user using the same password(s).

If that doesn't help then perhaps try swapping the network cables or network
/ wireless cards or cables / sockets on the network router around to see if
that moves the problem to another computer. It could be a broken cable /
network card / router causing the problem.

If it's plugged into an Ethernet network, you could try physically moving
the computer to a different desk and plugging it into a wall socket you know
is working - it could be the otiginal wall socket or wiring is faulty.

Helpful Harry

)

#6

On Oct 19, 4:13*pm, "Your Name" <your.n... (AT) isp (DOT) com> wrote:

Quote:

"Christoph Kaufmann" <c... (AT) tele2 (DOT) ch> wrote in message

news:1jqmink.66auvgkd3ugwN%clk (AT) tele2 (DOT) ch...

pastover <pasto... (AT) gmail (DOT) com> wrote:

I'm afraid that neither of those are the
problem. *The machine in question is used constantly/simultaneously
for other tasks, and the connection error has been happening for
weeks. *The user has to move to another machine in the next room to
log into Filemaker, with her username/password the same.

I'd try typing the password into a text editor anyway. I recently spent
a horrible hour trying to get back into the files I'm building until I
found out the keyboard wouldn't respond to a key when I was typing
quickly.

In order to narrow things further down, enable the guest account on of
those hosted files and try then.

That's definietly worth a try. Unfortunately "network issues" can be very
difficult to find the source of.

It could of course be a corrupt verision of FileMaker (or even the operating
system), in which case a complete re-install of either / both MIGHT fix it
... but first I would try bypassing the newtork putting a copy of the
databases onto the "naughty" computer itself and see if you can open themup
as single user using the same password(s).

If that doesn't help then perhaps try swapping the network cables or network
/ wireless cards or cables / sockets on the network router around to see if
that moves the problem to another computer. It could be a broken cable /
network card / router causing the problem.

If it's plugged into an Ethernet network, you could try physically moving
the computer to a different desk and plugging it into a wall socket you know
is working - it could be the otiginal wall socket or wiring is faulty.

Helpful Harry *

)

On Oct 19, 4:13*pm, "Your Name" <your.n... (AT) isp (DOT) com> wrote:

Quote:

"Christoph Kaufmann" <c... (AT) tele2 (DOT) ch> wrote in message

news:1jqmink.66auvgkd3ugwN%clk (AT) tele2 (DOT) ch...

pastover <pasto... (AT) gmail (DOT) com> wrote:

I'm afraid that neither of those are the
problem. *The machine in question is used constantly/simultaneously
for other tasks, and the connection error has been happening for
weeks. *The user has to move to another machine in the next room to
log into Filemaker, with her username/password the same.

I'd try typing the password into a text editor anyway. I recently spent
a horrible hour trying to get back into the files I'm building until I
found out the keyboard wouldn't respond to a key when I was typing
quickly.

In order to narrow things further down, enable the guest account on of
those hosted files and try then.

That's definietly worth a try. Unfortunately "network issues" can be very
difficult to find the source of.

It could of course be a corrupt verision of FileMaker (or even the operating
system), in which case a complete re-install of either / both MIGHT fix it
... but first I would try bypassing the newtork putting a copy of the
databases onto the "naughty" computer itself and see if you can open themup
as single user using the same password(s).

If that doesn't help then perhaps try swapping the network cables or network
/ wireless cards or cables / sockets on the network router around to see if
that moves the problem to another computer. It could be a broken cable /
network card / router causing the problem.

If it's plugged into an Ethernet network, you could try physically moving
the computer to a different desk and plugging it into a wall socket you know
is working - it could be the otiginal wall socket or wiring is faulty.

Helpful Harry *

)

Those were great suggestions. I started with the Guest Account option
- and lo and behold, it worked! Then I re-installed Filemaker on the
client machine, and when I went to Open Remote, there was a
difference: now I could no longer see the remote file - the IP of the
local server showed up, but not the hosted files. Weird. So then I
connected my laptop to the ethernet cable for that machine, and...
same thing - no remote file showed up in the dialog.

So I think it's narrowed down to the ethernet cabling. They didn't
have any extras, so I'll test it tomorrow and report back. But, how
strange that the original installation of FM9 was able to see the
remote file (though without being able to authorize), and then without
touching the cable setup, it lost that ability with a clean install.
As if there were residual connection info somewhere in the caches that
allowed it to communicate. I'll never understand computers.

- Lanse

#7

In article
<c68fd6ae-210e-4662-97ac-a342629c4f70 (AT) l8g2000yql (DOT) googlegroups.com>,
pastover <pastover (AT) gmail (DOT) com> wrote:

Quote:

Those were great suggestions. I started with the Guest Account option
- and lo and behold, it worked! Then I re-installed Filemaker on the
client machine, and when I went to Open Remote, there was a
difference: now I could no longer see the remote file - the IP of the
local server showed up, but not the hosted files. Weird. So then I
connected my laptop to the ethernet cable for that machine, and...
same thing - no remote file showed up in the dialog.

So I think it's narrowed down to the ethernet cabling. They didn't
have any extras, so I'll test it tomorrow and report back. But, how
strange that the original installation of FM9 was able to see the
remote file (though without being able to authorize), and then without
touching the cable setup, it lost that ability with a clean install.
As if there were residual connection info somewhere in the caches that
allowed it to communicate. I'll never understand computers.

If you've reinstalled FileMaker Pro on the computer, then don't forget to
check FileMaker's Preferences options to make sure it's set-up to use the
proper networking protocol. FileMaker uses it's own system, not the normal
Windows / Mac OS one, so although the computer can see the server,
FileMaker may still not be able to see FileMaker Server / hosted FileMaker
databases.

Helpful Harry

)

#8

On 21/10/10 8:48 AM, pastover wrote:

Quote:

On Oct 19, 4:13 pm, "Your Name"<your.n... (AT) isp (DOT) com> wrote:
"Christoph Kaufmann"<c... (AT) tele2 (DOT) ch> wrote in message

news:1jqmink.66auvgkd3ugwN%clk (AT) tele2 (DOT) ch...

pastover<pasto... (AT) gmail (DOT) com> wrote:

I'm afraid that neither of those are the
problem. The machine in question is used constantly/simultaneously
for other tasks, and the connection error has been happening for
weeks. The user has to move to another machine in the next room to
log into Filemaker, with her username/password the same.

Helpful Harry

)

Those were great suggestions. I started with the Guest Account option
- and lo and behold, it worked! Then I re-installed Filemaker on the
client machine, and when I went to Open Remote, there was a
difference: now I could no longer see the remote file - the IP of the
local server showed up, but not the hosted files. Weird. So then I
connected my laptop to the ethernet cable for that machine, and...
same thing - no remote file showed up in the dialog.

So I think it's narrowed down to the ethernet cabling. They didn't
have any extras, so I'll test it tomorrow and report back. But, how
strange that the original installation of FM9 was able to see the
remote file (though without being able to authorize), and then without
touching the cable setup, it lost that ability with a clean install.
As if there were residual connection info somewhere in the caches that
allowed it to communicate. I'll never understand computers.

- Lanse

I think my situation a few months ago was different, but it may be worth
checking.

Is the errant client on the same subnet?
Is there antiviral software on the server?

Mine was a mac min server running a major hospital emergency department
PMS database. IT got involved at putting it on their network (it had
been on an isolated LAN). The 'no anti virus package' policy was clearly
advised to them. Access was added successfully, and then access was
expanded to include new clients in a different department. One
department (only one client windows box), could see the server but not
the db. Early question on the onsite day, is there any ati-viral
sofwtare installed? Answer: no. After working up the chain, and numerous
permutations, checked access into the server form a direct ethernet
connection from laptop into the server; bright red warning message on
the server...

The details are fuzzy after the intervening months, but the viral
software on the server, screwed login from other subnets. As I said,
probably not your issue, but maybe worth a look.

#9

On Oct 21, 6:50*pm, 105 <corti... (AT) internode (DOT) on.net> wrote:

Quote:

On 21/10/10 8:48 AM, pastover wrote:

On Oct 19, 4:13 pm, "Your Name"<your.n... (AT) isp (DOT) com> *wrote:
"Christoph Kaufmann"<c... (AT) tele2 (DOT) ch> *wrote in message

news:1jqmink.66auvgkd3ugwN%clk (AT) tele2 (DOT) ch...

pastover<pasto... (AT) gmail (DOT) com> *wrote:

I'm afraid that neither of those are the
problem. *The machine in question is used constantly/simultaneously
for other tasks, and the connection error has been happening for
weeks. *The user has to move to another machine in the next room to
log into Filemaker, with her username/password the same.

Helpful Harry *

)

Those were great suggestions. *I started with the Guest Account option
- and lo and behold, it worked! *Then I re-installed Filemaker on the
client machine, and when I went to Open Remote, there was a
difference: *now I could no longer see the remote file - the IP of the
local server showed up, but not the hosted files. *Weird. *So then I
connected my laptop to the ethernet cable for that machine, and...
same thing - no remote file showed up in the dialog.

So I think it's narrowed down to the ethernet cabling. *They didn't
have any extras, so I'll test it tomorrow and report back. *But, how
strange that the original installation of FM9 was able to see the
remote file (though without being able to authorize), and then without
touching the cable setup, it lost that ability with a clean install.
As if there were residual connection info somewhere in the caches that
allowed it to communicate. *I'll never understand computers.

- Lanse

I think my situation a few months ago was different, but it may be worth
checking.

Is the errant client on the same subnet?
Is there antiviral software on the server?

Mine was a mac min server running a major hospital emergency department
PMS database. IT got involved at putting it on their network (it had
been on an isolated LAN). The 'no anti virus package' policy was clearly
advised to them. Access was added successfully, and then access was
expanded to include new clients in a different department. One
department (only one client windows box), could see the server but not
the db. Early question on the onsite day, is there any ati-viral
sofwtare installed? Answer: no. After working up the chain, and numerous
permutations, checked access into the server form a direct ethernet
connection from laptop into the server; bright red warning message on
the server...

The details are fuzzy after the intervening months, but the viral
software on the server, *screwed login from other subnets. As I said,
probably not your issue, but maybe worth a look.

Thanks, I'll check that. At this point I'm still frustrated - after
the reinstall of FM 9 on the client, they can see the server with Open
Remote > Local Hosts, but not the hosted files. If I use the same
ethernet connection with my laptop, I have no problems, so it's not
the cabling.

per Helpful Harry:
If you've reinstalled FileMaker Pro on the computer, then don't forget
to
check FileMaker's Preferences options to make sure it's set-up to use
the
proper networking protocol. FileMaker uses it's own system, not the
normal
Windows / Mac OS one, so although the computer can see the server,
FileMaker may still not be able to see FileMaker Server / hosted
FileMaker
databases.

My understanding of the client FM Preferences is that the Sharing
dialogs refer to local files hosted by the client, not remote files
accessed by the client. Having said that, I've tried turning on FM
sharing on the client, and it doesn't affect the problem.

- Lanse

#10

In article
<05657aaf-9a2b-4288-8cb9-8883be4ae4d4 (AT) t1g2000yqd (DOT) googlegroups.com>,
pastover <pastover (AT) gmail (DOT) com> wrote:

Quote:

Thanks, I'll check that. At this point I'm still frustrated - after
the reinstall of FM 9 on the client, they can see the server with Open
Remote > Local Hosts, but not the hosted files. If I use the same
ethernet connection with my laptop, I have no problems, so it's not
the cabling.

Since it works on the laptop with that network connection and the other
computers on the network are working, the problem is obviously with the
computer itself.

It could be a faulty network card / network socket on the computer, but
since it can see FileMaker Server that seems unlikely.

As someone else suggested, it could be a security / anti-virus application
setting which is blocking certain ports, but again I would think you would
not see FileMaker Server at all.

It may still be a FileMaker Preference Application setting that needs to
be set (or reset) or even a corrupt Perferences file that needs deleting
(I don't know where in the Windows filing system that file is stored
though).

I dont know if it's possible for FileMaker Server to block certain
machines / users itself.

Quote:

per Helpful Harry:
If you've reinstalled FileMaker Pro on the computer, then don't forget
to check FileMaker's Preferences options to make sure it's set-up to
use the proper networking protocol. FileMaker uses it's own system,
not the normal Windows / Mac OS one, so although the computer can see
the server, FileMaker may still not be able to see FileMaker Server /
hosted FileMaker databases.

My understanding of the client FM Preferences is that the Sharing
dialogs refer to local files hosted by the client, not remote files
accessed by the client. Having said that, I've tried turning on FM
sharing on the client, and it doesn't affect the problem.

I'm not actually sure about the newer versions of FileMaker, but in my old
version there's an option in the Preferences -> Application to set the
Network Protocol. This has to be set the same for all copies of FileMaker
on the network. Admittedly in my version of FileMaker the choices are
"AppleTalk" and "TCP/IP", but AppleTalk has been phased out, so this
setting my no longer exist.

The Sharing settings are different and are used to basically make a normal
copy of FileMaker act as a server / host for the database.

Helpful Harry

)