Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.
It's already gone, I forgot I had that in as a test. As you can see from here and here they do not show up in the log, it's very odd.
I can get to the PF interface from that machine, it can get a DHCP address but no internet traffic can be captured.
Alright, so I have a vlan setup for a "guest" network. I have that vlan assigned to an interface (this is all in VMWARE). VMware network and vlans, interface assignments.
I can get a DHCP address on the VMWare machine and can ping the gateway.
I cannot however, ping anything on the...
I think this is what I'm missing. I'll go in and try to find this setting and change this. Will I need to do this on both sides then for this to work effectively or do you think changing it on the VPN settings will do it for the whole tunnel?
I'm currently logging in more detail the pings over night, on and off backup but the linked pings were during a non backup time and only the tunnel pings were dropped, not the outside ones.
I may have to check to see if I can limit the backup speed though.
Here's the setup.
I have 2 USG50 units setup to do IPSec VPN point to point so one office can connect to the other.
Both internet connections are fed off of a local wireless company, the main office has 5/1 internet and the other is 3/1.
The VPN has been working just fine, for the most...
By default, SC will try to connect to the "relay server" via port 8041 and if that port is not open on the firewall, the connection will fail.
http://help.screenconnect.com/HOWTO-0003.ashx#CF_Changing_Relay_Port_6
I have not yet changed the network but after a few of the previously mentioned chnages the PC (one, for now) is able to nslookup and find the AD/DNS server. I will do further testing on other machines and continue to seek best practices.
I had not, makes sense though. I'd like to read more about this, when to use what, etc if anyone has a good link or two. I did make the change, will see if that helps for external queries, I did noticed it randomly selected some junk IP addresses internally, that may have been causing the issue.
The router DOES have a static IP on the LAN side, it's getting a DHCP address on the WAN side. With clients pointing at the server for DNS, I shouldn't have to set any Google or External DNS nor setup forwarding on the router, the server should take care of that.
I plan on getting in there to...
I'm just going to have to stop in there and re-setup the network/routers, this double NAT is causing a headache.
Now it's passing that 254.254 down.
Config: http://i.imgur.com/hsJ9dVl.jpg (I tried filling all fields with the same IP but it still pushes the 254.254)
DNS Servers . . . ...
The DNS suffix "domain.invalid" I think is some how coming from the Windstream, maybe that IS some how passing bad info along.
Wireless LAN adapter Wireless Network Connection:
Connection-specific DNS Suffix . : domain.invalid
Description . . . . . . . . . . . : Linksys AE2500...
When I get the chance to stop in the shop I will likely make the Linksys a dumb switch but in the mean time, the DHCP device for the "network" is also handing out the right IPCONFIG information. External DNS does work, it's just slow at NSLOOKUP queries sometimes.
Why 1.1 as DNS? Server is 1.4. Also, the 254.254 is coming from a Windstream Modem/Gateway, it's handling the DSL connection, then it's handing down 254.1 to the WAN port of the Linksys. Default gatway of that Linksys is 254.254 of the first router but I don't see how that portion would cause...
Network - 192.168.1.0/24 Router - 192.168.1.1 Server - 192.168.1.4 DNS - 192.168.1.4 DHCP - 192.168.1.1
**NOTE - Tracert shows "double NAT", network before 192.168.1.1 is 192.168.254.254, I cannot change this from my current position but can in the future.
I have a domain setup, we'll call...