Hi Russ,

I did mention it on the original/first posting. I tried the server name
with & without backslahes, the fax name with & without backslashes, and
server\fax with and without the leading backslashes. It made no difference.

"Russ Valentine [MVP-Outlook]" wrote in message
...
Not sure what you're saying. You should enter only the faxname, no
severname, no backslashes whatsoever. And if you tried it already, why
didn't you say so?
If you have, you're problem cannot be reproduced by the developers, so
I'll notify them.
--
Russ Valentine
[MVP-Outlook]
"CoDer" wrote in message
...
Thanks for the suggestion, but had tried that already
\\servername
servername
\\servername\faxname
servername\faxname
faxname
\\faxname

All give the same result- the "no permission" message, with no
opportunity to enter and appropriate logon

"Russ Valentine [MVP-Outlook]" wrote in message
...
Try losing the backslash on your path statement when configuring the Fax
Account.
--
Russ Valentine
[MVP-Outlook]
"CoDer" wrote in message
...
I had added "Everyone" permissions to the fax server on Server 2003. I
even created a user account on Server 2003 with the same name & password
as the Vista user (although their SID's would have been different, since
the Vista user is not the Domain user on the Server). None of that made
a difference.

Although I've seen similar issues reading through the group, I haven't
come across the same type of scenario - most that deal with domains are
talking about SBS, which is slightly different than the standard
Windows Server. But none of the things they've tried have made a
difference on my end.

I think the part that makes this more troublesome is that it simply
says you have no permission, without giving you an opportunity to enter
appropriate credentials. As I mentioned on the posting, I am able to
add the fax server as one of my printers by adding a network printer
through "Add new printer". At the point that I'm adding that new
printer, it does prompt me for appropriate server crendentials, and
then the printer gets mapped. But if I try to use that printer, it
takes me to the step in Windows Fax and Scan where you need to create
the Fax account (even though I wasn't purposefully trying to use Fax
and Scan), and we're back to square one where it just tells you there's
no permission, without the option to provide credentials...

In short, after trying all kinds of options, this is what the behavior
appears to be:

1) Any printing done to a fax printer is forced to go through Windows
Fax and Scan (that is, even if you're not using Vista's built-in fax
print driver). Or, at least, another MS fax printer driver (like the
one from Server 2003) gets recognized by Vista as a fax printer driver
and forces it to go through Windows Fax and Scan.

2) If you're going through Windows Fax and Scan, a Fax account must be
created. And in creating that account, if there is any kind of
permission issue, you have no way of entering an appropriate
user/password for accessing or to allow use of the printer.

I can't see that being the case, as it would be so terribly restrictive
and a big step backwards, so I must be missing something! But at this
point, what I've done so far points in that direction.

As far as the PC not being on the Domain, unfortunately it cannot be
added to the domain. But I can map the printer to the PC by providing
an appropriate domain logon when I map it, so it doesn't look like the
domain is blocking any and all clients that are not on the domain.

"Russ Valentine [MVP-Outlook]" wrote in message
news Lots of folks have had similar issues (as you can see by reading the
group). I'm wondering if the problem is that the client isn't on the
domain. Have you checked the permission settings in the Security Tab?
--
Russ Valentine
[MVP-Outlook]
"CoDer" wrote in message
...
I am running Vista Business, and am trying to setup faxing with
Vista's built-in Windows Fax and Scan. I do not have a modem, and so
I'm trying to connect to the fax on a Windows Server 2003 R2 server.
This is a "standard" Server 2003, that is, it is *not* SBS (Small
Business Server).

The server is a domain controller, but the Vista PC is not on the
domain. However, both computers are on the same local network/subnet.
On Vista I can map a drive that's on the server (providing the proper
server credentials). I can even "Add new printer" to Vista by
selecting network printer and entering the server address & shared
fax name, then entering the proper server credentials. So this rules
out any network issues, and at least mostly rules out authentication
issues (since I'm able to connect to the server disk and printer
resources if I provide a server administrator logon).

However, from Vista's "Windows Fax and Scan", when I try to create a
fax account, it prompts me for the server name, and when I enter the
server, it tells me that I don't have the appropriate permissions and
to contact the fax administrator. This happens whether I enter
\\servername, \\servername\faxname, servername, faxname, \\faxname.
Also, I have made sure to run Windows Fax and Scan as an
administrator, that is, right-click/run as administrator.

If I try to print to the fax printer that seemed to have been mapped
successfully (that was mapped with "add printer" as described above),
it basically takes me to the same step to add a fax account, at which
point it tells me I don't have the appropriate permissions when I
enter the server name. Note that when I "added" the printer, it
prompted me for the credentials, and then successfully mapped the
printer. Now in trying to use it to print (fax) something, it behaves
as if I still need to create a fax account and tells me I have no
permissions (and there is no option to enter a user/password).

Has anyone run across this, or can provide any suggestions.

Thanks

I saw that but needed to confirm exactly what you did before forwarding to
the developers to have a look. I'll let you know if I hear anything.
--
Russ Valentine
[MVP-Outlook]
"CoDer" wrote in message
...
Hi Russ,

I did mention it on the original/first posting. I tried the server name
with & without backslahes, the fax name with & without backslashes, and
server\fax with and without the leading backslashes. It made no
difference.

"Russ Valentine [MVP-Outlook]" wrote in message
...
Not sure what you're saying. You should enter only the faxname, no
severname, no backslashes whatsoever. And if you tried it already, why
didn't you say so?
If you have, you're problem cannot be reproduced by the developers, so
I'll notify them.
--
Russ Valentine
[MVP-Outlook]
"CoDer" wrote in message
...
Thanks for the suggestion, but had tried that already
\\servername
servername
\\servername\faxname
servername\faxname
faxname
\\faxname

All give the same result- the "no permission" message, with no
opportunity to enter and appropriate logon

"Russ Valentine [MVP-Outlook]" wrote in message
...
Try losing the backslash on your path statement when configuring the
Fax Account.
--
Russ Valentine
[MVP-Outlook]
"CoDer" wrote in message
...
I had added "Everyone" permissions to the fax server on Server 2003. I
even created a user account on Server 2003 with the same name &
password as the Vista user (although their SID's would have been
different, since the Vista user is not the Domain user on the Server).
None of that made a difference.

Although I've seen similar issues reading through the group, I haven't
come across the same type of scenario - most that deal with domains
are talking about SBS, which is slightly different than the standard
Windows Server. But none of the things they've tried have made a
difference on my end.

I think the part that makes this more troublesome is that it simply
says you have no permission, without giving you an opportunity to
enter appropriate credentials. As I mentioned on the posting, I am
able to add the fax server as one of my printers by adding a network
printer through "Add new printer". At the point that I'm adding that
new printer, it does prompt me for appropriate server crendentials,
and then the printer gets mapped. But if I try to use that printer, it
takes me to the step in Windows Fax and Scan where you need to create
the Fax account (even though I wasn't purposefully trying to use Fax
and Scan), and we're back to square one where it just tells you
there's no permission, without the option to provide credentials...

In short, after trying all kinds of options, this is what the behavior
appears to be:

1) Any printing done to a fax printer is forced to go through Windows
Fax and Scan (that is, even if you're not using Vista's built-in fax
print driver). Or, at least, another MS fax printer driver (like the
one from Server 2003) gets recognized by Vista as a fax printer driver
and forces it to go through Windows Fax and Scan.

2) If you're going through Windows Fax and Scan, a Fax account must be
created. And in creating that account, if there is any kind of
permission issue, you have no way of entering an appropriate
user/password for accessing or to allow use of the printer.

I can't see that being the case, as it would be so terribly
restrictive and a big step backwards, so I must be missing something!
But at this point, what I've done so far points in that direction.

As far as the PC not being on the Domain, unfortunately it cannot be
added to the domain. But I can map the printer to the PC by providing
an appropriate domain logon when I map it, so it doesn't look like the
domain is blocking any and all clients that are not on the domain.

"Russ Valentine [MVP-Outlook]" wrote in message
news Lots of folks have had similar issues (as you can see by reading the
group). I'm wondering if the problem is that the client isn't on the
domain. Have you checked the permission settings in the Security Tab?
--
Russ Valentine
[MVP-Outlook]
"CoDer" wrote in message
...
I am running Vista Business, and am trying to setup faxing with
Vista's built-in Windows Fax and Scan. I do not have a modem, and so
I'm trying to connect to the fax on a Windows Server 2003 R2 server.
This is a "standard" Server 2003, that is, it is *not* SBS (Small
Business Server).

The server is a domain controller, but the Vista PC is not on the
domain. However, both computers are on the same local
network/subnet. On Vista I can map a drive that's on the server
(providing the proper server credentials). I can even "Add new
printer" to Vista by selecting network printer and entering the
server address & shared fax name, then entering the proper server
credentials. So this rules out any network issues, and at least
mostly rules out authentication issues (since I'm able to connect to
the server disk and printer resources if I provide a server
administrator logon).

However, from Vista's "Windows Fax and Scan", when I try to create a
fax account, it prompts me for the server name, and when I enter the
server, it tells me that I don't have the appropriate permissions
and to contact the fax administrator. This happens whether I enter
\\servername, \\servername\faxname, servername, faxname, \\faxname.
Also, I have made sure to run Windows Fax and Scan as an
administrator, that is, right-click/run as administrator.

If I try to print to the fax printer that seemed to have been mapped
successfully (that was mapped with "add printer" as described
above), it basically takes me to the same step to add a fax account,
at which point it tells me I don't have the appropriate permissions
when I enter the server name. Note that when I "added" the printer,
it prompted me for the credentials, and then successfully mapped the
printer. Now in trying to use it to print (fax) something, it
behaves as if I still need to create a fax account and tells me I
have no permissions (and there is no option to enter a
user/password).

Has anyone run across this, or can provide any suggestions.

Thanks

The developers confirmed that the answer is what I suggested initially. For
WFS to work, the client must be logged onto the domain with credentials the
server understands. Creating a network connection will not work in Vista as
it did in older OS because of the tighter security in Vista: RPC for network
shares no longer remembers credentials because of the security risk that
poses. So RPC for WFS can use only the logged on user token and cannot use a
network share. Makes sense even to a dumb cardiologist. It's called
"progress."
--
Russ Valentine
[MVP-Outlook]
"CoDer" wrote in message
...
Hi Russ,

I did mention it on the original/first posting. I tried the server name
with & without backslahes, the fax name with & without backslashes, and
server\fax with and without the leading backslashes. It made no
difference.

"Russ Valentine [MVP-Outlook]" wrote in message
...
Not sure what you're saying. You should enter only the faxname, no
severname, no backslashes whatsoever. And if you tried it already, why
didn't you say so?
If you have, you're problem cannot be reproduced by the developers, so
I'll notify them.
--
Russ Valentine
[MVP-Outlook]
"CoDer" wrote in message
...
Thanks for the suggestion, but had tried that already
\\servername
servername
\\servername\faxname
servername\faxname
faxname
\\faxname

All give the same result- the "no permission" message, with no
opportunity to enter and appropriate logon

"Russ Valentine [MVP-Outlook]" wrote in message
...
Try losing the backslash on your path statement when configuring the
Fax Account.
--
Russ Valentine
[MVP-Outlook]
"CoDer" wrote in message
...
I had added "Everyone" permissions to the fax server on Server 2003. I
even created a user account on Server 2003 with the same name &
password as the Vista user (although their SID's would have been
different, since the Vista user is not the Domain user on the Server).
None of that made a difference.

Although I've seen similar issues reading through the group, I haven't
come across the same type of scenario - most that deal with domains
are talking about SBS, which is slightly different than the standard
Windows Server. But none of the things they've tried have made a
difference on my end.

I think the part that makes this more troublesome is that it simply
says you have no permission, without giving you an opportunity to
enter appropriate credentials. As I mentioned on the posting, I am
able to add the fax server as one of my printers by adding a network
printer through "Add new printer". At the point that I'm adding that
new printer, it does prompt me for appropriate server crendentials,
and then the printer gets mapped. But if I try to use that printer, it
takes me to the step in Windows Fax and Scan where you need to create
the Fax account (even though I wasn't purposefully trying to use Fax
and Scan), and we're back to square one where it just tells you
there's no permission, without the option to provide credentials...

In short, after trying all kinds of options, this is what the behavior
appears to be:

1) Any printing done to a fax printer is forced to go through Windows
Fax and Scan (that is, even if you're not using Vista's built-in fax
print driver). Or, at least, another MS fax printer driver (like the
one from Server 2003) gets recognized by Vista as a fax printer driver
and forces it to go through Windows Fax and Scan.

2) If you're going through Windows Fax and Scan, a Fax account must be
created. And in creating that account, if there is any kind of
permission issue, you have no way of entering an appropriate
user/password for accessing or to allow use of the printer.

I can't see that being the case, as it would be so terribly
restrictive and a big step backwards, so I must be missing something!
But at this point, what I've done so far points in that direction.

As far as the PC not being on the Domain, unfortunately it cannot be
added to the domain. But I can map the printer to the PC by providing
an appropriate domain logon when I map it, so it doesn't look like the
domain is blocking any and all clients that are not on the domain.

"Russ Valentine [MVP-Outlook]" wrote in message
news Lots of folks have had similar issues (as you can see by reading the
group). I'm wondering if the problem is that the client isn't on the
domain. Have you checked the permission settings in the Security Tab?
--
Russ Valentine
[MVP-Outlook]
"CoDer" wrote in message
...
I am running Vista Business, and am trying to setup faxing with
Vista's built-in Windows Fax and Scan. I do not have a modem, and so
I'm trying to connect to the fax on a Windows Server 2003 R2 server.
This is a "standard" Server 2003, that is, it is *not* SBS (Small
Business Server).

The server is a domain controller, but the Vista PC is not on the
domain. However, both computers are on the same local
network/subnet. On Vista I can map a drive that's on the server
(providing the proper server credentials). I can even "Add new
printer" to Vista by selecting network printer and entering the
server address & shared fax name, then entering the proper server
credentials. So this rules out any network issues, and at least
mostly rules out authentication issues (since I'm able to connect to
the server disk and printer resources if I provide a server
administrator logon).

However, from Vista's "Windows Fax and Scan", when I try to create a
fax account, it prompts me for the server name, and when I enter the
server, it tells me that I don't have the appropriate permissions
and to contact the fax administrator. This happens whether I enter
\\servername, \\servername\faxname, servername, faxname, \\faxname.
Also, I have made sure to run Windows Fax and Scan as an
administrator, that is, right-click/run as administrator.

If I try to print to the fax printer that seemed to have been mapped
successfully (that was mapped with "add printer" as described
above), it basically takes me to the same step to add a fax account,
at which point it tells me I don't have the appropriate permissions
when I enter the server name. Note that when I "added" the printer,
it prompted me for the credentials, and then successfully mapped the
printer. Now in trying to use it to print (fax) something, it
behaves as if I still need to create a fax account and tells me I
have no permissions (and there is no option to enter a
user/password).

Has anyone run across this, or can provide any suggestions.

Thanks

Greetings,
I got same problem at my customer's network with all PC's and server
with Windows Server 2003 Standard R2 SP2 (up-to-date) on workgroup (no
DC)!

Last week their boss bought new Lenovo laptop with Vista bussiness.
All went well till I need to put him access to their fax server what is
running on their upper named server.

Each PC user have same account with same password on server that gives
them access to server resource.

Let me just note that all works well on PC's running XP!.

P.S. is there a solution or I must downgrade laptop to XP Pro to make
it back working?


--
ludidomagoj
Posted via http://www.vistaheads.com

You mean a solution other than the one I posted?
Obviously not.

--
Russ Valentine
[MVP-Outlook]
"ludidomagoj" wrote in
message ...

Greetings,
I got same problem at my customer's network with all PC's and server
with Windows Server 2003 Standard R2 SP2 (up-to-date) on workgroup (no
DC)!

Last week their boss bought new Lenovo laptop with Vista bussiness.
All went well till I need to put him access to their fax server what is
running on their upper named server.

Each PC user have same account with same password on server that gives
them access to server resource.

Let me just note that all works well on PC's running XP!.

P.S. is there a solution or I must downgrade laptop to XP Pro to make
it back working?


--
ludidomagoj
Posted via http://www.vistaheads.com

Just wanted to add after a long time of no hope/solution that I called
upon OEM Vista Business licence right to downgrade it and I did it.
Installed XP Pro SP3, putted SAME username/password local account on
laptop as it is written on server.

Then installed XP Fax service WITHOUT MODEM driver althoe laptop has it
and after it I just doubleclicked on server's shared fax "printer" while
"exploring" '\\SERVERNAME' (file://\\SERVERNAME) and it works as it
should

GL fixing that bug and try to remove workgroup "mode" in near future
server products as u did with SMB server products to avoid any more
shameful posts.

Best Regards

P.S. it was client side problem not server, because whole time I
haven't touched a server, because of lack of faith in Vista as client
product


--
ludidomagoj
Posted via http://www.vistaheads.com

This tells me what is different and why it won't work

This part I do not fully understand. Wonder if you could answer a few questions.

1. Can WFS add a SBS 2003 fax server as an account?

2. If so, how?

3. If not is there another way to use the fax server in SBS 2003 from a vista machine?


Post Originated from http://www.VistaForums.com Vista Support Forums

As long as the server fax has been enabled for sharing, it can be used to
create a Fax account in WFS. Just use \\servername in the text box for
remote server.
--
Russ Valentine
[MVP-Outlook]
"NTZeek" wrote in message ...

Quote:

. . . For WFS to work, the client must be logged onto the domain with credentials the server understands. Creating a network connection will not work in Vista as it did in older OS because of the tighter security in Vista:

This tells me what is different and why it won't work

Quote:

So RPC for WFS can use only the logged on user token and cannot use a network share.

This part I do not fully understand. Wonder if you could answer a few
questions.

1. Can WFS add a SBS 2003 fax server as an account?

2. If so, how?

3. If not is there another way to use the fax server in SBS 2003 from a
vista machine?


Post Originated from http://www.VistaForums.com Vista Support Forums