unable to get the current node name error... 1

[brownlg]

We've got some folks running Windows 2000 with the 4.0 client who are now getting the following error message whenever they login:

"Unable to get the current node name. Real time display cannot continue."

They get this right when they login. Everything else then seems to work fine except for the RTDs.

This is a recent devlopment. It seems to have started after having their virus scan software updated and the blaster fix applied to their client. Obviously we don't want to roll back the fix or disable virus scan, so those aren't really options - other than just to see if they're the cause I suppose.

Just wondering if anyone else has seen this error.

Les Brown
Kelly Services, Inc.

 

[lislis]

I have the same error when trying to connect to some servers outside my corporate network using some VPN or something like that.
In my opinion it's something about port blocking but I don't have ideas which ones...

Any news/solutions?

Lis

 

[brownlg]

they're on the corporate lan, but you might be on to something. i am here in the same building as the server and have no problem. they are from a different building, but still on the same lan and all have the problem. i wonder if it has something to do with the router through which they're connecting to our building?

Les Brown
Kelly Services, Inc.

 

[brownlg]

it is definitely port blocking. we had a bunch of ports locked down during a virus crisis. we started getting those errors even on our internal LAN (if you had to cross a router to get to the server). they recently opened the ports back up and that eliminated the problem. i know ONE of the ports was 135. i haven't tried to see if i can access it from the VPN since though.

Les Brown
Kelly Services, Inc.