Windows Domain Policy Blocking Ports?

[Kurbz]

Hi All,

I'll lay out the scenario:

System A:

XPsp2 w/ full updates etc

Windows Firewall off

No 3rd party firewall

Symantic Corp AV

No Modifications to Policies.

Logged in as Local Admin

Direct connection to the internet

This system allows incoming data on all ports !

Now...

System is removed from the Direct Internet connection

Located on a network with a Domain

Logged in as Local Admin once more

The Domain is joined and relevant authentication is successful

Reboot, login under known domain account

**Now here there are policies allpied to the system.???

**Which are preventing this....

System is returned to the original location with a direct connection to the internet

Logged in as Local Admin

= System cannot receive incoming data on certain ports (eg 15123)

I had this problem before, and I scoured the net and at the end of the day I got around this problem for good. I simply cannot remember what i did it has been so long, and I cannot find the relevant information to solve it. I do remember however i did change the registry or even some setting in the policy editor, group or local or other i cant remember wither.

BTW: In everyday context this problem is simlar to having ports blocked using uTorrent or such. Except there is no firewall,no router.

This is tough...!

Kurbz

Edited June 6, 2007 by Kurbz

[cluberti]

The only thing that would be blocking ports would be the firewall, or TCP port filtering (both could have been configured in group policy via settings under the Computer Configuration container, which would affect a local user not logging into the domain as the policies would have been tatooed under HKLM). You can check these settings obviously in the control panel for the firewall, and the properties of TCP/IP for the network connection, respectively. Unless there's a 3rd party app that can block ports on the box, which you state there is not.

[Kurbz]

Hi,

thx for reply, double checked everything....

Firewall Off

No IP Filtering

In addition..

Policy Keys in HKLM have been stripped (these rebuilt themselves for a standard local machine (it seems))

Using GPEDIT.MSC to view Machine & User Policies, they are all set to 'Not Configured'

Edited June 6, 2007 by Kurbz