Solaris nis client can't connect to Windows 2008 NIS Server across subnets

I have been using Microsoft Windows Server for NIS for years to centralize some accounts accessing Solaris and Linux OS.
Windows 2003 R2 Indentity Management for UNIX version of Server for NIS was last working version with Solairs.
After upgrading Domain to Windows 2008 all Solaris clients that are on different subnets fail to bind and connect to NIS servers now.
These servers already were setup using ypinit -c to manually add the NIS servers to connect to and prior to Windows 2008 this worked.
Now no Solaris nis clients on different subnets (no firewall between) can connect , but other Unix/Linux OS connect fine.
Is this a known issue and can we get a resolution as it seems only Solaris is affected?

Hi Mid.Hudson-IT,
Before we begin ,we should ensure we have configured the printer server correctly .
Here is a link for reference of configuring the printer server .
Print server role: Configuring a print server
https://technet.microsoft.com/en-us/library/cc775791(v=ws.10).aspx
"I can map all of the printers on the network to the print server as-well as install the drivers correctly and I can resolve the IP and server name via DNS"
From this sentence ,I can`t figure out whether you have tried to ping the server both with the IP adress and name adress from the client ?
If we can ping the print server from the client,we can ensure the connection to the printer server is good .
Then we can try to install the printer driver directly to have a check .In the adress bar of Windows Explorer ,input "\\server name \the printer name"
If we cannot ping the print server ,we should troubleshoot the network issue firstly.
We also can check the event viewer for more information to troubleshoot this issue .
Best regards

Similar Messages

Wyse Thin client not connecting to Windows 2008 R2 server

Configuration
SBS 2011 Server
Windows 2008 R2 server with Remote Desktop Services installed, License Manager installed.
WYSE WT3125SE thin clients with Windows CE 5
I setup the Windows 2008 with Remote Desktop Services and was able to successfully connect the Thin client. Then I installed the License Manger and applied my Open license using User Cals. Was able to login. Next day I get the following
error-"Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again" I still can connect fine from other machines even Windows Home Ed.
I remove license server and still was unable to connect. Built a second Windows 2008 R2 server with RDS on it. Was able to connect without issue. Pointed it to the first RDS server license manager and have still been able to connect with
the Thin Client. The thin client can rdp to the SBS server without issue in admin mode, can connect to RDS2 server but not RDS1 with the license manger. So my issue is with the license and so my question is what is it with the license server
running on that server that is keeping thin client from connecting. I even did a reload of RDS1 and tested connecting throughout the process and it worked up until I applied the license and then it stops. And then if I uninstall the license, rds, remove
from domain still not able to connect. Any help would be appreciated.

We had the same problem with older terminals after cloning a 2008R2 rds server and sysprep it.
The original rds server worked fine but when the old terminals connect to the new 1 they come up with the error : Because
of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again"
After reading all of the postings about this issue and tried the reactivate solution of the license server,
I was sure that it had something to do with the x509 certificates that are generated the first time you connect to a valid license server.
What I did, I installed a new license server activate it but did not install licenses on it.
I pointed the defective rds server to the newly installed license server and deleted the following registry keys:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM
Certificate
X509 Certificate
X509 Certificate ID
X509 Certificate2
Then reboot.
After the reboot all old terminals can connect fine again. As final step I pointed the rds server to the same license server as the other ones,
reboot and all worked fine.
So conclusion is that when you pont a rds server to a license server that has the new type of licenses on it it will generate the wrong x509 certificates
that are not supported by the older clients, by pointing it first to 1 without any rds calls on it, it generates the older x509 certificates which are compatible with the older rdp clients then the switch to new license server will then not regenerate the
x509 certs so it keeps working.
I hope this helps someone
This issue was driving me crazy so very happy that it is resolved now
Cheers Frits

Can't connect to Windows shared file server

I'm trying to connect to our Windows shared file server. I can add the drive and see it, however, when I open the folders nothing is there. I called Apple Support who said that it was most likely a Windows-related issue and that I may need to install some Windows driver on the PC the file server is on to get this to work (he wasn't exactly sure what the fix was for this). Has anyone experienced anything similar? And if so, what's the fix???

Reinfire,
sorry to horn in on this question, but i am having a similar problem, but in reverse. I am trying to connect from Win 8.1 to my mavericks iMac but it will not connect. I am sure that it's related to SMB but the fix you have posted did nothing for it.
Any ideas?

How to connect to Windows 2008 VPN server with certificate support

Unfortunatelly if I select any Windows 2008 server compatible protocol (PPTP, L2TP) I cannot select PKI certificate, its only available for Cisco VPN. Yet my company has 1000 laptops and utilizing Windows 2008 Server for VPN (Cisco is too expensive and unnecessary because VPN is part of Windows Server). PKI certificate is required for connection security.
Any plans to enable certificates for PPTP or L2TP in 2.1 firmware? Even better would be to add SSTP protocol with certificate support, because it takes only one standard TCP connection (https) per user (uses least possible NAT resources for heavy loaded NATed WiFi spots). Also in some public places https is the only option to connect as PPTP and L2TP are filtered.

Hi Shahzad,
>>how to connect sql server 2008 r2 sp2 with visual studio 2013 ultimate?
Based on your issue, if you wan to connect the sql server 2008 r2 sp2 from VS2013 IDE. I suggest you can try the Ammar and darnold924's suggestion to check your issue.
In addition, I suggest you can also refer the following steps to connect the sql server 2008 r2 sp2 with visual studio 2013 ultimate.
Step1: I suggest you can go to VIEW->SQL Server Object Explorer->Right click SQL Server->Add SQL Server.
Step2: After you connect the SQL Server 2008 r2 sp2 fine, I suggest you can go to VIEW->Server Explorer-> right click the Data Connection->Add Connection.
And then you can create the connect string in the Add Connection dialog box.
Hope it help you!
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Can't connect to windows xp via server name

I have a network via Airport Express: imac 10.6.8 and PC windows XP sp3
Suddenly, without any reason, I got this issue:
I can't see the PC in on left share bar of Finder windows.
The only way to see the PC is : go > connect to server" > server address = smb://ip address BUT doesn't work if I use the computer name instead of the ip address( i.e ".smb://ip-address" works fine BUT "smb://computer-name" doens't work : message "connection failed")
Sometimes , very rerely, the XP computer name appears on the share bar but again, if I try to connect I get "connection failed " message.
It seems that iMac is not able to translate the logical computer name with the ip address.
Due to this issue , I have a trouble to use the shared windows printer because I have to install (on the mac) the windows printer using the ip address of the PC but if the IP address changes (I use DHCP and sometimes I have other computers on the network so the IP addres may change) I have to install again the printer with the new IP address.
Can someone help me?
Many thanks
Giuseppe

Same problem - can't see the Apple TV on iTunes to be able to connect despite changing the TCP address etc

Mac10.x client can't connect to File Server on Windows2008 Failover Cluster

Installation of a cluster was made according to the document "Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster " http://technet.microsoft.com/en-us/library/cc731844.aspx.
My Mac OS X 10.5.2 and Mac OS X 10.4.11 clients be able to connect to a non-cluster file server on a Windows 2008 (the File Services role) and also to old file cluster on a Windows 2003.
Why Mac clients can't connect to Windows 2008 Failover Cluster?

Are you running a firewall on the Macs. If yes does it work with out the firewall? If it works with out the firewall that means you will have to create a custom ipf rule which includes the both the physical an virtual IP addresses of your cluster.

Windows 2008 Terminal Server issue after swapping modem/router

Hi, I have a problem I just can't crack.
Windows 2008 Terminal Server, all patched and up to date. The IP Address is 192.168.1.11 (on a teamed intel controller). Terminal services enabled and working ok.
TP-Link Modem 192.168.1.1, RDP Port forwarded ok.
Set the Windows gateway to 192.168.1.1 and external access to RDP is not a problem.
We had some modem speed issues, so we got a much faster connection, but it can't be used for incoming RDP, so left the TP-Link in place. So added a 3G modem at 192.168.1.5 and set that as the gateway.
External RDP access still works perfectly, and now users have much faster internet.
The TP-Link is giving some reliability issues, so I swapped it over for another modem, a Billion modem. Same 192.168.1.1 IP address, same port forwarding. External RDP access is no longer possible.
Swap back to the TP-Link and everything is fine. Test the modem on another site, everything works as expected.
If I set the gateway on the terminal server to 192.168.1.1 with the Billion attached then external RDP access is no problem. If I set it to 192.168.1.5 then it stops working again.
I tried with a new TP-Link modem of the same model with exactly the same settings and this also had the same problem. External RDP access will only work the existing TP-Link modem, which is a problem as the modem appears to be faulty.
It's almost like it hasn't worked out that it's a new network, and when Windows does that it seems to lock down RDP. That is only my assumption from experience of moving computers to new networks and RDP won't work until windows prompts you with the new
network screen to select home, office or public.
Has anyone experienced anything like this before or can shed some light on the problem?
Thanks.

Hi,
How is the issue going now? Is there any update?
Thanks.
Jeremy Wu
TechNet Community Support

Client can not connect to Server installed window server 2008 and using 8.8

HI all!
I have a problem when Client log in to server that installed window server 2008.It can not connect to this server even when restart and key in IP or Server name,...
I try disable Firewall of window 2008 in server machine and client can connect to server. But when i disable firewall, it's mean i can not use Remote desktop or terminal service..
Now, how i can do in order to solve this problem.
Thanks!

Hi,
Take a look at the admin guide (Page 75, 119, 159):
[http://service.sap.com/~sapidb/011000358700000150922010E.zip]
If you installed a firewall on the license service computer, make sure that the firewall is not set to port 30000; otherwise, the license service cannot work.
If you are using Port X, make sure that you open Port X and Port (X+1) in the firewall. For example, if you are using port 10000, make sure to also open port 10001.
The default communication port is 1143.
The default port of the SAP Business One license server is 30000 for license communication and 30001 for the license naming service

Outlook client can't connect in but OWA works

You need to make sure your OutlookAnywhere and AutoDiscover settings are setup properly along with Split-DNS. OutlookAnywhere and Split-DNS are vital for future-proofing your Exchange configuration and making it work properly now, regardless if you use Exchange 2007, 2010, or 2013. For Exchange 2013, OutlookAnywhere is a requirement and Split-DNS is Best Practice. If you are on Exchange 2007 or 2010, and you do not have OutlookAnywhere enabled, enable OutlookAnywhere and follow this guide.You should always use NTLM over Basic authentication, as Basic sends the username and password in the clear, and NTLM is Windows Authentication. On Exchange 2013, you also have a new option called Negotiate, which is recommended. As you follow this guide, you will set the ClientAuthenticationMethod (Internal and External if on Exchange 2013) to NTLM...

Outlook client can't connect in configured outlook on workstation but OWA works.
This topic first appeared in the Spiceworks Community

HT3986 I installed windows 7 to my macbook pro, but my mousepad does not work in windows 7 and also i can not connect my windows 7 to projector, but i can use my macbook's mouse pad and i can connect my mac to projector,so please help me for windows 7 pro

I installed windows 7 to my macbook pro, but my mousepad does not work in windows 7 and also i can not connect my windows 7 to projector, but i can use my macbook's mouse pad and i can connect my mac to projector,so please help me for windows 7 problem

i try to download now, do you think when i download and install the windows support software, can i fix the problem?

Remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed

remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed each time i try to open remote connection to the server,
does remote desktop connection manager V2.2 not compatible with windows 8.1, and if so, is there are any other compatible versions
or what's the problem,
Mahmoud Sabry IT System Engineer

this issue maybe will be fix by latest version, we still waiting for it
maybe your issue can be fix using this methods
https://social.technet.microsoft.com/Forums/windowsserver/en-US/61f218a5-5ef8-49da-a035-90cdd64fc9a0/problem-with-remote-desktop-connection-manager-error-3334?forum=winserverTS
http://shawn.meunier.com/?p=1#comment-43

Windows 2008 R2 Client computer backup files (*.dat) can't get restored after re-imaging the Windows 2008 R2 server

I have a Windows server 2008 R2 and I'm using backup feature to backup all computers in the network on it. Recently I ran into an issue and had to re-image my Windows 2008 R2 server and had to restore 2 of my client computers but now I can't restore
files from my client computer backups because they are not listed under Backups & Devices anymore however all backup files are still available on my Backup drive. How can I retrieve files from these backup files?

Anyone out there to help me with this issue?

Windows can't connect to shares on Lion Server

I can't connect any windows machines (XP, Vist, or 7) to a Mac Pro running Lion Server. When attempting to connect, the windows user is prompted for credentials, and nothing entered in this box works even the server admin account info, once entering account credentials, it comes back with NAMEOFWINDOWSCOMPUTER\USER as if it's trying to sign into a domain, which we don't have domains.
I can't seem to find anything relevent when searching...

There are a couple things you can try:
1.\ go to the apple server, sys prefs, sharing, selct file sharing and then select option. from there make sure the both check boxes are selected. then select done.
2.\ while you are there, in the shared folders section, selct the folder you would like to share (or add if its not) and make sure the user is in the users pane that you want to share the folder with.
3.\ restart your windows machine to make sure it forgets any passwords you may have put in.
4.\ if it still doesnt ask for a user account go to map network drive. and select the option to put another username and password in. for the user name user SERVERNAME\username - ensure the servername is in CAPITAL letter...
hope this helps...

Some clients can't connect after 10.6.6 update - the see an error -43

Hi There,
I'm a designer so am not all that technical but have managed to setup and maintain OS X servers since 10.5.
I've just updated the server to 10.6.6 and now some of our clients can't connect - they get the following error:
"There was an error connecting to the server. Check the server name or IP address and try again.
If you are unable to resolve the problem contact your system administrator."
If I click OK to the error above on the client, I see another error which reads:
"The operation cannot be completed because one or more required items cannot be found.
(Error code -43)"
I've restarted the server and the clients but no luck.
The server is running the following services:
- AFP
- DNS
- Firewall
- NFS (although I don't remember setting this up - is this started with AFP?)
- Open Directory
I can ping the server and login via ARD so not sure why we see the first IP address error as mentioned above.
Any help or suggestions would be most welcome.
Regards
Ben

One question, is this when you hit "Connect to Server" or is this after you've established a connection and try to open/edit/save files?
Here is some general advice:
1) I assume your whole network is behind a router and that we are talking a small office environment (5-10 people) and not some large enterprise. If so the Firewall service can probably be disabled. As a matter of fact if your issue is that clients can't connect at all the firewall may actually be causing your problem.
2) NFS can almost certainly be disabled. Its generally only used for two reasons 1) The netboot service needs it. 2) You support unix/bsd clients. I can see from your list of services that netboot isn't something you're doing and I doubt that as a designer you would have much use for unix/bsd systems.

Control key not working on MB Pro while connected to windows 2008 server through 2x client. Any ideas? Works on windows through parallels.

Control key not working on MB Pro while connected to windows 2008 server through 2x client. Any ideas? Works on windows XP through parallels desktop.

Hello...
It seems I got it fixed!! I had been trying the Fixit tool from
http://support.microsoft.com/kb/306759 while typing up there :))))
This tool is for changing RDP port but running it fixed my problem (I kept the port 3389 intact)!!
Hope it helps someone.

Solaris nis client can't connect to Windows 2008 NIS Server across subnets

Similar Messages

Maybe you are looking for