Win2k3 wierd network behaviour

Posted By: raptor3676 | Jun 1st, 2007 @ 10:37 AM
page 1 of 1
Comments: 5 | Views: 2156
#Jun 1st, 2007 @ 10:37 AM
raptor3676
raptor3676
Hi everyone,

I'm installing a brand new Windows Server,  after I started the server I noticed that Remote Desktop was not working after I activated it, I'm in a hurry so I installed UltraVNC to fulfill the same purpose.  But It didn't work either!

I used the netstat -a command, to check that the sockets where in the listening is state and they are in fact listening.  But didn't connect.  I also tried to see if the culprit was on my laptop and application so I run the command "telnet 192.168.0.81 5900" (which is the port to VNC) from another server but again no connection was stablished.

This is not a network related error, since I'm able to connect to the server shared folders.

Can anyone please point out about what is preventing the server from receiving incomming connectio. By the way the service that this software is meant to run, is not receiving connections from clients either. I already run out of ideas.

Thanx in advace

Raptor
#Jun 1st, 2007 @ 10:43 AM
phreaks
phreaks
Start -->Control Panel --> System -->

Click the 'Remote' tab

Check the box "Enable remote users to do stuff"
(or something to that effect)
#Jun 1st, 2007 @ 10:50 AM
raptor3676
raptor3676
phreaks wrote:
Start -->Control Panel --> System -->

Click the 'Remote' tab

Check the box "Enable remote users to do stuff"
(or something to that effect)


As I've said it was the first thing I did.  And it doesn't explains why VNC or the service I'm trying to install are not working either or being more specific... Why are no accepting incoming connection since there listed as "LISTENING" by the netstat -a command?
#Jun 1st, 2007 @ 12:53 PM
hodo
hodo

Is this an R2 installation?

R2 installs will have the firewall on and block all connections until you logon for the first time and you tell it to start accepting connections.

Before you do this it will allow you to go to Windows Update and get any needed patches but any other types of connections will be disallowed.

#Jun 1st, 2007 @ 1:44 PM
raptor3676
raptor3676
Yes it is a R2 server,  however it was staged before reaching my hands and the Firewall was disabled.   So I don't know what else can be blocking connections.

Thanx anyway
#Jun 1st, 2007 @ 6:40 PM
RichardRudek
RichardRudek
I've had a number of systems that used to run fine with VNC recently stop working. I've been meaning to look into this.

One thing that I was suspicious of was RPC, so you might want to look into that. Specifically, the [dynamic port allocation part of RPC].
page 1 of 1
Comments: 5 | Views: 2156