Search results for query: *

I think I may have figured this out, correct me if I am wrong. The domain I blocked was @ix.netcom.com and @netcom.com by blocking @netcom.com would this also block the @ix.netcom.com? I discovered the problem last night and removed it and restarted the ims. I had the user send an email, never...

Thanks, but I tried that last night. I readded both the individual account and the domain, restarted the ims and then removed them restarted the ims again and restarted the server still not working this morning. Maybe will try this again tonight. Mark

I have a problem with message filtering. A user or the domain got added to the filtered list, once we noticed that they should not have been added we removed them and worked fine for months. Just installed some hotfix patches from Microsoft and now that user is being blocked again. Checked the...

You are correct in your assumption. You can only map to shared folders. Share each subfolder and this should work. I experienced similiar problems when we migrated to NT from Novell. -Mark

Sorry, I am having an off day its port 113, I should research this a little more before I open my big fat fingers. -Mark Clip from Watchguards website- Description: Some SMTP servers use the port 113 Authentication service to verify the identity of the sending host. If your Firebox or SOHO...

Your right and I am wrong this works the other way around when you can not send mail to their domain. Sorry for the runaround. Sounds like a DNS issue on there end though did you check into the ip port 13 (AUTH) on the firewall. We run a Watchguard firebox and this did need to opened up for some...

You need to add the ip address and the domain name on yours. I know it seems weird but that will probably fix it. -Mark

It is an authorization port, I read your post again and if they are on exchange also you probably don't need port 13 open, the problem I encountered was a unix machine with sendmail, somehow it uses this port to verify the sender address. -Mark

If this doesn't fix it or you are already setup this way, I had a customer once that I had to add them manually on the connection tab of the IMS under message delivery click the specify by e-mail domain and add their domain and ip address. It fixed this for them, I think the problem was with the...

I don't think it is an Exchange problem, open port 13 on your firewall and have them try again. -Mark

Microsoft Knowledge Base Article - 256194 No Desktop or Blank Desktop After Logging On to Windows 2000 The information in this article applies to: Microsoft Windows 2000 Server Microsoft Windows 2000 Advanced Server Microsoft Windows 2000 Professional This article was previously published under...

I had this problem with a remote location, and it was the default gateway on the unix server was wrong, it had never been updated when they installed thier dsl router. -Mark

The way that I handled this (wrong way but works) Come in bright and early and stop the information store. Explain to everyone that you may not have enough disk space any longer for all the saved email and this could be the reason the server is not working. Tell them that as soon as you get it...

The only way that we have been able to accomplish this is to create a public folder object for contacts and the users can stick em in there. -mark

First take away thier internet address, double click the mailbox go to the email address tab and remove the smtp address, this will eliminate incoming mail. Then goto the IMS for your site under connections click on the delivery restrictions tab add these users to the reject messages from...

Rename the user in user manager for domains then change the primary windows account for the mailbox. -Mark

Try this link. I remember when we first setup exchange with owa and had this same problem. http://support.microsoft.com/default.aspx?scid=kb;en-us;Q230594

I am up to date on virus defs and run NavMSE on my exchange server. I am able to block this virus with out any problems from outside threats. This virus keeps appearing on my exchange server imcdata/in folder. It quarantines it with out any problems but I cant determine were it is originating...

At this location they are using netbeui and have tcp/ip running for the protocols. They have logon and restore network connections enabled for the client for MS networks. This is a remote location (them in Holland and me in the US) that I have only seen their setup once and have been trying to...

We have 5 95 workstations one of these is acting as a server with shared folders and printers. Sometimes when a user reboots his machine he is not able to reconnect to the server. Once the server is rebooted the user is able to connect to the server with out any problems. Any ideas. Mark