sultan966

What is the subnet mask of primary gateway 10.198.136.1? What is the switchport ip address and subnet maks that is connected to primary gateway?

Your firewall address is 10.0.0.253. One of the port of your layer 3 switch must have an address in this same subnet. This port is not switchport but layer 3 port means it has static ip address. Check what port is connected to Firewall. Let us say the port of your layer 3 switch that is connected to Firewall has an address of 10.0.0.100. On the firewall issue the command: ip route 172.16.10.96 0.0.0.31 10.0.0.100 Check all the ip addresses on the layer 3 switch. Find out what port has ip address in 10.0.0.0 network. It could be a vlan as well. For example: Interface vlan 1 ip address 10.0.0.100 255.255.255.0 Find out if a physical port or vlan port has an address in 10.0.0.0/24 network on the layer 3 switch.

On the firewall you have to make a static route: ip route 172.16.10.96 0.0.0.31 (someting like this). Check hp command for static route.

Your configuration is: VLAN 50 - Management Default Gateway - 172.16.10.100 Mask - 255.255.255.224 Range of IPs - 172.16.10.96 - 172.16.10.127 You need: Interface vlan 50 ip address 172.16.10.97 255.255.255.224 (or 172.16.10.100) Clients of 172.16.10.96-172.16.10.127 network must have the default gateway address of 172.16.10.97 (You can use 172.16.10.100 as well) You must exclude 172.16.19.97 from dhcp addres range because you are assigning it to Vlan50. From your Layer 3 switch to firewall what is your address range? Can you ping from switch to firewall? Layer3 switch to firewall is different subnet. Ping 8.8.8.8 from switch and see if it works. It must be successful. If not problem is with the firewall. From the firewall ping 8.8.8.8 and see if it succeeds. You sequence of testing will be: 1. Ping 8.8.8.8 from firewall 2. Ping 8.8.8.8 form switch 3. Ping 8.8.8.8 from client in Vlan 50 Do remember that clients in vlan 50 does not need to know your firewall at all. What it needs to know is the default gateway of 172.16.10.97. One more thing: How would the firewall know about network 172.16.10.96-172.16.10.127? You can make a static route on Firewall which will point towards this network. Or you can use a routing protocol between Firewall and layer 3 switch. Firewall must be able to ping a client in the 172.16.10.96-172.16.10.127. Test this. If you can not then sort this out by static route or routing protocol.

You can use ether channel. When you aggregate links using ether channel then there is no STP because it is only one logical channel rather than multiple single channels.

Glad to see your problem is solved.

I think increasing IIS private memory limit will solve the problem. Restart the server after that.

1. Increase IIS Private memory limit. 2. Run WSUS Server CleanUp Wizard. It may take long time to do this. Run one item at a time. Be patient on this. It sometimes takes days to cleanup. See what happens.

some information is missing. Post the upper part of the screenshot.

As soon as you land on the telnet page you have to go to the privilege mode by using the command #enable. It may ask for password if there is one. In this mode use the command: #show span

Use show span command on switches. You will find which switch is root bridge. It also shows the blocked ports. By default stp blocks the slowest links. Port status are as follows: Forwarding Disabled Blocking In one of the switches you will find that one of the port is in blocking state. On root bridge both ports are in forwarding state. On the other switch you will find that one port is in forwarding state and the other port is in blocking state. Obviously you will have to connect to the console port and use a terminal software such as putty. You can also telnet to it if the switch has ip address and telent allowed on the vty lines. Layer 3 switches can be configured to have ip addresses.

1. You have to look at your task sequence. Here is a working task sequence for Windows 10. 2. Load network card driver in SCCM. Compare your task sequence with this one and see if there is any difference.

Sometimes just press CTRL+ALT+DELETE and you will get logon screen.

If you do not need this proxy server anymore then you can try the following: search the registry of the domain controller. Any entry with that proxy server address you can safely delete.

I use pix resizer and it works perfect. Free software.