Cannot connect to client

Setting up ARD for the first time in a high school setting. I can't connect to any of my classroom computers. They are not showing up using Bonjour or using the Local network.
I do have Remote Management On.
thanks for any advice.

So I have tried to figure this out based on the Port Mapping user tip, with no luck. It's not exactly self-explanatory for a non-expert like me. Here's what I did:
Go to system Prefs and show Ethernet Connection
Change to Manual addressing
IP address: 10.0.1.201
Subnet mask: 255.255.255.0
Router IP: 10.0.1.1
DNS server: 10.0.1.1
When I do this I lose internet service.
Then I go to Airport Admin Utility and go to Port Mapping
ADD: Public Address: 3283; Private IP address: 10.0.1.161 or 10.0.1.201 (.161 is my compter at work, .201 is my home iMac - neither address works and I'm not sure which it should refer to); Private port:3283
Add: Public Address: 5900; Private IP address: 10.0.1.161 or 10.0.1.201 (.161 is my compter at work, .201 is my home iMac - neither address works and I'm not sure which it should refer to); Private port:5900
What should I do differently?

Similar Messages

AirPort Express cannot connect in client mode when encryption used

I'm trying to set up my brand new AirPort Express in client mode to stream my music wirelessly to my receiver, which is on another floor of my house. I can't get it to associate with my Linksys WRV200 wireless router when using any kind of encryption. It works fine with encryption disabled, but I really don't want to leave that kind of security hole in my network.
-Equipment-
AirPort Extreme - v6.3 firmware
AirPort Admin - v4.2
WRV200 - v1.0.12 firmware (latest version)
Dell desktop with Windows XP SP2 (Running iTunes 6.0.5.20)
Dell laptop with Windows XP SP2 (running AirPort Admin)
IBM laptop with Fedora Core 5 (for connection testing)
-Procedure-
Various encryption methods were set on the WRV200's primary SSID and matching settings were set on the AirPort. All changes to the AirPort Extreme were done wirelessly with AirPort Admin 4.2 on Windows XP SP2+latest updates. Here are the changes from default that I made on the AirPort:
AirPort Tab
-Name and password were changed
-Wireless mode was set to "Join an existing wireless network (wireless client)"
-Network name was changed but stayed consistent throughout the tests
-Security setting was changed for each test
Internet Tab
-DHCP or manual IP were specified depending on the test.
Music Tab
-"Enable Air Tunes" was checked
-A name was given to the share
-Results-
No Encryption - iTunes sees the AirPort Extreme and can stream music to it. This works in both DHCP and manual IP mode. Interestingly enough, when set to DHCP, it grabs the same address as the manual one I input, which isn't the next one in sequence for the DHCP server (192.168.1.250 instead of 192.168.1.103)
128 bit WEP - Flashing orange light on the AirPort, no DHCP lease, no connection. Still doesn't work when a manual IP address is provided.
WPA2 Personal - Solid green light for 10 seconds, then two amber flashes and back to solid green. I can see association requests in my router's log every 10 seconds or so while this is going on. The strange light pattern only happens when a manual IP is selected. I still see the association requests when DHCP is selected, but the light on the AirPort just flashes amber all the time.
I know that the router's working correctly as my Linux and Windows laptops can DHCP and connect to the Internet with WEP or WPA2, but for some reason I can't connect the AirPort Express to the wireless router when I use encryption. I'd switch out the Linksys box, but I don't know of any other consumer-level wireless routers that allow multiple simultaneous wireless SSIDs.
Does anyone have a suggestion of what to try next?
AirPort Express Other OS

One of the problems with WEP is that the actual standard relies on a 10 character HEX key for 40bit WEP and a 26 character HEX key for 128bit WEP.
In order to make things easier for people, vendors use certain algorithms to convert simple alphanumeric passwords (or passphrases) into HEX keys, thus enabling people to use simple memorable WEP password rather than lengthy HEX keys.
The problem is that different vendors use different algorithms to generate the HEX key and therefore a ASCII password on an AEBS will be hashed differently on a Netgear client and vice versa.
One thing is a 13 character 128 bit WEP password will be hashed by all vendors in the same way (if you use 40bit WEP then a 5 character password is required).
Though sometimes not even that works and the HEX key must be used regardless.
AirPort: Joining an encrypted wireless network
http://docs.info.apple.com/article.html?artnum=106424
Choosing a password for networks that use Wired Equivalent Privacy (WEP)
http://docs.info.apple.com/article.html?artnum=108058

Re: Cannot connect Java client to T3S

Timothy Lee wrote:
This should be in one of the FAQs for WLS7. I think this is the message you
get when you do not have a valid certificate, or you forgot to disable cert
validity/hostname checking via
-Dweblogic.security.SSL.IgnoreHostnameVerification=true
The WLS 6.1sp2 message might have been something like:
Failed to connect to t3s://localhost:7002 due to: [t3s://localhost:7002:
Destination unreachable; nested exception is:
java.io.IOException: Server Certificate SubjectDN CommonName
received does not match Server hostname; No available router to destination]
However, I've verified that the -D option (above) fails in 7.0, and using
the console to disable hostname verification also fails in 6.1sp2. This is
exactly what fails for me:
java -cp ~/weblogic6/wlserver6.1/lib/weblogic.jar weblogic.Admin -url
t3s://localhost:7002 PING
(with the error above).
I get the original poster's error (below) with 7.0 even if I disable
hostname verification. In 7.0, SSL isn't enabled by default and you have to
generate your own certs with utils.CertGen password...
I notice that the release notes for 6.1sp3 contain several t3s fixes.
Perhaps it is fixed there. I'm still waiting to be "approved" for the silly
new system bea has in place so I can download patches to test sp3.
(as a software developer, I want to download and test the software I am
thinking of purchasing and running in production. If I can not do that then
the system is broken.)
Hi
The same command works with Weblogic 6.0. Is it a bug of Weblogic
7.0?
Or it is a configuration issue (I use default value for everything for a
newly created domain).
Tim
Timothy Lee wrote:
Hi
I am trying to connect a Java JMS client to Weblogic 7.0 over SSL.
However, I am not able to connect any Java client using t3s (e.g. java
weblogic.Admin PING). The SSLClient from the example works fine in both
Weblogic and JSSE. Is anyone have idea what is wrong with my Weblogic
setting or anything? Here is the error message:
Failed to connect to t3s://localhost:7002 due to: [t3s://localhost:7002:
Destination unreachable; nested exception is:
java.io.IOException: Write Channel Closed, possible SSL handshaking or
trust failure; No available router to destination]
Regards,
Tim

"Kiran" <[email protected]> wrote in message
news:3fafdf60$[email protected]..
I am also getting the same problem. Is there any solution for this?What is the exact error message that you are getting?

ARD Login Screen Flashes; cannot connect to client

I have a Macbook Pro running ARD 3.4 under Leopard in my office.
Recently I purchased several new iMacs running Snow Leopard. I have set up 5 of them, but on one of them I cannot login with ARD. I can see the computer on the Scanner list of machines. When I click on it the first time login screen flashes very rapidly on my screen then disappears. I cannot enter my user name or password because it is gone so quickly. What do I do to trouble shoot this?

One thing I found, when trying to put a client system into ARD, is that the IP address currently assigned to the system being entered is the same IP that was used by a different system previously entered the ARD "All Computers" list. This "old" system IP is held in ARD even though DHCP has expired the lease and given the IP to the "new" system.
What I end up doing is deleting the "old" system from ARD and then doing a scan, finding the "new" system and putting it into ARD. When the "old" system comes back on line, you will have to do another scan to put it back into ARD.
One other problem I have run into, but can not make happen on a repeatable basis is that a client system will, for no appearent reason, drop off the ARD server's list and then only show up as a "black" computer on subsequent scans. It can not be put back into the ARD list of computers. Sometimes Screen Sharing will work but other times even screen sharing does not work. The only thing I found that will reliably clear this problem is to totally remove ALL ARD and Remote Management related files, including the hidden files, restarting the computer and downloading and installing a new copy of the ARD client and then putting it back into the ARD server's list.

Very new to ARD. Quick question re: Cannot connect to client

I will try to be brief here. I have a MacBookPro running ARD 3. I stay in conntact with my 86 year old mom with iChat and have controlled her emac with ARD 2.2 in the past. She has moved to a new home and nothing changed on her machine. I upgraded to the ARD 3.0, yet all passwords remained the same. When I try to connect, I see unknown under offline, yet I get an accurate ip address for her machine (had a friend verify it at her end) I am sure this is a simple fix, but being so new to this world of ip stuff, I could really use the help. Without this link, mom starts pushing buttons and can really screw up her machine. I have not done any upgrades to 3 at her end.
Thanks in advance.
Phil

Verrrry similar situation, except that I am new to the whole ARD experience. Just bought ARD 3 to use on my mom's new intel iMac.
Don't know WHAT I'm doing. I hate to admit that I don't know how to 'open port 22,' as I'm more of a photoshop/audio/video guy, and this 'networking/administering' stuff is new to me.
Is there a 'sticky' or FAQ on getting a single machine under control from my machines at home?
Sorry to be so naive, just started searching and found this topic.

ASA Remote Access VPN: internal LAN cannot connect to connected VPN clients

Hi community,
I configured IPSec remote Access VPN in ASA, and remote client use Cisco VPN client to connect to the HQ. The VPN is working now, VPN clients can connect to Servers inside and IT's subnet, but from my PC or Servers inside LAN cannot ping or initial a RDP to connected VPN clients. Below is my configuration:
object-group network RemoteVPN_LocalNet
network-object 172.29.168.0 255.255.255.0
network-object 172.29.169.0 255.255.255.0
network-object 172.29.173.0 255.255.255.128
network-object 172.29.172.0 255.255.255.0
access-list Split_Tunnel remark The Corporation network behind ASA
access-list Split_Tunnel extended permit ip object-group RemoteVPN_LocalNet 10.88.61.0 255.255.255.0
ip local pool remotevpnpool 10.88.61.10-10.88.61.15 mask 255.255.255.0
nat (inside,outside) source static Allow_Go_Internet Allow_Go_Internet destination static remotevpnpool remotevpnpool
crypto ipsec ikev1 transform-set myset esp-aes esp-sha-hmac
crypto dynamic-map dyn1 1 set ikev1 transform-set myset
crypto map mymap 65000 ipsec-isakmp dynamic dyn1
crypto map mymap interface outside
tunnel-group remotevpngroup type remote-access
tunnel-group remotevpngroup general-attributes
address-pool remotevpnpool
authentication-server-group MS_LDAP LOCAL
default-group-policy Split_Tunnel_Policy
I don't know what I miss in order to have internal LANs initial connection to connected vpn clients. Please guide me.
Thanks in advanced.

Hi tranminhc,
Step 1: Create an object.
object network vpn_clients
subnet 10.88.61.0 mask 255.255.255.0
Step 2: Create a standard ACL.
access-list my-split standard permit ip object RemoteVPN_LocalNet
Step 3: Remove this line, because I am not sure what "Allow_Go_Internet" included for nat-exemption.
no nat (inside,outside) source static Allow_Go_Internet Allow_Go_Internet destination static remotevpnpool remotevpnpool
Step 4: Create new nat exemption.
nat (inside,outside) source static RemoteVPN_LocalNet RemoteVPN_LocalNet destination static vpn_clients vpn_clients
Step 5: Apply ACL on the tunnel.
group-policy Split_Tunnel_Policy attributes
split-tunnel-policy tunnelspecified
split-tunnel-network-list value my-split
Step 6:
I assume you have a default route on your inside L3 switch point back to ASA's inside address. If you don't have one.
Please add a default or add static route as shown below.
route 10.88.61.0 mask 255.255.255.0 xxx.xxx.xxx.xxx
xxx.xxx.xxx.xxx = equal to ASA's inside interface address.
Hope this helps.
Thanks
Rizwan Rafeek

Cannot connect to printer hosted on a Win2012 Server with a Windows 7-64bit client (Error 0x00004005)

I have a Windows 2012 Server set up offering print services to our network, there are about 20 printers set up all deployed via group policy. Recently, on one of our Windows 7 machines I am finding that I an unable to connect to one of the printers shared
on the print server while other clients seem to be able to connect to the same printer with no problem. Also, the printer used to work just fine from this same Windows 7 machine.
To test things further I logged onto the Win7 machine as the domain administrator, connected to the print server and double clicked on the printer to attempt to install it manually (rather than letting Group Policy do it). When I do so I receive the following
message, "Windows cannot connect to the printer. Operation failed with error 0x00004005.
I have done some searching but the only references I am finding to this particular error message involved users attempting to connect to a printer hosted on a 32-bit version of Windows from a 64-bit client. However, in my case both the server and client
are 64-bit.
Can any one help me troubleshoot this 0x00004005 error?
Thank you.

Sorry for the delay. I just went and attempted to add the printer again on the client machine, the installation failed just as before, no log entries were recorded in the PrintService Admin log and the Operational log was disabled, I enabled it and added
the printer again. This time when the installation failed seven log entries appeared in the Operational log, all of them informational, no errors or warnings, the events are as follows...
1. Event 300, Printer {71688D29-F70C-42F2-90E1-DA5D450E772D} was created. No user action is required.
2. Event 304, Printer {71688D29-F70C-42F2-90E1-DA5D450E772D} was resumed. No user action is required.
3. Event 306, Settings for printer {71688D29-F70C-42F2-90E1-DA5D450E772D} were changed. No user action is required.
4. Event 306, Settings for printer {71688D29-F70C-42F2-90E1-DA5D450E772D} were changed. No user action is required.
5. Event 302, Printer {71688D29-F70C-42F2-90E1-DA5D450E772D} will be deleted. No user action is required.
6. Event 302, Printer {71688D29-F70C-42F2-90E1-DA5D450E772D},8 will be deleted. No user action is required.
7. Event 301, Printer {71688D29-F70C-42F2-90E1-DA5D450E772D} was deleted, and users will no longer be able to print to this printer. No user action is required.
There are a couple log entries in the Admin log indicating an error occurred, those errors occurred yesterday afternoon at 4:30pm or so. I did not try to add the printer then so I don't know if these are related to this particular problem or not. This same
entry appeared twice at exactly the same time...
The print spooler failed to load a plug-in module C:\Windows\system32\spool\DRIVERS\x64\3\PrintConfig.dll, error code 0xc1. See the event user data for context information.
As a temporary workaround I installed the drivers for that printer directly on the Windows 7 client machine and that works fine, however this is less than ideal because I had set up group policy to only install that printer for specific users, not for everyone.

Windows 8.1 cannot connect to group policy client service

Windows 8.1 laptop under administrator account has this "cannot connect to group policy client service" error.Found the following instructions on internet but I don't see this "Replace owner on subcontainers and objects" box on Permissions/Advanced
popup windows ???
Could anyone help ?
Change the permissions on the relevant keys configuring the Group Policy Client service to allow Full Control to Administrators
Open regedit (Start > type regedit in the search box) and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\gpsvc
Right-click the registry key and choose Permissions.
Click Advanced, then click Owner.
Choose Administrators and check the Replace owner on subcontainers and objects box.
Exit the permissions dialog and then open it again.
Click Advanced, then choose Administrators and click
Edit…
Check Replace all child object permissions with inheritable permissions from this object.
Click OK and confirm; exit.
Thank you,

Hello CarLover,
Based on my test, the option Replace owner on subcontainers and objects exists in Windows 7, but doesn’t exist in Windows 8.1.
Please take a look at the screenshot about the option in Windows 7.
Please take a look at the following thread similar to this issue.
http://answers.microsoft.com/en-us/windows/forum/windows_7-performance/why-wont-windows-connect-to-the-group-policy/b73107f8-8447-4599-87a5-65ecc6a63aa0
Best regards,
Fangzhou CHEN
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Windows VNC clients cannot connect to Snow Leopard Server native VNC server

I am resurfacing the following related comment made in another post that discusses the same issue I am having with VNC on Snow Leopard. This is still an issue and I cannot connect to our Xserve's Snow Leopard Server with a VNC client on Windows.
I don't want to install another third party VNC server onto our SL Server, and am looking for a VNC client for windows that will connect to our SL Server.
Does anyone have any solutions?
== QUOTED TEXT BELOW ==
Re: Newbie: Connect Windows -> OSX Server
Posted: Nov 4, 2009 9:26 AM in response to: Antonio Rocco
I would politely disagree. Yes, definitely, the Mac 'Screen Sharing' app works a treat, and Apple Remote Desktop.app works as well, but I am coming from a Window's PeeCee.
For me, connecting to my 10.5(.8) Server via tightvnc gives 'Server did not offer supported security type!". Using RealVNC to this machine states "No matching security types Do you wish to reconnect to ... ?" a telnet to this AppleVNCServer service (port 5900), shows RFB 003.889 *, or Remote Frame Buffer Major 3, minor 889.
Also, connecting to multiple 10.6(.1) Clients with Tightvnc correctly asks for a password but then hangs at "Status: Security type requested". Using RealVNC opens, connects, asks for authentication, and exits. Telneting to this AppleVNCServer service (port 5900), also shows RFB 003.889 *.
The Current Version of the protocol is supposed to be 3.8, that is Major version 3, minor version 8. Not 80 or 800 but Eight). http://www.realvnc.com/docs/rfbproto.pdf and I believe that tightvnc only supports up to version 3.7.
On each station I have installed the 'old' OSXVnc.app as a service (to a unique port). OSXVnc utilizes protocol 3.3 and I can control them successfully, but that is of my own doing because of this issue.
Now JollysFastVNC works a treat to any machine I have EVER tried to connect to. I have not tried COTVNC or any of the others (too slow for me, when they wer e around)
Also, I just noticed that RealVNC states that their free and personal version will not connect to Mac OSX (x86 and PPC) but the Enterprise one will. I just Dl'ed the Enterprise Viewer and it gave essentially the same thing ('protocol is not valid' message, even after it asks for a password). Anyway, I am not here to hijack this thread, just trying to keep the info flowing and open.
Maybe I am the only one with these problems but the bottom line is I cannot use Real or Tight, or UltraVNC to administer my server or clients as long as AppleVNCServer gives out the 003.889 protocol version.
Peter
* The ProtocolVersion message consists of 12 bytes interpreted as a string of ASCII characters in the format "RFB xxx.yyy\n" where xxx and yyy are the major and
minor version numbers, padded with zeros.

Searching on the net brought me to the same solution that Mr. Hoffman found as well, I was a bit skeptical at first but since he recommended it, and all my other attempts failed, it was a last resort and I have some additional notes of my own for a successful solution. Read the two links below first before doing anything, as they contribute to the solution in tandem.
http://forums.macrumors.com/showpost.php?p=7221295&postcount=20
http://forums.macrumors.com/showpost.php?p=9081641&postcount=28
I should probably just create an entirely new post with all of the steps that worked for me, but it's rather straightforward nonetheless.

Cannot connect clients to LDAP only CardDav

Hi All,
I've got a mountain lion server running 10.8.2 and we're recently migrated our OD from a 10.6.8 server. All the users and passwords work fine for file sharing, contacts (via carddav), calendar, and vpn. However, I'd like to some users via LDAP for machines that are unmanaged but shared computers or ios devices.
I've got the "directory contacts in search" check marked in the server admin app. The server host name is example.com and I'm trying to setup my ldap clients as below:
iOS
Server: example.com
User Name: user (not [email protected])
Password: password
Description: example.com
Mountain Lion
Account Type: LDAP
server address: example.com
Server Options: por 636 use ssl
Description: EXAMPLE LDAP
Search Base: dc=example, dc=com
Scope: Subtree
Authentication: Simple
User Name: User
Password: Password
On iOS devices, I get an error that says "cannot connect using ssl" even though there's valid certificate on the server for the hostname, I then get an "LDAP Account unable to verify account information" error. On the Macs I can add the account, and it will show under directories, but nothing is returned in searchs.
As a side note, I do have Google apps setup on the same hostname, with those MX records on the ISP DNS, but not the internal DNS (as when they were on the internal DNS CardDav would not work).
Any suggestions? Are my search bases wrong? Something I need to configure in the Directory Manager?
Thanks!
Fkick

I was able to get this fixed myself. Basically, I had to have Authentication set to none in order for any device to connect to the server... is there no way to enforce user authentication with 10.8.2 Server?

Cannot connect to Hyperion MDM application server through MDM client

Hi,
I am using Hyperion System 9 MDM.
But after installing the MDM server on a MS SQL database, i installed the mdm client.
Now when i tried to create a new connection from client app and gave the application server URL "http://localhost/mdm_ntier" as stated in the installation guide, i was getting the error.
"cannot connect to the URL".
Can anyone help me in this regard.
Thanks in advance.

Please delete this post and post in a Hyperion forum.
That way you will find an audience that can help you.

8.8 Client cannot connect to Windows Server 2008 error -1102

SAP Business On 8.8 on PL 18
This is not the first time I have had this issue with Windows Server 2008.
however everytime the resolution was diffrent. Now this site is causing trouble.
The issue is the client cannot connect. We have the log on window, can see the company list. type on the password and we get a -1102 error.
The client on the Server itself can log on. It is the cleints that cannot.
I checked these below.
1 SQL Native client is installed and ok.
2. Licence server is configured and ok
3. The user has admin access to locl PC
4. The SAP user name and password are correct ( client on server can connect fine )
5. The ports 1433, 30000 and 30001 are open on the server.
6. Through SQL server configuration the named pipes and TCP are enabled.
7. SQL server browser is running
The only things I have not tried are
The Firewall is running on the server and I have not yet stopped it. Will try that tomorrow.
Do you have any other ideas please ?

I have got this working but I am not confidant of the outcome - yet - I really need your expert advise here.
This is what I did. In that order.
1.     As Owen suggested I checked if there was a specified Port for the instance. What I found was TCP Dynamic ports were enabled ( SQL server config manager | network configuration | tcp properties ) and there was no TCP port specified. Assuming ( ai may be wrong) that the system assigns a dynamic port to this instance I set it up so the Dynamic port does not happen and manually specified the Port 1433. Restarted the SQL Service. ( still having the Port 1433 open in the firewall). This did not solve the issue.
2.     With the above setting still on, switched off the firewall. Went to the PC client and SAP can log on now. Now keeping the SAP client running, switched on the Firewall on the server. Log off SAP on PC client and log back in ( with firewall off ). SAP now can log on.
3.     I had to do the above step for all PCs to get them working.
4. Currently the firewall is on and clients can connect
So what could be happening? I have no clue. It is apparent there is some setting that gets saved within the PCs ( may be user profile) after the first log on with the Firewall off - to say its safe ?
However I have no idea what will happen if the server is restarted u2013 this server we cannot restart any time we want as itu2019s a critical server and runs other things.
I would still like to get to the bottom of this to understand what is happening.
I have a SAP message running too and will ask them this same question.

"System cannot connect to the application server" (Admin Client only)

Hello Experts,
I have a strange issue: I am getting "system cannot connect to the application server" when I am trying to launch BPC Admin.
I successfully connect to the same application server with Excel client on the same PC.
I am able to connect via Admin from another PC.
The installation in question is a new installation. The only difference between my PC and a troubled one is IE7 vs. IE8 - IE8 is the one giving issues.
BPC site is in Local Intranet zone. Windows Authentication is enabled. What am I missing? Local Policy? IE8 settings? Folder permissions (I'm local admin on both PCs)?
It's BPC 7.5 SP05.
Thanks in advance,
Akim
P.S. OS: Windows Server 2003 SP2 32-bit (Citrix box).
Edited by: Akim Zubarchuk on Mar 30, 2011 12:28 AM

Hi Akim,
Check client diagnostic for admin client can provide good information.
Any way if you are able to connect with excel client not with admin client I will say:
1. Check the rights of user used to connect with admin console
2. Check proxy settings
3. Disable antivorus or firewall into that computer.
4. Make sure the installation of admin client was correct done.
In my opinion it is a big probability to be point 3 or 4.
Regards
Sorin Radulescu

Cannot connect with CSM client

One of our clients has a problem with their CSM deployment, they recently upgraded their CSM version which is deployed on a vmware environment, the services are listed as running and the webservice is available on port 1714 - when he tries to access it with the CSM client he gets the error.
The client cannot connect to the authentication service."
* Please cofnirm whether the security manager server is running
I cant find any troubleshooting information for this specific issue - has anyone got any experience of this issue or what could be causing it.
Regards
Joel

I'm having the exact same problem. My work around is to run C:\Program Files (x86)\cscopx\setup\support\resetcasuser.exe, select option 1 and reboot the CSM box.
TAC said the issue was a GPO preventing the casuser for running batch, but we just modified the GPO yesterday and still have trouble.
Strange thing is twe did not have this issue when the backup job was failing.

Win XP Client Cannot Connect to Mac OS X 10.4.4 Server but Win 2000 Can

Anyone run into this problem? Just basic Apple/Windows stand alone, no domain or interaction with other Windows Servers. User can log on fine with Windows 2000 client, but same user cannot connect with Windows XP client on same network.
Any workarounds out there?
Mac G4 MDD, 1GB RAM, 80MB main drive, 400GB data Mac OS X (10.4.4)

I had trouble with a WinXP client a while back, and
only vaguely rememeber things I did to fix it. I'm
thinking it's the Win system, not the Mac. On the win
machine, try deselecting the box "Enable IEEE 802.1x
authen. for this network" in the Properties >
Authentication tab for your network
interface.
Thank you for the suggestion. It worked!

Cannot connect to client

Similar Messages

Maybe you are looking for