Re: Some clients won't connect - node type?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks Jim. I will give it a try.
Regards, Catherine

"Jim Behning SBS MVP" wrote:

Just for grinnies have you run winsockxpfix? I go to this college
website to get the fix. They obviously have plenty of machines that
get messed up and the utility is their starting point. I might also be
running hijackthis to see if there is any junk running on the machine
but that takes an experienced eye. Something I have some days but not
other days.
http://www.iup.edu/house/resnet/winfix.shtm

On Tue, 20 Feb 2007 05:17:13 -0800, Catherine Allen
<CatherineAllen@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hi Douglas/Alan,
Thanks. As suggested I ran ipconfig /renew on a failing workstation while
running ISA logging. The workstation is initially assigned a valid IP
address, but eventaully connection is Closed. There are no obvious rules
that are failing.

When I compare to other workstations that are not failing I noted only the
following differences:
1. Failing computer has no LDAP or RPC (all interfaces) protocols in ISA log.
2. Failing computer has "Unidentified IP traffic" protocol, Action:
Initiated Connection. Rule: All traffic from internal network to local host".
48 seconds later there is: Ping, Closed Connection, All traffic from
internal network to local host; NetBios session, Closed Connection, Allow
access from trusted connection to firewall client; and Microsoft CIFS (TCP),
Closed Connection, Allow access from trusted connection to firewall client.
The IP address then disappears from the log.

DHCP is already assigning node type hybrid, so there is nothing to
fix/change there.

Any other suggestions would be appreciated.
Thanks, Catherine

"Douglas Boyd [MSFT]" wrote:

Hello Catherine

Thanks for using Microsoft Online support

You can use the logging functionality in ISA to see which rule is causing
the failure. Open up ISA management and click the logging tab and then
start the query and do a ipconfig/renew on one of the clients that is
failing. The logging should show you any failures and the rule that caused
the failure. You can also change the node type assigned by DHCP in the
Scope.

I hope this helps

Doug Boyd
dboyd@xxxxxxxxxxxxxxxxxxxx

This post is provided "AS IS" with no warranties and confers no rights



.

Relevant Pages

  • Re: Some clients wont connect - node type?
    ... As suggested I ran ipconfig /renew on a failing workstation while ... but eventaully connection is Closed. ... NetBios session, Closed Connection, Allow ... You can use the logging functionality in ISA to see which rule is causing ...
    (microsoft.public.windows.server.sbs)
  • LDAP bind failed with error 1053
    ... Noticed that when logging on to a member server of a different domain via ... remote desktop connection, ... Computer: memberserver ... Windows cannot query for the list of Group Policy objects. ...
    (microsoft.public.windows.server.general)
  • Re: How to stop an event recoding in syslog
    ... know any service daemon who _does not_ write a log entry for a connection ... Logging that message seems to me like something that many people would ... Which evidence do you have for this asumtion!? ... I'm sorry that we don't speak a shared version of English. ...
    (comp.mail.sendmail)
  • Re: Postfix smtpd DNS lookup delay
    ... the connection. ... Small risk, but still a risk. ... it may want to do logging based on the service configuration ... Many servers want to (or can be configured ...
    (alt.os.linux.suse)
  • Re: redirecting stdout/err to mysql table
    ... connection to the database *every* time you log. ... if you have many programs logging to the same ... to the same MySQL database on a separate machine, ...
    (comp.lang.python)