Vista_x64 and BM39SP2 vista client = PROBLEM

Vista_x64.
Any body know - how to use BM39sp2 client for vista with this Vista_x64 ??
Serg

Hi,
skoltogyan wrote:
>
> Vista_x64.
> Any body know - how to use BM39sp2 client for vista with this Vista_x64
> ??
You can't. There is no 64-bit VPN CLient, and the 32bit will not work at
all.
CU,
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de

Similar Messages

Bonjour mDNS Vista client problem

Hi all, in my home network I have several machines with different OS'es; XP, Vista, Ubuntu. Recently I have installed Avahi in Ubuntu machines, and Bonjour in Windows machines. The main goal is to have mDNS (.local resolving) working throughout the network. Avahi seems to work ok, as does Bonjour in XP machine. Those machines are able to resolve other's .local names to IP address, and they also answer correctly to mDNS queries.
The problem is the Vista machine. It does answer correctly to mDNS queries, so other machines are able to resolve it's .local name to IP address. But Vista machine is not able to resolve other machines' IP addresses as it should. For ping, the resolving seems to work, but it is slow; it takes 2-3 seconds before ping actually starts, as resolving the .local name to IP address takes so long. Mapping a network drive using .local mDNS name does not work at all. Putty is not able to connect to other machines using .local name.
Is there some known issues in Vista's Bonjour mDNS client which could cause this kind of behavior (e.g. slowness in resolve process, and some programs able to resolve the names and some not)? Any proposals how to debug this further?
I have Vista Ultimate, and I have tried with both 32-b bit and 64-bit versions.

"I can see no real need to install Bonjour on a Windows machine"?
I just explained that the need is to have .local names resolved throughout my home network. AFAIK, there is no support for this in native Windows, but Bonjour should be able to provide that support. So uninstalling Bonjour is not an answer to my needs.

Server 2012R2 -- RDS Farm with XP and Windows Vista Clients

Hi There,
My team has been having some fun in getting our Server 2012R2 farm operational, annoyingly MS documentation is severely lacking on how to correctly configure a 2012R2 Farm correctly.
We have an RDG1-TCC server, which is the RDGateway, RDConnection Broker and RDWeb Server. We have two session host servers RDS1-TCC and RDS2-TCC.
It took us some time and much online research to figure out exactly how we needed to configure the RDS server as a lot of information online for 2012R2 was apparently incorrect(was based on 2008R2 practices). We started off with using a DNS Round Robin for
the RDS Session hosts servers and after a number of certificate issues, we later found this was incorrect. We're now using RDWeb exclusively, which appears to be the correct way to have the Connection Broker working?
We've ran into a number of issues with certificates too, we have an external certificate for remote.domain.com. Installing this on all 4 options in the certificate manager has made internally work correctly via RDWeb, however externally we are getting a
certificate mismatch as it's trying to connected to RDG1-TCC with a certificate for remote.domain.com. I'm pretty sure I can resolve this with a replacement remote.domain.com certificate that includes a SAN for *.domain.internal. Testing with a self signed
certificate seemed to resolve this issue.
Now providing i've configured everything the correct way, we have an issue where RDWEb RDP files do not work internally or externally for XP, Vista or Windows 7 (With RDP7.1). Windows 8/8.1 and Windows 7 with RDP 8/8.1 updates work perfectly fine. Unfortunately
this new client has a few XP machines that they are not willing to update just yet.
Is there a known fix/workaround to get these older clients working correctly?
Sorry for the extremely long post, but I'm sick of banging my head against the wall trying to get something that we assumed would have been fairly simple to get up and running.
Cheers,
Ben

Thanks for the assistance so fat, now I have all clients connecting, I need to tackle the certificate issues.
The UC SAN certificate is going to cost much more than the current certificate, currently that idea is on the back burner as the client does not wish to pay a few hundred extra.
To quickly sum things up:
AD DNS(internal DNS) override in place for remote.domain.com.au pointing it to the internal IP of the gateway/connection broker/RDWeb server.
Connecting Internally its working perfectly fine under all circumstances (I'm guessing this is because of Kerberos Auth)
When users connect externally via RDWeb they get a certificate missmatch as the cert is for remote.domain.com.au and the server is RDG1-TCC.domain.com.net
When users connect externally via MSTSC using the Gateway option, they get a certificate missmatch as per the above, however they also receive a second "certificate is not trusted" error for whatever RDS server they hit.
I have tried the below previously and they broke other things:
"Change published FQDN for Server 2012 or 2012 R2 RDS Deployment."
This resolved the external certificate issue. However then internal connections stopped working. When connecting via RDWeb, you would get asked for credentials instantly and no matter what you entered, it just asked for credentials again.
There did not seem to be ANY event logs for this connection.
"Changing RDP-Tcp listener on RDSH to use external certificate."
I can't recall the exact error we had when we did this, but I know we had to roll back the change. I have a feeling we then started getting certificate missmatch errors on the Session Hosts.
I'm half thinking that when the farm is free(Currently being used for application UAT), I'm going to try and reconfigure the RDP-Tcp listener on the RDSH servers again and see if that resolves one or more of our issues.
Do you have any suggestions on how I can use the correct published FQDN name without breaking internal access? Or any other ideas on getting this entire thing working both internally and externally?
Also, Dharmesh, I've tried clearing out the certificate cache as suggested, but to no avail.

Mac Lion and Cisco VPN client problems

I just installed Lion 10.7 on my iMac and can no longer use the downloaded Cisco VPN client to connect to Microsoft Remote Desktop and access the PC in my company's office. When I try to launch the VPN client I get Error 51. I used to be able to enter a command in the Terminal as a workaround to use the VPN client when that happened, but that no longer works. I have tried booting into 32-bit mode; doesn't work. I tried to use the Cisco client built into Lion using settings provided by my company. When I try to connect I get the following message: "The negotiation with the VPN server failed. Verify the server address and try reconnecting."
I have searched the web looking for a solution. My company's tech department is stumped; the Apple Geniuses haven't been able to help. Does anyone have any ideas how I can use either the downloaded Cisco VPN client or the client built into Lion?
Sent from Cisco Technical Support iPad App

Here is the link which you can use to configure the inbuilt VPN client in MAC Lion.
http://glazenbakje.wordpress.com/2011/07/28/how-to-create-a-cisco-vpn-connection-in-apple-mac-os-x-lion/
Make sure you configure the attributes correctly.
Secondly the inbuilt VPN client code of Lion is made in collaboration with Cisco so there will not be any issues of compatibility.
Cheers,
Rohan

Strange behavior Lion SMB with Vista clients

Hi,
I have a problem with the SMB server in Lion. The configuration is as followes:
- Server: Lion Server (10.7.1) on Mac Mini
- Clients: Mixed, WinXP/Vista/7, 10.6/10.7
Problem:
Vista client have a problem with the SMB shares on Lion.
When I add for example a new folder, in explorer the folder shows up as "ew Folder" instead of "New Folder".
When I try to change the name of the created folder, Windows report it can't find the folder. When I refresh the explorer, the foldername is correct.
It also occurs when creating new files, change files, etc.
It only happens on the Windows Vista client, on Windows XP/7 I have no problems with it.
I can reproduce the problem. On a clean install of 10.7 server and Win Vista the problems exists.

Even after 10.7.2 Server upgrade the problem described byJeroen still remain.
Did someone has a Windows Vista client machine that write files and folders correctly to an SMB share on Lion?
When I say correctly i mean with correct name (example: in my network vista machine can write in SMB share on Lion, but when we add a new folder, this news folder is shown with "ew Folder" instead of "New Folder. Only refreshing explorer we can see the real correct folder name).
This problem doesn't affect ours XP and Vindows 7 clients that are working very well.
Any ideas and solutions?
thanks

Mac OS10.6.2 Server and Windows Vista 64 bit client

Can anyone tell me if the problem below was a quirk or if there is an issue generally.
I recently purchased a new workstation using windows Vista Home Premium 64bit.
Our Apple Sserver had a share on it for the intended user of this workstation but I simply could not get a connection to the server. Everytime I tried to connect it said I did not has sufficient privledges.
If I tried logging into the server from another workstation, using XP, Vista or Windows 7 32bit versions I could access the share with no issues.
I eventually erased and installed a 32bit Windows 7 Pro onto the workstation and it connected perfectly.
This was the forst workstation we have bought running a 64bit operating system, and now faced with a further two workstations to purchase I am somewhat worried.
Is it an inherent problem, or was it just a rough PC with perhaps a problem with the initial install of Vista 64bit.
Any help would be appreicated.
The Server just runs AFP, DHCP and SMB sharing, no open directory, no DNS. Also its just a workgroup not a domain we are trying to connect to.
Thanks
mark

The main problem you're going to have is that Vista will not authenticate in a compatible way to Mac OS X server, not without modifications at the Vista client.
See the post be "Malke" here:
http://www.vistax64.com/vista-general/53712-connecting-osx-macs.html

SBO Client and Windows Vista in workgroup Licence error

Hi!
My customer runs B1 2004C. Network structure is workgroup. Client and server are in the same workgroup. XP users connect successfully, but new Vista user gets the licence error: "-2147024891 Access denied". DCOM and other customizations on the licence server are done like in SAP Notes. It doesn't help.
I know Vista is not officially supported by 2004C B1, but i have several Vista users running SBO fine in domain structure. I think the trouble is in the workgroup.
Thanks a lot!
David.

Hi David,
some of the SAP Notes addressing DCOM access denied problem of 2004 releases.
<b>Note 833798 - After Upgrade W2003 to SP1: Access denied -2147024891</b>
Symptom
After upgrading Windows 2003 server to SP1 you get the access denied error -2147024891
Other terms
license server, error -2147024891
Reason and Prerequisites
Upgrade to Windows 2003 server changes security settings
Solution
The problem is caused by SP1 for W2003 Server. You have to change the
default configuration of the DCOM to enable clients to access license
server again:
1. go to "Start/run", type in "Dcomcnfg" and the Dcom configuration will open
2. expand "Component Services"
3. right click on "my computer", open "Properties"
4. go to tab "Com Security"
5. in "launch and activation permission" go to "edit limits" this
button is new since SP1
6. tick the boxes "remote launch" and "remote activation" for user
"everyone"
After that the clients can access the license server again, if all nescessary rights are give in the DCOM as well. When the changes described above did not take effect, please check this additionally:
1. go to "Start/run", type in "Dcomcnfg" and the Dcom configuration will open
2. expand "Component Services"
3. Go to "SBOLicense", open "Properties" by right-clicking the mouse
4. On register tab "Security" customize all permissions. Add all nescessary User accounts there. If you add i.e. User Group "Everyone" there, you will not have access right problems any longer, as every user belongs by default to this group.
If that change does not take effect immediately, reboot the server.
This note is permanently updated. If you have any comments or proposals tho improve it, please contact the SAP Business One Hotline and let us know.
<b>Note 824976 - error -2147024891, access denied to license server</b>
Symptom
error -2147024891 when trying to connect with B1 client to license server on another computer The License mechanism needs a properly set up license server which is available over the network via DCOM interface to client computers. The necessary windows user rights must be assigned to client and server.
Other terms
Access denied, SAP Business One, License server
Reason and Prerequisites
Functionality description
Solution
1. Is the license server up and running?
The B1 client on the license server computer should be started and logged into to ensure that there are no problems withs the license server itself. The B1 Server tools should be opened and the settings of the License Manager should be checked so that it is possible to connect by pressing the Connect button.
2. Is the network connection between client and license server working?
The server should be pinged via its IP-address for a response. Any firewalls should be disabled between client and license server for troubleshooting reasons as they can effectively block data packets which are needed for license mechanism. If a VPN is used between client and license server all ports should be available.
3. Are necessary windows user rights in the domain given?
We highly recommend to use B1 in a windows domain, as this is the only way to manage user accounts effectively. Domain user accounts have to be configured on the domain controller computer only. For troubleshooting reasons log in at the client with the windows domain administrator account, that should prevent the user from being blocked due to a lack windows user rights. According to our recommendations the users should be Power Users on the local computer.
4. Are necessary windows user rights in a workgroup given?
If the user is in a windows workgroup, the same user account should be configured with the same password on the license server and on each client computer as well. For troubleshooting reasons a local admin account should be configured on each of these computers. As account information is stored locally on each computer, username and password must be exactly the same on each of the machines. Login with this local administrator account. According to our recommendations the users should be Power Users on the local computer.
5. Is DCOM installed and configured correctly?
On the license server DCOM interface should to be installed and configured correctly. It is located under Control panel\administrative tools\ component service. Expand and in My Computer you will find DCOM Config\SBO License. Open its Properties and check configurations in Security tab. Add user accounts there, if needed.
DCOM should be enabled on the Client machines and on the server(s). In the Component Services expand to My Computer and right click to open the Properties for My Computer. Go to the Default Properties tab and make sure that 'Enable Distributed COM on this computer' is ticked. If these settings are modifed a restart of the computer is needed for the changes to take effect.
Br,
Chris

I am intalling client now on windows98 and i have a problem

Hello i am Eloy
i am intalling client now on windows98 and i have this problem

Hello i am Eloy
i am intalling client now on windows98 and i have
this problem....
Which problem do you have?
Win98 was a very "buggy" windows version. Unexpected falls, blue screens, memory violations errors, I was very disappointed about it. This version is seldom found nowadays and a lot of machines come with XP, 2003 or vista from factory.
Win98 was long ago a deprecated platform, so even if you have not clarified which problem you are facing, if it has to do with new software 9iR2, 10gR1, 10gR2, whatever the problem the only solution is to install a newer OS version.
~ Madrid.

Is Verizon going to acknowlege the problems with FIOS and Windows Vista

For months now, I have been reading the numerous problems Fios internet customers are having with Fios internet/Actiontech Router and Windows Vista and there has been no acknowledgement by Verizon of this current major issue.
I have also experienced the exact same issue for months now since I switched to Verizon FIOS internet. Previously I had Comcast HSI using my Windows Vista laptop. I had their service for over a year and I NEVER has a problem with the Windows Vista globe icon disappearing and loosing internet connection. The Globe always stayed on and never went away and I never lost connection when I had Comcast
I had Verizon FIOS installed last September with my Windows Vista computer and my wireless internet connection started to drop from day 1 and it has been a daily occurrence for over 5 months now. It has gotten so bad, I have had to hardwire my laptop to to be able to use the internet uninterrupted.
This is what daily scenario is:
When I turn on my laptop(with Windows Vista, I can initially get full internet access(with the globe on and it says "Local and internet). After about 10 minutes or less, the globe switches to "local only" and I can still get internet access. After another 5 or so minutes, a large X covers the globe and I lose internet connection entirely. The actiontech router wireless signal is no longer listed as one of the wireless networks. The only way for me to regain internet access is either to restart my laptop or reboot the actiontech router.
Numeorus posts here, over by DSL forums(Broadband Reports),Microsoft's website and a few othere websites detail this issue.
I am extremely shocked and surprised that Verizon has not tried to fix this issue by working with both the makers of the Actiontech Router as well as Microsoft to find out what the problem is and how to fix it.
I would just like to reiterate I strongly believe this is primarily a FIOS internet issue since I previously had Comcast HSI for over a year with the same Windows Vista laptop and I NEVER had that problem. Also, I can connect to my neighbors wireless connection(she uses Comcast HSI) and when I do, the globe stay on all the time on my computer and the internet does not lose connection.
I know that there are a couple of Verizon employees here. Please tell the higher ups who handle FIOS internet that this is a major issue that needs to be resolved as soon as possible.
P.S: Please don't tell me to go by my own router because then, I will have to deal with the issues of setting it up to work with Fios TV and the related VOD, widgets, remote DVR compatability issues to deal with. I don't think I can deal with the additional headaches.

FIOS is short for fiber optics. fiber optics is different technology than DSL.
With that said, if you search the Microsoft databases for vista issues with fiber optics, (CURRENTLY THERE IS ONLY ONE PROVIDER OF FIBER TO THE HOUSE, that being Verizon, so yes you can also search Vista issues with verizon and\or fios) and you will find that Microsoft already acknowledges this issue with their software. AND they offer you a fix.
cjacobs001

Dreamweaver and Windows Vista Problem

Hello,
I ran into a problem with my Dreamweaver - 8 application and
cannot find a fix. I open up the Dreamweaver application, 2-3
seconds later, I get the following error message, “A problem
caused the program to stop working correctly, windows will close
the program and notify you if a solution is available.” I am
using Windows Vista and believe the problem is associated with the
Vista operating system. I am puzzled by the fact that I have been
using Dreamweaver with Vista and have had no problems up until now.
I uninstalled & reinstalled Dreamweaver to no avail. I
restored my computer to an earlier date, and updated Dreamweaver,
and still have the same problem.
Any help to resolve this problem would be greatly
appreciated.
Steve
Text
Text

Hello Again,
I finally fixed the problem. I went into my network settings
and reset my network address. This did the trick, I went back and
opened up Dreamweaver without any problem.
Steve

ITunes and Windows Vista problem

I have Windows Vista and ran iTunes successfully for 8mos. Now I'm getting a message box that says "iTunes has stopped working. Close box and Windows will send a solution." The solution, upgrading Windows, doesn't work. Is Vista the problem?

Scan and Fix windows System files:
Can you go to command prompt (START/ALL PROGRAMS/ACCESSORIES right mouse click "command prompt" and choose "Run as Administrator"
type in
sfc /scannow
let Windows fix any system files that need to be repaired.
Restart the computer if it did actually repair or update files.
Start iTunes again

I have been creating forms in InDesign and pulling into Acrobat XI Pro to do form fields. My client would like to fill in the PDF form, save under a different name locally on their device, and redistribute. The problem I have is that, sometimes, they want

I have been creating forms in InDesign and pulling into Acrobat XI Pro to do form fields. My client would like to fill in the PDF form using Reader, save under a different name locally on their device, and redistribute. The problem I have is that, sometimes, they want to redistribute the form as Read Only. I know how to flatten the form on a mobile device, but uncertain how they can do that with a PC or Mac using Adobe Reader. I looked at FormsCentral thinking there might be a solution going that route, but don't believe there is. Any advice?

FormsCentral won't help with flattening a form. You could set up the form in Acrobat so that the fields are set to read-only, using JavaScript. Not quite the same as flattening but it's the best Reader can do.
Note that when Reader is used to e-sign a document, it gets flattened, but this won't be possible if you need to Reader-enable the form and under certain other conditions.

Problems with airport extreme and windows vista

Hi, I have windows vista and I'm having problems conecting it to air port extreme. The only way I can make airport extreme work is to disconect and reconect the powercord and then my computer reconizes it.
Any sugestions would be helpful.

I just got off the HP "chat" technical assistance about my HP DV6500z doing this same thing. At least for my model there is an October BIOS update. She had me re-install the Broadcom drivers and run the BIOS update. Now the whole computer runs faster in addition to connecting wirelessly! Not only that, I can use the "closed" network feature through the Airport Utility to hide my network as I did in the past and the PC finds it! I guess through all of the very testy notes on HP's discussion board they finally came through (well, at least on this model). My model has the AMD processor so if yours is Intel it may not be the same. I recommend going to their TA chat line or type in your model on their Software & Driver page to see if there is a recent revision on your models BIOS. The one I downloaded was dated 10-2007.

FROM WINDOWS (VISTA) A PROBLEM HAS CAUSED THE PROGRAM TO STOP WORKING CORRECTLY. WINDOWS WILL CLOSE THIS PROGRAM AND NOTIFY YOU IF THERE IS A SOLUTION. FIRE FOX UPDATED TO THE LATEEST, I WOULD RATHER NOT HAVE AUTO UPDATES.

FROM WINDOWS (VISTA) A PROBLEM HAS CAUSED THE PROGRAM TO STOP WORKING CORRECTLY. WINDOWS WILL CLOSE THIS PROGRAM AND NOTIFY YOU IF THERE IS A SOLUTION. UPDATED TO THE LATEEST, I WOULD RATHER NOT HAVE AUTO UPDATES. [email protected] edit

You may select how and whether Firefox updates, although like most software it may be sensible to keep it up-to-date, it is more likely to remain secure and compatible with other software whilst up to date.
* for information on the options available see [[Updating firefox]] <--- clickable link ---

Gateway Server address and Certificate subject name do not match error on Vista client

RD Gateway server is 2012, RD Server is 2008 R2. Client is (currently) Vista Gold (surprised me too).
User was able to connect through the Gateway in the past, but seems to have broken around the time that we switched to a real wildcard SSL certificate. Prior to this, it was using a self issued cert.
I'm stalling for time (and hoping this fixes it) by having the user install the Vista Service Packs. Can anyone verify if this is what's causing the issue, or if I need to look at something else?

Hi,
Yes, updating should fix the issue--the old client versions didn't work properly with wildcard. I recommend you have them install the latest version of the Remote Desktop Client for Vista which is RDP 7.0 capable:
Description of the Remote Desktop Connection 7.0 client update for Remote Desktop Services (RDS) for Windows XP SP3, Windows Vista SP1, and Windows Vista SP2
http://support.microsoft.com/kb/969084
-TP

Vista_x64 and BM39SP2 vista client = PROBLEM

Similar Messages

Maybe you are looking for