Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 390
  • Last Modified:

Problem to access mailbox from one sub-network since 1 day

Hi,

I've got an annoying problem since yesterday.

I've got one network in 192.168.0.X and another in 192.168.42.0.
My exchange serveur (2003) is on 192.168.0.X network.

all is ok for the first subnetwork but for 42.X since yesterday impossible to use outlook.

I can access web access from http://192.168.0.9/exchange without problem...
But when i start outlook, normally it should ask for a password, now it do not.

If i try to create a new profile, when i put ip server adress and the name to search it says that it can't connect to exchange...(but i can ping and use OWA)

Thank you for your help
0
Kishkool
Asked:
Kishkool
  • 13
  • 8
1 Solution
 
NenadicCommented:
What do you have between those subnets? Any form of firewall?
0
 
KishkoolAuthor Commented:
I've got a juniper firewall and a D-link switch.
0
 
KishkoolAuthor Commented:
But i've made no change on them, it's not the first time this problem come. Last time, It has come to work again with no change.

But this time it seems not to want to return...
0
Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

 
NenadicCommented:
On the client computer, modify the c:\windows\system32\drivers\etc\HOSTS file by adding the following to the end:
192.168.0.9    <NAME OF EXCHANGE SERVER>.<AD-Domain>

For example:
192.168.0.9    exchsrv01.mycompany.local

You can use Notepad to open the HOSTS file.
0
 
NenadicCommented:
Sorry, then try to complete profile setup using the Exchange server name.
0
 
KishkoolAuthor Commented:
Thanks for your help but i've already tried this.

When i put netstat i've got
exchangeserver.domain.local:epmap SYN_SENT


If i launch OWA i've got
exchangeserver.domain.local:https ETABLISHED

(so it's work)

I'm lost...
0
 
NenadicCommented:
It has to be down to the firewall then. Are you able to post firewall rules here?
We're looking for RPC ports specifically. If you have a firewall between Outlook and Exchange, RPC ports have to be configured statically.
0
 
KishkoolAuthor Commented:
set address "Bureautique" "proliant" 192.168.0.9 255.255.255.255
set address "technique" "technique-lan" 192.168.42.0 255.255.255.0

Ok so here my exchange serveur is add in group Bureautique.
Network who got problem is group technique (i'm 42.240)


set policy id 4 from "technique" to "Bureautique"  "Any" "Any" "ANY" permit
set policy id 4
exit

So all port is allowed to talk with Bureautique group, including my exchange

Any way, it was working last week and no change were done on firewall so...i don't understand.
I just can't communicate with "outlook autorisation service".. :(
0
 
NenadicCommented:
You need to be able to communicate with DC as well. Where is the DC?
0
 
KishkoolAuthor Commented:
DC is domain controller?

I have no active directory set for the moment.
I've got no domain when we log to computer, exchange server is a windows serveur.
I use it only for create mail user and some IIS service.
0
 
NenadicCommented:
Exchange cannot install without an Active Directory domain. So, you either have a Domain Controller or you had one. If you had one and now you don't - that's the problem.
0
 
KishkoolAuthor Commented:
Exchange still work (OWA, for other subnetwork).

Excuse me if i'm not clear, we 've got a subdomain : mycompany.local
It's all i can say. if i ping exchange.capitalvision.local it works...
0
 
NenadicCommented:
OK. So where is the DC for mycompany.local?
For testing purposes, are you able to open up all ports on the firewall between these two subnets - to remove firewall out of the equation?
0
 
KishkoolAuthor Commented:
Ok i've git all port open beetween subnet. Not working.

I just arrive i'm not sûre. I think this is exchange serveur but there is also a samba serveur. 192.168.0.10.

But all is accessible. It's amazing. And 2 days ago all was working great..
0
 
NenadicCommented:
Nothing in event logs in Exchange? System, Application, Security?
0
 
KishkoolAuthor Commented:
I'll look on it tomorrow and keep you inform.
Thks
0
 
KishkoolAuthor Commented:
Ok so my DC is my exchange server.

Where can i see event logs? I've got only tracking log.
Any way i've look everywhere and i've got not alert who explain my problem.
0
 
KishkoolAuthor Commented:
Ok...i've put company.local in server name then "find a name"
It asks me for the password (allelujah) but it doesn't want my password.

I've close and restart, and now i've got again can't connect to exchange server..
0
 
KishkoolAuthor Commented:
Ah !
Interesting thing.


I'ev got a DNS interne serveur : 192.168.21.1.

On subnet 192.168.0.X if i do

nslookup exchange

I got

Serveur :  srvdns.company.local
Address:  192.168.21.1

Nom : exchange.capitalvision.local
ip : 192.168.0.9

But on my 42.0 network i've got :


Serveur :  srvdns.company.local
Address:  192.168.21.1

srvdns.company.local can't find exchange : non existent domain...
0
 
KishkoolAuthor Commented:
Ok, the problem is resolved. It came from the firewall, even if everything was open there had also NAT rules that disrupted the port 135 (RCP exchange). Thank you for your help.
0
 
KishkoolAuthor Commented:
Thank you
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 13
  • 8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now