Tracing routing issue on network

[mdrabble]

I have a very strange issue and I'm after help on where and how to go about troubleshooting it.

 

Sage 200 installer refuses to run and download the "sage bits" when run over the LAN where the core switches are the gateway.

 

Desktop -> LAN -> Core -> Smoothwall = fail to download and install

 

Traffic was not even reaching the Smoothwall box!

 

 

 

If I run the wifi, where the Gateway is set as smoothwall, then it run, downloads and installs.

 

Desktop -> Wifi -> Smoothwall = Download and Installs.

 

 

 

The url that Sage 200 installer connects to download and install is 'https://pros200appasage.blob.core.windows.net/clickonce/desktopclient/StandardDesktop.application' - which resolves to 20.209.58.11:443

 

I've just installed wireshark to try and capture what is happening - so this is going to be fun......

 

Any help would be appreciated.

 

Cheers

[Davit2005]

Does not make a lot of sense, lol.

 

Have you tried a packet capture on the smoothwall. The reason why I ask is that our firewall will only log traffic which matches a rule and that rule is set to log traffic. On our firewall we can do a packet capture for dropped traffic. Is their any chance it could be SSL inspection if you have that enabled?

[mdrabble]

Does not make a lot of sense, lol.

 

The way I am trying to describe the issue - or the issue itself?

 

Have you tried a packet capture on the smoothwall. The reason why I ask is that our firewall will only log traffic which matches a rule and that rule is set to log traffic. On our firewall we can do a packet capture for dropped traffic. Is their any chance it could be SSL inspection if you have that enabled?

 

I was on the phone with Smoothwall for nearly an hour looking at this and the engineer said he couldn't see the traffic for the desktop IP going to the sage url/ip

 

That was when I thought to try the Wifi connection and hey presto it worked - so we concluded it must has been a LAN based issue.

 

I'll have a play and see what I else I can find out.

[Davit2005]

Yep the issue :-)

 

Our firewall will only log traffic if there is some sort of rule in place that being a deny or allow. If there is no filtering or firewall between the desktop and the Smoothwall it leads me to think the issue is with the Smoothwall.

 

Is it the same device failing on wired and then successful on wifi?

 

Can you try and do a tracert to the IP and FQDN from the desktop to see the route, this should get as far as the Smoothwall at least?

Edited August 29, 2023 by Davit2005

[mdrabble]

 

Sovled it!

 

I had the URLS in the client proxy exceptions for nearly 2 years worked fine, so why now they have stopped I have no idea - soon as I removed them from the Proxy Settings, it worked straight away!

 

I'm just happy I have it working and dont have to mess my headup trying to understand wireshark captures

[3s-gtech]

Been through that pain when our ISP stopped allowing Teams traffic straight through the firewall but didn’t tell us, it wouldn’t work until I pulled the addresses out of the exceptions list!

 

That was a fun day.

[Davit2005]

Spent a 2 weeks sorting an issue caused by an application using 443 but in the end had to put an exception in to bypass decryption to that URL from specific internal addresses as lucky enough it was users from specific internal IP addresses.